Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T233443 [Epic] Reply Tool | |||
Resolved | ppelberg | T251654 Deploy Replying v2.0 as Beta Feature to partner wikis | |||
Resolved | ppelberg | T244500 Instrument new replying workflow | |||
Resolved | ppelberg | T252931 Instrument Reply tool v2.0 | |||
Resolved | Mayakp.wiki | T244498 Replies v2.0: determine what additional instrumentation is needed | |||
Resolved | DLynch | T252924 Add fields to VisualEditorFeatureUse | |||
Resolved | Mayakp.wiki | T252930 Post-deployment QA: Reply tool v2.0 instrumentation (DB) | |||
Resolved | Ryasmeen | T252927 Post-deployment QA: Reply tool v2.0 instrumentation | |||
Resolved | Ryasmeen | T252926 Pre-deployment QA: Reply tool v2.0 instrumentation | |||
Resolved | DLynch | T252925 Apply VisualEditorFeatureUse schema changes to all editing interfaces | |||
Resolved | Mayakp.wiki | T254291 Add additional events to VisualEditorFeatureUse | |||
Resolved | ppelberg | T255639 action: "window-open-from-tool" is showing up instead of "action": "external-link-input" when a user clicks on "Link" |
Event Timeline
Comment Actions
We need to go over the events for the mode-switching and ensure that they're firing appropriately.
A quick test on beta suggests that two things are obviously wrong currently:
- EditAttemptStep.firstChange fires every single time you switch to source mode if there's any content in the field (but not when you switch to visual mode, regardless.
- There's no event fired at all for switching between modes. It should probably be consistent with whatever fires to VisualEditorFeatureUse for a switch from VE to NWE, though because of the different architecture I imagine we'll have to manually trigger the appropriate activity. event rather than relying on it coming from a Tool.