New changes:
aec8d85c5 build: Upgrade eslint-utils dependency from 1.3.1 to 1.4.2 for security issue
Change-Id: Ia2e5f94899fbb6d3ba036d820df95a3149df0a03
New changes:
13477446b Localisation updates from https://translatewiki.net.
9ef837943 GeneratedContentNode: Re-apply model selection if DOM node count changes
45c37f702 ve.ce.Surface: Don't request offsets that are out of bounds
Bug: T231085
Bug: T231094
Change-Id: Iad370402c5645a0ed4078977155815a95715dab5
New changes:
2e37aaea7 Localisation updates from https://translatewiki.net.
85011b54a Utils: Move ve.supportSelectionExtend to client-only utils
077dfaa59 ve.dm.Change: Remove no-longer used doc argument from #deserialize
586a91bc5 ve.dm.Change: Fix serialize to be recursive
Change-Id: Ia70f2a663899972e35ac0b077465f946ebc49ffc
New changes:
77076f828 LinkAnnotationInspector: add a "label" field on mobile
Local changes:
* Updates for mobile link label editing
Bug: T229431
Change-Id: Ib0489f6f59b228ebc4a20f7a0a515be938a8f6d3
When saving fails for a reason we don't handle explicitly, the error
message will have HTML formatting and will respect any on-wiki
overridden messages, rather than being plain text generic message.
Extensions providing custom SaveErrorHandlers may need to be updated.
The only one in Gerrit that requires a fix is TitleBlacklist:
Ibeae79c95557a7af699716c9d921f34c310bee6d.
* Remove handling for errors returned in .visualeditoredit.edit.info
rather than .errors (.error in old format). AFAIK this is only used
by some extensions, it is probably incorrect to do (T229539) and all
extensions I know of that do this (AbuseFilter, SpamBlacklist,
ConfirmEdit) have custom SaveErrorHandlers.
* Remove custom error messages for 'readonly' (identical to API
response) and for 'hookaborted' (very unhelpful and there is a
chance that the API response is better, if the extension causing
this error generates any error message).
* Add a silly shim for MobileFrontend integration, because we allow it
to handle error responses, and it expects them in the old format.
This is probably subtly wrong in many ways, but MobileFrontend code
only uses this for logging, so it shouldn't explode. In the future
we will hopefully change it to use errorformat=html (T228897#5366960).
Bug: T229532
Change-Id: I3b9c4fefc0869ef7999c21cef754434febd852ec
A @method annotation is only necessary when the docblock is not
directly followed by a function declaration (in which case JSDuck
assumes it documents a property), e.g. when defining an abstract
function or referencing a function from another library.
I verified that JSDuck generates exactly the same output before and
after this change (docs/data-<hash>.js files are identical).
Change-Id: I7edf51a8560ab9978b42800ab1026f0b5555c3bf
New changes:
92b32ff5e Localisation updates from https://translatewiki.net.
43950656f Rebaser: Listen to surface history event, not document transact event
3847440a4 Localisation updates from https://translatewiki.net.
5e3e913ea Consider focus, not anchor, in ve.ce.RangeState
56378e975 Prevent RangeState tests from hanging QUnit via a huge diff
Bug: T230814
Change-Id: Ib1f238c4800e3acb581122cbb999a8e59dd5b2c5
New changes:
62f06382c Localisation updates from https://translatewiki.net.
5fc25c0d9 LinkContextItem: Apply ellipsis directly to link
Local changes to fix link ellipsis styles.
Bug: T230267
Depends-On: I25bb4fa9b7288232b08bab9c88f281817a26d6bb
Change-Id: I8a4b04d45979a1f6c375a7c92a340e3e81d7753c
The .oo-ui-popupToolGroup-handle styles only need to apply to the
editTools toolbar, where they override OOUI styles so that our
"stretched" toolbar works; they don't need to apply to the pageTools
toolbar, which contains just the editor switcher, and where they make
it look different from the MF wikitext editor toolbar for no reason.
Change-Id: I21315b34be0a7c3938f84ada720ff5754d953879
New changes:
1375d1500 Document that toJSON takes a key argument
27056b919 Localisation updates from https://translatewiki.net.
aa52f476f Only create context footer on mobile
ab6d942c5 Deactivate surface during replaceAll
aae84a489 MobileContext: Ensure isVisible returns true while opening
Bug: T229734
Bug: T229879
Change-Id: Ic03c22a785a2e9e8a4d38c17789ea2d4f16ef3ed
New changes:
cd5e54f78 MediaSizeWidget: Make methods chainable
1606e2dd5 Localisation updates from https://translatewiki.net.
5a2f5fdb5 ve.ui.AnnotationInspector: Select inserted elements (not text) after inserting
6f2206ee2 Fix ve.dm.Change#toJSON to cope with arguments passed by JSON.stringify
7c78f1db7 Document ve.dm.TransactionProcessor#process better
Bug: T227630
Change-Id: Ic79e8bb8ef9a6288d80b591a83bf43cafc83743d
New changes:
d6d0ff8ce Localisation updates from https://translatewiki.net.
f57c6344c Move common code from FragmentDialog and FragmentInspector to FragmentWindow
a7d95c35b build: Bump lodash for npm audit
Change-Id: Ide09983d0b8c2006b25ab257fc048416a83b50c6
We were incorrectly always adding action=edit to the URL in that case.
The condition was always passing because `this.section` is `null` when
unset, but `this.currentUri.query.section` is `undefined` when unset.
This is a similar fix/bug to a68cc38b22.
Bug: T209163
Change-Id: Ic80ac377b763aea53678c4209ba6b3a6ba2996c9
