| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Removes a CSS selector that is only used by Vector and makes red-links
in the personal menu a slightly different color than other red-links
in Vector (which are styled by rules in legacy.less).
Bug: T282884
Change-Id: Ie04182da57c968b34401a3811ce715424eaa181d
|
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Refactor CollapsibleFieldsetLayout to work when not wrapped in
mw-htmlform-ooui-wrapper.
Bug: T278935
Change-Id: I89c17671de1c1c8b5897a75ad292c576a1e1bbb1
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Register whatwg-fetch (by GitHub) as fetch polyfill to MediaWiki core,
with a skip function. This adds fetch() support for Safari 6.1+ and
IE 10+. The polyfill depends on Promise being defined first.
Bug: T260198
Change-Id: I610da8abd6334de965f9c763462b563822788eb2
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When a PHP exception occurs, its error message is usually displayed
in a standard error box. However, error boxes were hidden on
Special:RecentChanges and other changeslists. That code was meant
to only hide a single error message on Special:RecentChangesLinked
(see 82622146f87a3e3e5e6a0c7bf36fa87d954be493, where it was added).
Change-Id: I386c88edd22a07d09520bc7878cce1093f986faa
|
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
SVGO v2.x changed configuration to JS, amending configuration.
Adding new 'minify-svg' npm script.
Also re-crushing SVGs.
Bug: T278656
Change-Id: I1d746fca051cbc00900a05c33e8a401f95848930
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A”/“C”
Moving towards better explaining language on browser support.
Change-Id: Ib9457e0345a1805412a4c4df5aabb426e26264d2
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously thumbnail styles were split between the legacy and content
modules. The styles in legacy were concerned with layout only for example
floating and text alignment.
When migrating styles from legacy to a new feature called
`content.thumbnails` for backwards compatible we imported the entire
feature. On hindsight this was a mistake.
This had the impact of loading thumbnail styles on skins that did
not want those styles, with Timeless being the most known impact.
It is proposed we reconsider the patch in c504f19f1fa and instead
give proper backwards compatibility to skins.
Bug: T280292
Change-Id: I4464eb9195f63f27ea56d9b7baff02b45f3c3a13
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
1) Rename content-parser-output to `content-body`
Widen the scope of this module to apply to anything that can be rendered
as the article body. Improve the documentation on what is allowed here.
For early-adopter skins already using content-parser-output,
map the feature to the new name and add tests.
2) Reclaim the `mw-body-content` class for result of
SkinTemplate::wrapHTML
The `mw-body-content` has been used in skins to wrap various elements.
Going forward we will use it to wrap any HTML content generated by
OutputPage.
See dependent patches, which we're not directly depending on to avoid
a CI gremlin:
- I90d85c21f4a62e6697f24e3ce388445a0a53c2b0 (MonoBook)
- I11242e243c9a529b72972089af9ac2a8c906331a (Modern)
- I87942c60e62f6f14acdfeaa1836ace4eac9252ac (CologneBlue)
- I4c1b15d90bacbc9b13782a1d8f52e838ce8ecd83 (Vector)
Bug: T279388
Change-Id: I3a91b294fcb3724cd46743e497dff723de0490a6
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Follows-up the packageFiles converstion in I8f47be7d9929a1.
Separated to aid in code review and git attribution tracking.
Also:
* Fix mistake in the `set()` docs which referred to a non-existent
`clearVisibleTimeout()` method instead of the `clear()` method.
* Improves documentation a bit.
* Use clearer variable names to distinguish between IDs for native
timeouts and our own IDs for the "visible" timeout wrapper.
Change-Id: Ifdc711b1d19b9bc982ac38134f030b98e5e93032
|
|\| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I8f47be7d9929a1802b6b70bc5b9570a00eb446fa
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Firefox up to v15 has fallen out of basic browser support.
Bug: T277803
Change-Id: I4733a77d9f752f9ca4fe6b95be57f7e323c33694
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Firefox up to v15 has fallen out of basic browser support.
Bug: T277803
Change-Id: I44691d364d3cbbc58b5d21f033b7ec375e33f551
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I442ad6cbe8f3a5a2cf642c6d9c313d040e408246
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
updateBlockOptions() was unchecking all action blocks whenever
it was run and it's run any time a value changes. User inputs were
being lost if they didn't select actions last. Remove that
code from the update function.
Bug: T282177
Change-Id: Id06d172afb1998f9bd32ea0b7cb39d42b2e94d11
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Although this was targeted at somewhat discussable “interface” usage
of textareas, we already feature other “Wikimedia” opinionated styles
on elements in 'elements.less'. These will be simpler modifiable by
skins in future with variables.
Combining the rules simplifies mainentance.
Bug: T255717
Change-Id: I65f4325f42c859ce4d547258ed9d6cee8c0f0f7d
|
|\ \ \ \ \ \ |
|
| | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Amending design slightly to be closer to standard look as in OOUI.
While at it also remove code commented out for years.
We've rewritten already all lines of code in this CSS file in last
11 years, it doesn't make sense to leave these lines in to remind us
of some ancient upstream state.
Bug: T281941
Change-Id: I3434871d64ab82ddf00d117ce5213641f4fedb26
|
|\ \ \ \ \ \ |
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Firefox up to v26, Chrome up to v30 have fallen out of basic browser
support.
Bug: T277803
Change-Id: I5348b3574e95d6fb5ac666e20a90f029246f8b45
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | |
| | | | | | |
style"
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: T277803
Change-Id: Id9d135a5a44a5b4c58abd55213296b37d2df0198
|
|\ \ \ \ \ |
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
`list-style: none none` was a workaround for an IE 6 & 7 rendering issue.
Same goes for `list-style-image: none; list-style-type: none;` combination.
Let's unify to shorthand `list-style: none` for any non-ancient browser.
Change-Id: I05f00db8a08a9fc1523ea00fab91e91d3c00cab3
|
|\ \ \ \ \ |
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
Change-Id: I0073f758f67d4c3f85211439d43217aa99e7c8cd
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
`bottom` has no rendering impact on `position: static`.
Change-Id: I9fd0e16ccd6dd799af6aa78c923cd8e9f032a08e
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Removing code that applied only to now fallen off basic support browsers
after T266866.
Bug: T277803
Change-Id: Icfa3119877058a8810d0a1b1a1f8196f14937fa3
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Firefox up to v15 has fallen out of basic browser support.
Bug: T277803
Change-Id: I961dd9ee8b3e28f9cfca57df73f57c56fe88c5f9
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is similar to that we did for jQuery 1.9 Migrate in 2014 when
we upgraded from 1.8 to 1.11 (T46740), and this will likely be the
last patch in this series that's suitable for backporting to stable
releases.
After this, we'll start janking stuff out during the 1.37-master
release, slowly working toward its removal.
I've removed the patch file for now since we're far from the original
now, and if any changes do get released by upstream for migrate 3.x
in the next few months we'll have to apply by hand either way.
(Yes, I'm volunteering to do that.)
* Remove needless window.mw guard.
I think I copied this from our jQuery 1.9 migrate patch,
when we started the jQuery 3 migration, not realizing that by
now mw.loader and startup no longer depend on jquery.
jquery is loaded by an mw.loader callback (as evidenced by the need
for the window.jQuery lookup pach), so mw.track always exists.
If it doesn't we have bigger problems.
* Remove migrateTrace code instead of disabling it.
* Change `jquery-migrate` to `jquery_migrate` in mw.track call.
Otherwise, the name gets transformed into an underscore later on for
Prometheus, Graphite, Statsv, etc. WMF: in WikimediaEvents/statsd.
* Improve PATCH comments to state upfront whether they change, add,
or remove something (makes it a little easier for me if/when
this needs to be rebased).
* Fix duplicate "JQMIGRATE" prefix in cssProps warning.
Upstream ref https://github.com/jquery/jquery-migrate/pull/424.
Bug: T280944
Change-Id: Ieecf02982468f1c576d2c56b43dcd59d5255bf20
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug: T281228
Change-Id: I8a7f864f3101367bc290cb99b9d0c63876ad89a9
|
|\ \ \ \ \ \ |
|
| | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This also tries to centralize adding logic of adding history-deleted
class as well. To make future changes easier.
This doesn't affect history deletion on files, recentchanges, and logs yet
Bug: T23272
Change-Id: I08f14f712479e1b170c606e2b64857f8386acd76
|
|\ \ \ \ \ \ |
|
| | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This adds a new type of block restriction for actions, which extends
AbstractRestriction. Like page and namespace restrictions, action
restrictions are stored in the ipblocks_restrictions table.
Blockable actions are defined in a BlockActionInfo service, with a
method for getting all the blockable actions, getAllBlockActions.
Action blocks are checked for in PermissionManager::checkUserBlock
using DatabaseBlock::appliesToRight. To make this work, this patch
also removes the 'edit' case from AbstractBlock::appliesToRight,
which always returned true. This was incorrect, as blocks do not
always apply to edit, so cases that called appliesToRight('edit')
were fixed before this commit. appliesToRight('edit') now returns
null (i.e. unsure), which is correct because it is not possible to
determine whether a block applies to editing a particular page
without knowing what that page is, and appliesToRight doesn't know
that page.
There are some flags on sitewide blocks that predate partial blocks,
which block particular actions: 'createaccount' and 'sendemail'.
These are still handled in AbstractBlock::appliesToRight, and are
still checked for separately in the peripheral components.
The feature flag $wgEnablePartialActionBlocks must set to true to
enable partial action blocks.
Bug: T279556
Bug: T6995
Change-Id: I17962bb7c4247a12c722e7bc6bcaf8c36efd8600
|
|\ \ \ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Exceptions from one mw.hook handler should not affect another.
This expectation stems from how other systems work, such as
jQuery.ready, Promise, and DOM event listeners.
mw.hook used to be a shortcut to $.Callbacks(), which is the same API
that powers jQuery.ready and $.Deferred, but it is lower level and
before such error handling is used. With commit 9f23dfa47b4 I have
replaced with with a simple handling of our own with just the part
we need, and this commit improved that implementation with error
handling.
Bug: T223352
Change-Id: I380b93ab3de1b3b7e5f0c5effa2e367fa9b1e6f3
|
|\| | | | | | |
|