Special:SpecialPages should have horizontally based TOC (such as the TOC on Image: pages) for quicker navigation to such section.
Version: 1.21.x
Severity: enhancement
Description
Description
Details
Details
- Reference
- bz13862
Related Objects
Related Objects
- Mentioned In
- T114057: Refactor table of contents
- Mentioned Here
- T326130: Special:SpecialPages needs a table of contents
Event Timeline
Comment Actions
robert wrote:
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.
Comment Actions
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.
Comment Actions
TOC would also help anyone using a text-only browser, as the list of links is still pretty long.
Comment Actions
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?
Comment Actions
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.
Comment Actions
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.
Comment Actions
Removing myself from CC since I have no interest in implementing this request. I do confirm this is an easy task though.
Comment Actions
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 ?
Comment Actions
(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
Comment Actions
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.
Comment Actions
With the changes from T326130, Special:SpecialPages now has a normal "vertical" table of contents (example). I think that's good enough to resolve this task too, even though it originally asked for a horizontal one. I'm not sure how a horizontal table of contents would even be supposed to look like in Vector 2022.