Last modified: 2014-09-24 01:26:32 UTC
Special:SpecialPages should have horizontally based TOC (such as the TOC on Image: pages) for quicker navigation to such section.
I really don't see the point of this, the TOC itself would be quite large, given the ammount of sections (and there is a high possibility of more in the future) and that it is horizontal (which immediatley increases it's footprint); the page itself is quite small so on most screens one scroll is required to reach the bottom of the page.
Not everybody is using large wide screen displays, not everybody is having full screen window opened, thus the scrolling may be longer than "one scroll". Besides at least anchors/ids for each section would be handy for more user friendly links. And once there were anchors, it's simple to add the TOC.
TOC would also help anyone using a text-only browser, as the list of links is still pretty long.
Done in r36907
Reverted in r37001
Assigned: ^demon
I think is that better to be done as on the File description page which have three or more anchor links on the top of the page?
De-assigning myself, adding +easy
I don't get the point in this. The page is fairly short and a TOC will be way too large (by comment 2). Closing this as WONTFIX.
I think we should still put some IDs on it if we haven't already.
just checked, we have CSS ids for each section headers
Reopening per comment 0 comment 2 comment 3 comment 7. Besides it has been discussed on IRC in the days the bug has been open and it had support there as well.
Removing myself from CC since I have no interest in implementing this request. I do confirm this is an easy task though.
I don't think having a horizontal navigation is a bad idea. However re-using the #filetoc ID is not a good solution. Neither is duplicating CSS rules... Perhaps introduce a semantic class to apply to both ?
(In reply to comment #14) > I don't think having a horizontal navigation is a bad idea. > However re-using the #filetoc ID is not a good solution. Neither is duplicating > CSS rules... > > Perhaps introduce a semantic class to apply to both ? YOU SAID SEMANTIC
adding "design" tag as this is partially a visual design issue
Removing easy keyword - This bug is not "easy" for newcomers as long as it's not clear which design should get implemented. Needs design input first.
I think this should be WONTFIX'd.
