The custom one as-is is never going to actually be accurate due to
caching, with an implementation that was basically just a bad joke.
A more thoughtful implementation with rounding and stuff per the
winter prototype is probably in order, but that will require a
different implementation anyway (T182345)...
bug: T160647
Change-Id: Id2776d69a7d42b9907b4363977134fea48dc2440
Notably, content passed to Language::convert() needs to be escaped beforehand.
Spotted by phan-taint-check-plugin.
Change-Id: Id8a5f8bbe635e2f321882296e40dd0c41cf91a3b
modes
Mostly affects extensions that add stuff after the content with them
hook dealies, such as flaggedrevisions etc.
bug: T200729
Change-Id: I5c46af8f4cab20b04930a0e25d380ec040557bb6
Switching from a unique approach -- getting category names, querying
the database, and then building links -- to the standard
OutputPage::getCategoryLinks() fixes the display of redlinks (T175713),
display order (T197852), and perhaps other bugs in the subtasks
of T160645.
A downside to this approach is that categories will not be shown on
history pages, but this is consistent with other skins (e.g. Vector
and Monobook) not displaying categories on history pages.
Bug: T186089
Bug: T175716
Bug: T175714
Bug: T175713
Bug: T197852
Bug: T160645
Change-Id: Ifad999033e8448615128cba4d6386045a9fc749b
* display:flex for three-column
* float content and some voodoo for two-column (same as monobook)
Also had to slightly rearrange dom to make the latter work. Content
is now before nav in dom.
Change-Id: I7209eb21473877592d89f8471f8f8ed1f6b87851