This was causing a regression in the behaviour that takes you
to the external link tab automatically when 'http://' is typed,
as internally it is normalised to 'Http://'.
Bug: T112158
Change-Id: Id7cff07e89caafe5b350f4fb27b99c6c89498990
New changes:
4a089dd dm.Annotation: Remove unused convenience wrapper
f30ad5c PreviewWidget: De-duplicate code with a private function
c16da30 Restore scroll immediately after paste
45b1406 Links: Explicit entry/exit with cartouches
Change-Id: I48ad7fb3f68ebb5eff89cc7e2b00878cca550222
New changes:
184f952 [BREAKING CHANGE] ve.dm.Converter: Put static things in .static
a4c1e1e Localisation updates from https://translatewiki.net.
Local changes:
* Switch to using Converter's newly-static methods
Change-Id: If30f7b2a0de92c4c7f4d5ca57663251c132eeed2
If VE is enabled for consistency edit section links become edit source in all NS.
This patch fixes it to be done on the backend for namespaces where VE is not enabled
(instead of user side) to avoid noticeable flickers on page load.
Bug: T112366
Change-Id: Iba090bfc1b2ff4886fb0cf2b37db7870b6be792d
New changes:
63f6b71 build: Upgrade grunt-banana-checker to v0.3.0
a88b6d6 ve.resolveAttributes: Use addBack to build a single selection
ce39ef0 FindAndReplace: Only use caseSensitive for text matches
Change-Id: Ibddf90531709aa8951b3ac8ffcf225ca6410eb51
Drop beta-ness as users don't care and it confuses them. Leaving the preference
alone for now.
Bug: T99963
Bug: T112354
Change-Id: I0e039dec54d528fce24226e76b931b593dd13a9e
New changes:
0534de0 Localisation updates from https://translatewiki.net.
de0803c Localisation updates from https://translatewiki.net.
e0842b2 Add new krl language
61e0589 ve.dm.Scalable: Create unit tests
761d817 Localisation updates from https://translatewiki.net.
8c6b9f1 Follow-up 761d817: Fix build for added language 'olo'
5980634 Use removeChild instead of remove
d9bfb72 ve.dm.SurfaceFragment: Add more unit tests
Change-Id: I886c7427e53bd30d9518b6f868107a7b3cca7b54
The loading progress would not be reset upon failure, causing issues
when you tried to start loading again.
Bug: T96437
Change-Id: I7ec4be82304c101fa1bd634f60bc6b0047e2d53d
New changes:
417473d Slightly increase width of table context
ab7544c jquery.i18n: Add missing dependency on PluralRuleParser
01dda9e Update OOjs UI to v0.12.8
4d9c68e Use a 'larger' dialog and 3 columns for keyboard shortcuts
cfacd18 ve.ce.Surface: Wrap internal drop's insertContent in a try/catch
Change-Id: I1a9cd4cea16682a8eaabfa4c5551fc0acd8b666d
This only comes back in results from certain modules, so I'm not entirely
sure whether we want to do this in here or mw.widgets.TitleInputWidget.
Bug: T111598
Change-Id: If2916706db359d520c41c2dec7ded44e0d3a56a9
During testing of saveFailure for T110272, I noticed these were showing up as broken
missing messages on mobile.
Change-Id: I20ce66ba180b6f40443ba7a9a7a0da3de3b4e6f3
New changes:
6e5d335 sa.DesktopTarget: Clean up handling of actions toolbar
52a609d ElementLinearData: Add extra check to hasContent
97742c0 Allow shift+delete to cut on non-Mac platforms
Change-Id: I2a46c4a5e46fcc339b3686ce88f4137c74017d87
So many old keys not yet removed. Oy. Also, disable disallowDuplicateTranslations
for now as this fails so much.
Change-Id: I52e1555335a6e64b1e9db541ba726cf6ce8c7dd0
Right now .initialize() doesn't do anything other than enable
the window resize handler for toggling the "narrow" styling,
but as a matter of principle we should call .initialize()
on toolbars after attaching them.
Change-Id: I419c943d1d20af2105b84b8f5fbccc7070af601b
