Should avoid more of the issues with unwanted appearance of mobile
layouts. Cutoff results in layout switch when sidebar becomes ~a
third of the total window width.
bug: T196213
Change-Id: I9b8baee5fe53316128f864e732c86750b4e5470e
This provides a device agnostic, persistent opt-out for the new responsive
functionality.
The preference will show up under the skin selector if the user has their
skin already set to MonoBook. I considered adding a new skin option to
the radio selector of skins, but that is probably unnecessary for the
majority of users, in addition to complicating how to differentiate the
two modes (Classic MonoBook vs. Modern MonoBook?).
Wikis that want to make this opt-in can control the default in the standard
way ($wgDefaultUserOptions), or hide it entirely ($wgHiddenPrefs).
Change-Id: Id22f8e5199ff2b15fd03c94097db5cdc7188f8b1
* Improve their accessibility by giving both links a full label
("Jump to x" and "Jump to y" instead of "Jump to: ", "x", "y").
This also makes things better for localisation.
* Use pure CSS for the toggling of the visibility on focus,
instead of relying on JavaScript. Especially given the
JS came from core's 'jquery.mw-jump' module, which is
considered technical debt per T195256.
* Use plain <a> links in the HTML instead of wrapped in a <div>.
This solves the long-standing problem whereby the margin
between #contentSub and #mw-content-text had to be awkwardly
negated and overridden.
Bug: T195256
Change-Id: I40a769ee3a822a5a9167ec1d144e6b151eb8e141
* Reorder ULS and Echo links
* Rename conditional module load hook to be more generic, and add
ULS module
* Remove .active bolding from dropdown
Change-Id: I7e746e7c5af8ffd7c4ca06742ab1fe6bc94ba531
Have echo just show the numbers instead of the badges, and add a
text link to special:notifications in the dropdown, as opposed to
entirely reimplementing the flyout layout
Change-Id: I072dbc2b7bf70b6675469e09e3beb3927e06d0f7
Dropdown menus and js interactiveness for people who like to pretend
we live in a modern era or something.
Does not actually support newfangled tapping and swiping stuff.
Does not properly support echo. (will follow up)
Change-Id: I27d50c320b1526b9d158016a0e8022567f78ccc1
* Add screen-mobile.css with basic mobile styles
* Force loading of screen-desktop on IE8- due to lack of
@media width support
* Add some new divs and a set of spoof cactions for jumping
around the page (what's js?)
* Replace cactions label with a more descriptive string (was
previously set to display:none regardless)
* Also add a set of icons for fixed widths for tabs and things
(icons-source.svg is the source file for the set, and includes
a few others that ultimately weren't used here)
Cutoff 850px. Desktop styles should remain unchanged, with
mobile remaining stylistically consistent.
Change-Id: I737a7447db1e44e0d6abaa4c07813295a5ac73a6
A proposed change (I737a7447db1e44e0d6abaa4c07813295a5ac73a6) requires
this not to require Less parsing. It was unnecessary to convert this
to Less when I could have just removed an `/* @embed */` annotation.
Follow-up to ac8b055693.
Change-Id: Iba82f57d4ba3e65c61a5ef795b3b8d9c3f164a39
The following sniffs now pass and were enabled:
* MediaWiki.Commenting.FunctionComment.MissingDocumentationPublic
Depends-On: I74374c49407dcb789ef8a9219158a9a773c09d81
Change-Id: I467662e17ee381fd433f548f21ddf651ae632d61
More helper functions, general refactoring.
Output structure is all the same, all existing attributes
maintained. Some new ones are added:
* p-personal now rendered via getPortlet; has extra attribs
according to all others rendered with it
* footer rendered with slight variant of getFooter out of
BaseTemplate; has extra language attribs according to that
Change-Id: I462d1222b0166956d3dce17fbceccf386e179e8d
Use .background-image() and .background-image-svg() mixins to embed
all SVG images, but not embed GIF/PNG fallbacks.
Change-Id: I807719dbf07749f4c942b4ba9b023440ca52a510
instead of just spitting it out directly
Also rename all of said functions accordingly, add documentation,
and start trying to make an actually cross-compatible version of
getPortlet() for BaseTemplate...
Output should be structurally the same. All existing attributes for
output elements are maintained; some may have new attribs added due
to more consistent render method (getPortlet). (Essentially, if one
item had it, now they all have it.)
New attribs include:
* id
* lang
* dir
* aria-labelledby
Change-Id: I0a7ca1b95c2ad03273ed9c713be0da694c94a176
Previously added some svg versions of icons and background images.
svgs have now been run through svgo and cleaned up per Nikerabbit's
advice.
Also slightly tweaked user.svg to better match raster version.
Change-Id: Icf7ad259366a7051c66e2b8d6ac229ef1f0388fe
The following sniffs now pass and were enabled:
* MediaWiki.Commenting.FunctionComment.MissingParamComment
Change-Id: Ic4db7a090578ee3a894b74e66284902db55ff724
No guarantees that these styles actually apply to anything anymore.
But at least the TODO is resolved!
Change-Id: Ibb43c044f50f026afa84a0151b113dd600956942
Part of the move toward responsiveness.
* Use mixins and variables!
* Vectorise existing icons
* Delete a rule or two that don't apply to the source anymore
* Consolidate similar colours into the same ones using variables
Change-Id: I2f0eb2b79cba01d8fa3a06298711e8af4d5508ba
Also:
* Convert main.css to less because I can't figure out how to do svgs
and fallbacks by hand
* Add gradient image to fit with book for really, really, really wide
displays (and move book background to globalWrapper to make it
actually work)
Change-Id: Ie6f5b6b87b475953274688fc4640f9fa17184fa4
Also delete unused images, since even if something is
somewhere using them anyway (looked, couldn't find
anything), it wouldn't be able to find them in the new
image location regardless.
Wiki.png, magnify, and link are all part of core and have
been for some time.
Change-Id: Id7a02155a5f1b207908c9c0c8f7519b6d3f9a886
