Change Details

A Wikidata item is basically separated into two sections, one for statements and one for sitelinks. Both sections should be collapsible on mobile view and appear in the toc on tablets. The issues why MobileFrontend currently does not recognize our `<h2>` sections are the following: # For MobileFrontend, `<h2>` headlines must be a direct descendent of the `#content` element

A Wikidata item is basically separated into two sections, one for statements and one for sitelinks. Both sections should be collapsible on mobile view and appear in the toc on tablets. The issues why MobileFrontend currently does not recognize our `<h2>` sections are the following: # For MobileFrontend, `<h2>` headlines must be a direct descendent of the `#content` element # The `<div>` containting the content of the sections must follow the `<h2>` directly which is not the case for the sitelinks section atm The two options we have are either changing the DOM structure of item pages to fit MobileFrontend requirements or make MobileFrontend less restrictive about what to recognize as a headline.

A Wikidata item is basically separated into two sections, one for statements and one for sitelinks. Both sections should be collapsible on mobile view and appear in the toc on tablets. The issues why MobileFrontend currently does not recognize our `<h2>` sections are the following: # For MobileFrontend, `<h2>` headlines must be a direct descendent of the `#content` element # The `<div>` containting the content of the sections must follow the `<h2>` directly which is not the case for the sitelinks section atm The two options we have are either changing the DOM structure of item pages to fit MobileFrontend requirements or make MobileFrontend less restrictive about what to recognize as a headline.