Depends lightly on a patch to WikiEditor, which will hook up the logging there
for the case where the switch is happening from WikiEditor to VisualEditor on
the same pageload.
Bug: T221191
Change-Id: Ibafec77b2eabd3b3b3767472b7b5a40e3312bf18
New changes:
7f002809d Localisation updates from https://translatewiki.net.
599facff7 Restore inline slugs in source mode for cursoring
Bug: T225546
Change-Id: I28a08113d0c8b3b64b32c06b225b0b4038140758
If the translations of save/publish button messages like
'visualeditor-savedialog-label-publish-short-start' contain spaces
(e.g. in Bengali 'bn'), the button on mobile would wrap over two
or more lines, due to weird styles we have for the mobile toolbar.
Change-Id: Ieb439ae489ab7110b81382ffdcf0d3d3ad2f84ac
New changes:
f99a7cd43 Apply desktop contexts' line-wrapping to new mobile contexts
fad2671d3 Localisation updates from https://translatewiki.net.
262c84128 scrollSelectionIntoView: Code simplifications
a13c86033 scrollSelectionIntoView: Fix mobile logic
04774b03c Allow passing a pre-existing HashValueStore to getModelFromDom
1cf71b3f3 Catch errors from getNodeAndOffset
Bug: T202723
Change-Id: I41cf726dad38d4fe6647a1b760d66126fcee393f
New changes:
ee96c6334 Localisation updates from https://translatewiki.net.
2a9ff2c54 Localisation updates from https://translatewiki.net.
5facf5ef6 Localisation updates from https://translatewiki.net.
afe09ea26 Make annotationsAtModelSelection fail in fewer cases
f6278bba0 Fix clipping on label preview in link context
42717187a ve.ui.AnnotationInspector: Deactivate surface after closing on mobile
44556e8fd Move mobile context to bottom of page
Bug: T199617
Bug: T204733
Bug: T220633
Bug: T225541
Change-Id: Icd6de1d7e380a14444ddba2044553c8c13682706
mw.Uri requires undefined rather than null to unset a parameter;
null instead generates a parameter with no value (and no equals sign).
Our own code in ve.init.mw.DesktopArticleTarget.init.js parseSection()
can't parse that and causes an exception.
Change-Id: I783ea6b91c115b79bbd9deac6669bea0661139af
The EventLogging extension no longer uses these internal modules.
They were phased out as part of last year's "lightweight EventLogging"
project (detailed at T187207). Migration notes at T205744.
VisualEditor has migrated already, mostly. It still depended
on the existence of these module names for some condition guards.
* The subscriber for 'mwTimingHandler' was guarded by 'schema.EditAttemptStep',
but did not emit events of that schema. What 'mwTimingHandler' really
needs is the '*SamplingRate' variable for its call to 'inSample()'.
This previously worked because the variable and the schema are both
provided by the WikimediaEvents extension.
* The subscriber for 'activityHandler' had a separate schema guard. This
might suggest an intent for the code to silently degrade if WikimediaEvents
were to be changed to no longer supply the second schema, or for the code
to work for third-parties without WikimediaEvents if they register only
the schema. However, this subscriber too calls 'inSample()' and needs those
variables.
I've assumed for now that it is okay for these to all be guarded together.
Even if the schemas were to be removed and we were to forget updating this
code, the new EventLogging client degrades gracefully from this (no errors).
Bug: T221281
Change-Id: I260c25752c3becfe6e499813197fbf7a3dba88c3
* Remove animation for toolbar sliding into place. It now happens on
the fake toolbar in MobileFrontend shown before the real toolbar
loads, and our toolbar just transparently replaces it.
Bug: T217784
Depends-On: If21aa0ea619ec2500ce5fca6fe81eb27f26bb047
Change-Id: Ib6ff7594e1982d1b46e9ca89d6b9722d025e8207
New changes:
ca588de0d CommentAnnotation: Make deleteable
02eb9e835 Synchronizer: Fix defaultName config
4101ca058 Add removeEmptyLastChildOnEnter to CheckListNode
080317f9f CheckListNode: Flip margins based on content direction
df1dbd0c4 Localisation updates from https://translatewiki.net.
a55f5d7d9 Make undo concurrency-aware
Bug: T185706
Change-Id: Id2b993eb6efcb0dde0c7d1ea1fc6a6cf91bc0e43
Abandon warnings are already handled by the code in MobileFrontend's
EditorOverlayBase. Using window.history.back() causes that code to run.
Having a duplicate way to trigger them only results in inconsistencies
because our dialogs animate in a different way.
Bug: T222315
Change-Id: I19c5616a6aeecf0ac63f37a564ef44f11df010b0
