I82db33d656 in core changes the toggle button of the TOC.
This change removes the brackets around the new toctoggle, too.
Depends-On: I82db33d656b3795d7134a91d20ed9d93a3471086
Change-Id: I7a9fa9f3a630901d736331ecef2c43e3ab918d03
overflow:visible so line goes properly under indicators, help
thingies, wikipedian user icon spam, etc.
Change-Id: I5d626884b13449b8d1351fe4e9a94b3ee99baf80
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
Override the inline style `width: 0px` on .oo-ui-clippableElement-clippable
elements within .mw-echo-ui-overlay.
Also adjust some other styles for the callout, so that it stays within the
screen width, but is not any wider than it would be otherwise (500px).
Doing so causes the anchor triangle at the top to not align with the
relevant notifications icon, so it is hidden with `display:none`.
(On a narrow mobile screen, it doesn't seem to serve much purpose anyway.)
Bug: T197064
Change-Id: Iaedde85b5c31ab244d4f72c54c9aad6a1b4ebb73
Accidentally removed an unrelated thing; am too out of it right now to submit a followup putting that back.
This reverts commit 138036882f.
Change-Id: I1dcd0a887de8bc4423fc5e166e465873c1549a1a
Does not appear to work, and is possibly breaking things elsewise as
well. In particular: chrome text selection in general, possibly iphone
support?
May or may not resolve the following; please test (does seem to
effectively resolve T183215, for now, at least, but dunno at all about
the other two.):
Bug: T161470
Bug: T183215
Bug: T188387
Change-Id: I2d4aae98fe47bce5a873bc44b6cea58f111f5086
* colour bar for header now only has number of colours equal to
columns underneath it
* h1 and h2 now have grey underlines instead of blue
bug: T182388
bug: T132000
Change-Id: I883bcfa872d6306c04418230c3f7034e5ec9f188
elsewhere in mw
* Bump max content width up to 125em because why not
* Make fixed-width padding a bit less
* Basically just follow WikimediaUI Base breakpoints as appropriate
while keeping content similarly wide across devices
Bug: T165945
Change-Id: I8afb30bc1fb24907f94195b31289a664c050fcc4
Table layout is much better in combinging wrapping, using as much
space as available and floating content at the same time.
This is similar to how we do this for all our skins
Change-Id: I23408d1aa6773af05f2ee197356a9b04feb524f0
These OOUI widgets are special in so far that:
* OOUI makes the actual <input> element invisible and partly fails
to do so because Timeless sets properties on <input>s that are not
reset by OOUI.
* An outer <div> is styled like an <input> instead. Timeless is not
aware of this and forgets to set it's overrides for <input>s there.
This patch is motivated by the AdvancedSearch extension which uses
these widgets, but is not limited to this.
This patch also does not fix all compatibility issues between Timeless
and these OOUI widgets, but greatly reduces the main issues. More to
come in later patches.
Bug: T192303
Change-Id: I8a4fc3f74dabdb54fd95cd133bb4fe28944c4a40
Translation updater bot
Fomafix
jenkins-bot
Isarra
Jean-Yves Le Gallou
evad37
Jack Phoenix
RileyBugz
Paladox
Kunal Mehta
libraryupgrader
Bartosz Dziewoński
Volker E
Derk-Jan Hartman
Thiemo Kreuz