This task is about implementing an event that should log instances when people are prevented from switching from the Reply tool's source mode to the visual mode.
T256150 implements a new dialog that will prevent people from switching from the Reply tool's source mode to its visual mode if the comment they've drafted contains a template or a table.
This task will help us understand how often people are encountering this dialog/interrupt and subsequently inform how we prioritize implementing the new multi-line comment syntax that will be decided up on in T246960.
We would like for this event to be named, implemented and tested by 4-August-2020.
- An event is fired and logged that will enable to us to know:
- 1. What should this event be called?
- 2. What schema should this event be stored in?
|Person tries to switch to the Reply Tool's visual mode after writing a template in its source mode||dialog-prevent-template-show||VisualEditorFeatureUse|
|Person tries to switch to the Reply Tool's visual mode after writing a table in its source mode||dialog-prevent-table-show||VisualEditorFeatureUse|
- "Open questions" are answered
- Pre-deployment QA is completed
This is now done per T257501#6361341
- "Requirements" are implemented
This is now done per T257501#6350423
New events are added to the VisualEditor/Feature use data dictionary