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
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
New changes:
5810e0cd4 Update UnicodeJS to v12.0.0
145991ded Fix file list on demo page
53e69bf14 SurfaceSynchronizer: Force websocket transport
Bug: T201531
Bug: T201532
Bug: T201533
Bug: T201534
Change-Id: I96beb31df55b41bf1d259f5e6964245008face22
* Change the query in ve.init.mw.ArticleTargetLoader#requestParsoidData
so that in non-RESTBase mode with wikitext it still returns the
metadata required to initialize the editor, using the backend API
code added in I1b35b28e428a1f86d2e34d90ddbe73361ce14818. This fixes
the exception from T222312.
* Introduce new configuration option $wgVisualEditorAllowLossySwitching
to control this feature. It is enabled by default, fixing T214542.
We allow it to be disabled because switching in non-RESTBase mode may
cause "dirty diffs" (non-semantic changes to the wikitext), which are
undesirable on wikis where users carefully review all changes.
Bug: T214542
Bug: T222312
Change-Id: I58879cba5612002c70c24731306214d2577c2c52
Section=new behaves more like a form than a full
document editor, so allow focus to be fully moved
to the title input without leaving a deactivated
cursor behind.
Change-Id: I7e3835da925b27f5df79dcbdd4550445795cdc51
In general action=edit could be bound to a wikitext-specific
edit link, but in the case of redlinks we can use the
preferred editor instead.
Bug: T223793
Change-Id: Ib0851e9e2ce441ae93311153801e2c3de0a2063d
New changes:
c843549bc ve.ui.Surface: Remove unneeded code handling mobile dialogs
9d530f337 Don't show mobile table context on desktop
Bug: T211240
Change-Id: I8975279f4ee29eb290c6b6238a8106077857635f
New changes:
68b031087 ve.init.Target: Fix errant call to setSurfacePadding, not setPadding
Bug: T224255
Change-Id: I19db16ec5849968f48658e4149bf7410b58ece5e
