| Anomie added a comment. |
"editable": Slot may be editable via EditPage and ApiEditPage. Default is "ignored": Slot is ignored by EditPage and ApiEditPage.
On second thought, maybe we should switch that. Have the default be "editable" and allow code to specify "ignored" as the special case.
FYI, my current vague conception for an EditPage UI is that it would include edit fields[1] for the slots currently on the page (maybe as a tabbed interface?[2]). Each optional slot would have a widget (a button or checkbox?) to allow it to be marked for deletion. And the UI would have a widget (a dropdown with an "Add" button?) for adding a new slot to the page if there are any optional slots that aren't already present.
[1]: Normally a textarea, or an enhanced textarea-like thing. But there's no particular reason it couldn't be a custom form, or even a notice that the slot isn't editable with a standalone rendering of the slot's content. I'm not sure how VE would/should work, presenting a visual editor for the one slot versus continuing to override EditPage entirely.
[2]: For no-JS clients, we might just show all the tabs' contents serially as fieldsets, or make each "tab" a submit button so the server can serve the changed UI.
Cc: Anomie, Aklapper, gerritbot, daniel, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, JJMC89, Agabi10, D3r1ck01, Wikidata-bugs, aude, Jdforrester-WMF, Mbch331, Ltrlg
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
