@MNeisler Correct, they will be under event.feature='preview'. They would follow the same logic as other Realtime Preview events logging: https://gerrit.wikimedia.org/g/mediawiki/extensions/WikiEditor/+/6b1698d40822f72a450a9f3b54e41b676d9e42e0/modules/ext.wikiEditor.js#262

Hi @ppelberg ! I've updated the ===New instrumentation section and it's ready for you and @MNeisler to review. Please let us know when we can proceed with implementation. Thank you for guiding us through this process :)

In T306176#7898379, @Samwilson wrote:

How often are users opening and closing the Preview window inside the Wikitext code editor?

We can use the existing preview-realtime-on and preview-realtime-off event actions for this.

How often are users being defaulted to the Manual Reload experience rather than the auto-load experience?

For this we need a new action. I propose preview-realtime-stopped.

Which method are users opting for previewing their edits, shortcut or button?

Two new actions required: preview-realtime-reload-click and preview-realtime-reload-accesskey. (We are able to determine which user interaction is used to fire the reload.)

What's the average load time for a refresh?

I'm not sure how a time duration value should be stored. Perhaps there's an existing system for this sort of thing, or perhaps we can extract this info from other existing logs (e.g. the parse API? although of course that'd include other usages).

How often are users encountering the error view?

Errors are already logged, so we should be able to extract their frequency from existing logs.

---

So two questions for Analytics: Is it okay to add these three new actions? And how should we store the preview-load duration times?

We can use https://larynx.theresnotime.io/openapi/ as the TTS engine API for now.

We can use https://larynx.theresnotime.io/openapi/ as the TTS engine API for now.

Hi @MNeisler! We need your expertise for this task where we are trying to measure success for real-time preview.

• What data do you think we should be looking at?
• How should we look at the data?
• Is there any additional data that we should track besides T298218?

Investigation details: https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Reading/IPA_audio_renderer/TTS_investigation

@NRodriguez I'm trying to understand how we measure realtime preview success. Is it a calculation from the data gathered in T298218?

Thank you @RLazarus !!

@jhathaway this ticket is exactly the same request as [T296161]. Dmaza and I need the same access as samwilson. Please let me know if you still need me to update the template. Thank you for looking into this!

@NRodriguez @nayoub should the preview mode disappear if user resizes the screen to a width less than 600px?

@NRodriguez I was thinking that the button would always be at the right top corner under Preview, even if they scroll down.

@Samwilson @NRodriguez I'm testing this in my local and this button is very helpful. I'm wondering if the Reload button should follow the user. For long pages, the user would need to scroll to the top on the right pane in order to see the button when I'm adding a change at the bottom of the page.

Possible errors returned by API: https://www.mediawiki.org/wiki/API:Parsing_wikitext#Possible_errors

CommTech is not planning on working on this.

Community Tech is not planning on working on this feature.

Community Tech is not planning on working on this.

Community Tech is not planning on working on this.

CommTech is not planning on working on this improvement.

CommTech is not planning on working on this issue.