Change Details

During the beta feature phase, we have had almost exclusively highly-experienced editors using the new workflow. It's possible that we will run into new issues when we enter "small default" and less-experienced users see our interface. I would like to collect some additional data to understand whether we're allowing data loss. After a successful merge, [] How many "other" chunks were selected but not edited, for which the "your" chunk included diffs? In case we can intercept abandonment, [] Were any textboxes edited before abandonment? [] How did abandonment happen? Cancel button, back button, reload, tab closed... [] Store the "your" text and other edit fields needed to reconstruct the edit (section title, oldid, base revision). I'm not sure which abandonment flows can be intercepted. Maybe we can tap into the "leave page?" popup. Our data should be sent using `sendBeacon` to avoid slowing down navigation. This is the default for MediaWiki event APIs, but we need to also prevent data collection when the sendBeacon API isn't available.

During the beta feature phase, we have had almost exclusively highly-experienced editors using the new workflow. It's possible that we will run into new issues when we enter "small default" and less-experienced users see our interface. I would like to collect some additional data to understand whether we're allowing data loss. After a successful merge, [] How many chunks were selected but not edited, for which the corresponding conflicting chunk included diffs? [] How many chunks were edited but not selected? In case we can intercept abandonment, [] Were any textboxes edited before abandonment? [] How did abandonment happen? Cancel button, back button, reload, tab closed... [] Store the "your" text and other edit fields needed to reconstruct the edit (section title, oldid, base revision). I'm not sure which abandonment flows can be intercepted. Maybe we can tap into the "leave page?" popup. Our data should be sent using `sendBeacon` to avoid slowing down navigation. This is the default for MediaWiki event APIs, but we need to also prevent data collection when the sendBeacon API isn't available.

During the beta feature phase, we have had almost exclusively highly-experienced editors using the new workflow. It's possible that we will run into new issues when we enter "small default" and less-experienced users see our interface. I would like to collect some additional data to understand whether we're allowing data loss. After a successful merge, [] How many "other" chunks were selected but not edited, for which the "your"corresponding conflicting chunk included diffss? [] How many chunks were edited but not selected? In case we can intercept abandonment, [] Were any textboxes edited before abandonment? [] How did abandonment happen? Cancel button, back button, reload, tab closed... [] Store the "your" text and other edit fields needed to reconstruct the edit (section title, oldid, base revision). I'm not sure which abandonment flows can be intercepted. Maybe we can tap into the "leave page?" popup. Our data should be sent using `sendBeacon` to avoid slowing down navigation. This is the default for MediaWiki event APIs, but we need to also prevent data collection when the sendBeacon API isn't available.