The table of contents is shown at the bottom of each page only displaying the item's id. This TOC is obviously useless. We should decide if we want to have sections and thus also a TOC and then move the TOC to the right position and filling it with meaningfull data.
|Resolved||Jdlrobson||T78430 [Epic] Getting Wikidata to render nicely on mobile web|
|Resolved||Bene||T95884 Fix table of contents on mobile Wikidata|
|Resolved||Bene||T95889 Show collapsible sections for Statements and Sitelinks|
|Resolved||thiemowmde||T110902 [Bug] Table of content too large on mobile Wikidata|
- Mentioned In
- rEWBAe6364523694b: Insert empty toc to help MobileFrontend
rMEXT3238494fddd6: Updated mediawiki/extensions Project: mediawiki/extensions/Wikibase…
rMEXT6868905b6b06: Updated mediawiki/extensions Project: mediawiki/extensions/MobileFrontend…
rEMFR7ef1b8152e40: Get rid of $wgMFPageSections config
This can be resolved easily by adding an empty <div id="toc"></div> to the item's html. However, the toc should not show up if there are less then 3 sections (which is currently the case on item's pages) so this would still need to be fixed.
Including both sitelinks and identifiers in one section is going to be hard DOM wise and this mostly indicates a logical issue as well. The DOM for sitelinks is generated in SiteLinksView. We could now go ahead and also add the identifiers in there but that won't work in two ways: We don't have the information about statements in SiteLinksView but only a list of sitelinks and not all entities which have identifiers may also have sitelinks.
For these two reasons I think it is better to have three sections and separate sitelinks and identifiers. Furthermore, including two different UIs (for statements and sitelinks) in one section will also be bad considering the user-friendlyness.