[Decission made]
Expander should be there when editing, because when there are to many references the page could make huge scrolling jumps.
[Decission made]
Expander should be there when editing, because when there are to many references the page could make huge scrolling jumps.
Status | Subtype | Assigned | Task | |
---|---|---|---|---|
· · · | ||||
Resolved | Lydia_Pintscher | T87759 [Story] Allow simultaneous editing of mainsnak and references | ||
Declined | • Jonas | T112652 [RFC] The expander should not be there when editing a statement and it's references. Just remove it. The reference section should not be collapsible. | ||
· · · |
I agree that the expander might get confusing when being visible during editing (basically, it is confusing already). However, we need to be aware that for statements with many references the list might get quite long though I doubt we have those cases.
As far as I understand, the expander should still be there in non-edit mode? Or are we going to get rid of that completely and find a better solution?
If the references are hidden in non-edit mode and one clicks edit, we should make sure that the expanding animation is shown so that the user knows where the additional content comes from.