in favour of mw 1.34 shared.css to avoid weird inconsistent visual
styles
Inconsistencies include: monobook-style boxes, random text resizes,
miscellaneous inappropriate colours, unexpected centering of text
Use 'toc' even though it also has weird monobook box styles because
the less/js/rl/php soup for the collapsing is basically a labyrinth
and I can't replicate that; just override everything back to
basically how it's supposed to be, style-wise.
Incidentally resolves T239914 for timeless due to also overriding
toccolours styles that come with the toc feature.
Also include a fork of commonPrint.css as an accompaniment to
shared.css, which willl now hilariously go full-monobook. Ish.
TODO: Don't just use an entire copy of 1.34's shared.css and
commonPrint.css as a workaround, and come up with a better
approach to the toc maybe? (T280747)
Bug: T280285
Bug: T280292
Bug: T239914
Change-Id: I2d600a7d9768942b331f0de1dd1183e438144ad5
place
Use mw-body-content, that makes more sense, assuming we can get it
off the stupid indicators. (Why?!)
Bug: T279951
Depends-On: I785bd09d01e3b004df2f0fb898d7d8f28180501c
Change-Id: Ica58593dbdb2b36004ba1343f91c6c12476d871e
* Put hover underline back on links, because wikimedians hate change
and also why not the entire point of the skin is to troll people,
let's do it right
* Adjust link colours for better distinction between hover, visited,
external
* Remove text labels from some obvious cactions (history,
addsection) so they're all more likely to fit on stupid pages
* Don't show empty languages toggle on mobile
* I'unno, catnip.
Bug: T181177
Bug: T181192
Bug: T265205
Change-Id: I6256d9e27d6019944987db62432b1b324d5c4b38
* Move images up to match helplink positioning, assuming standard
size of 20px
* Remove mobile header clear and let the float itself sort it out
if it even is long enough to matter (most are just icons)
Bug: T269550
Change-Id: Iaddab576b208f927c51c8f64b3e601fd89c0d710
YOU WANNA NOT MATCH THE CONTENT IN THE NAME OF MATCHING THE CONTENT,
FINE. I WON'T STOP YOU. FECKING AAAAARGH.
Because just feckin' matching the interface theme for top-level ones
would have made waaaaay too much sense... or, I dunno, taking the
average of *visible* backgrounds on the page to see if it's overall
light or dark...
But nope. Let's just use the body background, which is usually
entirely covered up anyway. How could that possibly go wrong?!
Change-Id: Ib31030815c947622aaad6340fbafbd6103fef21f
Avoid breaking legacy templates. What other templates were affected,
though? Was it just tables? Hopefully it is...
Bug: T181321
Bug: T269970
Change-Id: I2ce7d7b4344cc1b056feb99e47bd7f99959df454
* Stop images from overflowing on desktop as well as mobile (folks wanna
overflow, they can load it sans skin, dammit)
* Firefox's stupid scrollbar colours
* Merge js into single module for desktop and mobile so it doesn't
randomly break on the wrong devices, and something about too many
modules anyway
* Weird footer padding?
* Weird WikiEditor/CodeMirror fonts/sizing
Bug: T256105
Bug: T247325
Change-Id: I8142c505534869c2530a915cfe8cef56303be6ed
This will only work with recent versions of core, but will not
give an error for older versions that don't have the
'mw-watchlink-temp' class.
Bug: T258674
Change-Id: Ia3d7732160dd0d8358ed12bd2c7ad08db16aa773
Apparently getFooterBlock never actually made it into core, so copied
out of Example.
Bug: T254266
Change-Id: Id62319314937080b99f2b93fd7b7fa62527d8fe7
Use normal `background-image` properties with SVGs now
that IE 8 and Android 2.1 is removed from Grade C.
Also removing all PNG fallback images.
Bug: T248062
Change-Id: I27d95241b6512f36985f7269122802d7b0962042
* Remove Liberation Mono from font stack; comes out excessively light on
hidpi chrome, to the point of unreadability (and probably is not a local
config problem beyond merely having it installed at all, as chrome
overrides normal font rendering settings regardless)
* Kill double border on pre styles; doesn't match other such boxes (notice,
warning, whatever)
Change-Id: I7a95931bd6af4efc880c3ee8f37a91d61f3e6539
And put the position:relative on that. Keeps the sticky header out of
it, regardless, and let folks do their weird non-content voodoo on
stuff like the siteSub more consistently, I guess...
Bug: T231400
Change-Id: I7ac35f741210a0c54976f43d2294af8f123967a1
* svgo on everything
* Line up some pixel borders more
* Use transparent for the grey amount
* Fix a couple of overflows on icon css
Change-Id: Ic56b65d71ae08cf71048ad5efdfa7e65a749f680
* No columns, so no point aligning anything to column-widths here.
* Add some IE9 fallbacks because the entire header is now flex.
* Clean up, consolidate same styles, etc
Bug: T184998
Change-Id: Iecf99d093a689d3c32932b2603f16939127ce7bd
Use a file upload onwiki for simplest approach, or specify srcset info in an
array if that's not an option or otherwise not desired.
For instance to just reuse a $wgLogo and $wgLogoHD already set for a 160x160px
logo, but where the HD versions actually come out the right size:
$wgTimelessLogo = [
'1x' => $wgLogo,
'1.5x' => $wgLogoHD['1.5x']",
'2x' => $wgLogoHD['2x'],
'width' => 160,
'height' => 160
];
Or to use File:Cows.svg uploaded onwiki:
$wgTimelessLogo = 'Cows.svg';
And the same thing with $wgTimelessWordmark to replace the site title string
with an image version.
Fallback behaviour remains unchanged, if just not using these.
Bug: T132004
Bug: T230663
Change-Id: I0d7b398935045ba69462252d40832ed95ad2d5ed
Partially reverts I148707085059f458512d328c415ea0bf134163f3 plus some random
cleanup and stuff
Both of the following bugs involve wikibase stuff so I can't actually be entirely
sure this resolves them, but I thiiiink it does because it should be killing the
offending parts of the above change that caused this? Probably?
Bug: T231256
Bug: T231234
Change-Id: Id7c0d90a805450b577271a321572fcd552ecbc3e
It's sort of attached to it regardless; might as well make it clickable
(especially since the first one is going to be shorter usually regardless)
Change-Id: I40f02240c0c6e447a7042546a0392a52a0f4910c
throughout
* Still need to redo how we're using mixins, but whatever.
* Cleans up a bit from the edit/view source etc changes too, since now
we have a little more context (oops)...
* Just hide 'view' in general because a, how much does it really add,
and b, it doesn't fit in a lot of cases when we have the extra width
from these icons regardless.
* Rename view and add section tabs to make more sense with icons/in
context/whatever ('view' is now only targeted at screen readers, and
we use a + for the new section icon, so saying 'add' is kinda...
redundant)
Bug: T197520
Change-Id: I1ab12ccda60e51035c4adec43c42508ac297c00a
We put overflow:hidden on headers so the underline doesn't undercut
thumbs weirdly; this results in actual stuff getting chopped off at
times as well. Main example is burmese, which does line heights a
bit differently, such that overlap is kind of expected.
Solution: move underline to its own pseudo-element. May fix some other
stuff (extensions?), or just as likely break them. Only bother with
parser output because I can't even think of anywhere else we use such
floating to begin with.
Bug: T195822
Change-Id: Ib17b444b2d8720ede860e42c72c8c69e62a9f4ac
* New icon for edit source as variant of normal edit icon
* Use old brackets icon for view source instead
* Put icon for editsection links outside the links themselves and only use one
for VE when there's two links
Bug: T173531
Bug: T229184
Change-Id: Ia178c487c8e6c175944868646d36064ebde8182c
No more need to add in an html pokey element every potential dropdown menu.
Aaaaaagh that made it bigger, didn't it.
Change-Id: I5d3817aa026849a5304710a32a3585f3e698321d
Ed Sanders
jenkins-bot
Isarra
Sam Wilson
Volker E
AronDemian
Kunal Mehta