In T235812#5623776, @marcella wrote:

@phuedx could you clarify what your concerns about this approach are?

In T220627#5607061, @Isaac wrote:

As I go to do this analysis, what UTC day/hour should be my cut-off for when QuickSurveys would have switched from the old approach to the new approach?

The beta opt-in panel feature/code has since been removed from the codebase(s) (see T229446: Remove the beta opt in panel from the mobile site for detail).

The beta opt-in panel feature/code has since been removed from the codebase(s) (see T229446: Remove the beta opt in panel from the mobile site for detail).

In T210808#5613061, @JoeWalsh wrote:

@Jdlrobson I filed two new tickets to specifically track what's blocking removal of the mobile view API: T236733 and T236731

Additionally, the Performance team is running their Perceived Performance survey right now.

In T235752#5584152, @Trizek-WMF wrote:

@kostajh, do you have a way to know if it is broadly used?

I tested this on enwiki in production. I enabled a couple of mobile-specific gadgets (presumably @TheDJ's!) and proving to myself that they were only loading when I was accessing the site using a (virtual) mobile device. I saw no relevant errors in the JavaScript console while testing.

MediaWiki:Mobile.css/js is loaded on the mobile domain

In T233609#5566968, @Jdlrobson wrote:

We do however do this on mobile in the beta mode so it's doable just at certain size audiences...

It might also be prudent to reconcile the MobileWebSearch and SearchSatisfaction schemas while we're at it.

I've been bold and marked the Search schema as inactive.

In T233614#5565083, @Jdlrobson wrote:

Confusingly desktop does have a Search schema which is not marked as inactive. Is this instrumentation still available? https://meta.wikimedia.org/wiki/Schema_talk:Search If not, I'm guessing desktop search instrumentation got turned off but mobile search didn't? Is the desktop code still around or can we locate the bug that turned it off if it is not?

@Jdrewniak should be submitting the RfC today (or early tomorrow)!

Who's going to do the QA, which, as written, is quite technical? Also, will this change have a negative impact on performance?

For reference, the code that processes statsv URLs is here.

The event is sent as something like this:
https://en.m.wikipedia.org/beacon/statsv?MediaWiki.minerva.WebClientError.anon=1c?MediaWiki.minerva.WebClientError.anon=1c?MediaWiki.minerva.WebClientError.anon=1c?...

Per my note in today's Web Team Task Grooming ritual, I don't want to get our hopes up about Sentry just yet 🙂

@fgiunchedi: Sorry for the belated ping but has the

An additional datapoint: There haven't been any significant changes to the Popups codebase since 23rd August 2019 (see https://github.com/wikimedia/mediawiki-extensions-Popups/commits/master/)

👌 Also, the client-side event validation was removed some time ago anyway! Thanks for tidying up, @Ottomata.

@ovasileva: I'm moved this out of Needs Analysis because the analysis is already done 🙂

This Looks GREAT to me 💪 Excellent work, @Jdlrobson, y'all!

I'm being bold and resolving this task as the work was done in T223824: Hide Cologne Blue skin in preferences .

@ovasileva: We agreed that I'd remind you to add the rationale for carrying on this piece of past the deadline for AMC to the description of this task.

This looks great 💪

Thanks, @Nuria and the Analytics Engineering team!

Is there any production instrumentation that relies on the time at which the beacon request arrived at the edge (the dt field in the Hive event.* tables IIRC)? My apologies if you've already looked into this.

In T115430#1724958, @matmarex wrote:

I am still sort of kind of maintaining them both (you'll notice that I joined both of their projects). No one seems to be filing any bugs though. I tried to help the Echo team a bit with their recent problems (I think I managed to merge a patch), but mostly they solved them swiftly enough without me.

Moving this off Reader's Webs board the original request of the team has been fulfilled.

Question that @alexhollender raised whilst discussing this task: What happens if a logged out user navigates to the URL for the talk page?

Thanks for creating that task, @alexhollender. Given T206354#5431259, T206354#5432542, and the existence of T231205: Add shadow to nav menu drawer, I think this task is OK to sign off.

Per the above, I've updated the documented sample, contact details, team, and project in the schema's documentation.