We already have wfUseMW( '1.24wmf6' ) so we don't need this any more.
The messages list for oojs-ui had gotten out of date, and rather than
fixing it I figured we should just remove this conditional registration
code altogether.
Change-Id: If0610beb2df8bd85aeba136530a84a793e3dda64
New changes:
32c7edd Localisation updates from https://translatewiki.net.
c7d61bc Round up height of language inspector widget
9473d2f Localisation updates from https://translatewiki.net.
2cffb4d build: Update grunt-jscs (formerly grunt-jscs-checker) from 0.6.0 to 0.6.1
b3f861e Localisation updates from https://translatewiki.net.
76b7992 Localisation updates from https://translatewiki.net.
76f8e90 Make the re-render flash more prominent
d2506a3 Localisation updates from https://translatewiki.net.
244bf0e CommandHelpDialog: Make closing action 'safe' not 'primary' for consistency
Change-Id: I68db9bdfa6078d4ab3b110e140c413fc6b865c1b
It's unnecessary, big and ugly, way too close to an actually useful button, and
adds oodles of complexity to the mire that is VPT without significant user benefit
whilst taking up an unjustifiably huge amount of the already-over-burdened space.
This means that the minimum browser width for English on default Vector to show
the toolbar correctly is now 945px, down from 1029px.
Bonuses: fix MWCancelConfirmDialog's cancel button to be destructive (it is) and
remove a now-recently-fixed comment asking for the save button to be styled using
a generic class (provided by the constructive flag).
Change-Id: I30dc7020121f0dd6907b61ef674a7cb14eb00652
Closing a dialog with specific data means closing it again with
potentially different data, while the dialog is already closing, means
someone wins and someone looses. Silently failing in this case is bad,
because if the first close call was a cancel, producing no side effects,
but the second close call would have produced some side effect, the side
effect would never occur.
The problem here really was that the save dialog needs to be closed
before we can destroy the surface so we can uphold the assumption that
hold and teardown processes are operating on an attached DOM.
The solution is to automatically close the save dialog on teardown,
rather than on save. Since save triggers teardown, this has and identical
user experience.
Bug: 68048
Change-Id: I669448739f168737d4eddd6496189a819ce894b1
New changes:
8bb3848 Bring back global/local specific CSS classes
Local changes:
Use global overlay class to target the z-index hack for the Vector skin.
Bug: 68066
Change-Id: If1b6ba0c9035ff32b61d34ee779a95554883a2ec
New changes:
77dd12e Prevent deletion of focusable nodes by typing
da66427 Update OOjs UI to v0.1.0-pre (97dbb50137)
Change-Id: Ia6d83495a523106e92b184c8b60f815d3739d1fa
Attach event listener to the alternate text and the media size widget
in the MediaDialog, so that when either of those are changed the
'Apply Changes' button is enabled.
Related to I88c3f3dcc7667b3ffdd2a8a8433cb47b82ba1531
Bug: 67684
Change-Id: I03efbed2f9b2909b055d96b9ae1e27b6d5e2bdbf
