The hover effect is not a basic usability requirement.
Having this ancient cruft in our HTML depresses me.
Change-Id: I0ca5b3b6a6037a9ec733283c656996969cc020e3
The installer hardcodes and expects to find a "skin.vector.styles"
module in skin.json, so moving it into a hook broke the styles. Moved it
back into skin.json, and left a comment so future developers don't make
the same mistake.
The responsive code is now a separate module,
"skins.vector.styles.responsive", which is only added to the page output
if VectorResponsive is enabled.
Bug: T106747
Change-Id: I7540b7871531ef650e799f012477cef6cdd32fb7
Vector's own configuration properties should be fetched from
Vector's own config object, instead of core's config object.
Follow up: Ib611357bbce739b1d193abaf89c228ba52613d6a
Change-Id: I358a5c1876098a85d77e90b11b3bf4e77c0f6c78
The fields separator is a , not a ;
This is a common mistake, because it was in one of the first
blogposts that discussed viewports.
Change-Id: I0b88db484c906f3c717aced67360d0f899af8f1f
This functionality is off by default, behind a configuration variable
($wgVectorResponsive) by popular developer demand.
CSS/LESS code by James Hare, with tweaks and testing by Jack Phoenix.
Bug: T46387
Change-Id: Ib611357bbce739b1d193abaf89c228ba52613d6a
* Don't require a Config instance to be passed in the constructor,
as that breaks skins that extend it.
* Don't manually register the skin with SkinFactory, use $wgValidSkinNames
Change-Id: Ie8539027c17caff35c1fc52a56676763df667fd9
They do more harm than good.
We still have the "HD" and "non-HD" styles, just no smooth transitions
between them.
Bug: T85614
Change-Id: I52dd9883eb4e7df00f0613182d4adaa3f28fe5b7
Siebrand Mazeland
Ori Livneh
Kunal Mehta
Florianschmidtwelzow
Derk-Jan Hartman
Jack Phoenix
Chad Horohoe
Bartosz Dziewoński