@JKatzWMF @ovasileva We have a lot on our plate at the moment. What is the date by which you need this data? How critical is it to decision making?

@kzimmerman - Since JK is out for a while, I'll chime in here. This data is basically needed for any future editing-related features, as we need to decide whether or not to continue building no-JS fallbacks for those features. For example, the Editing team is currently working on Discussion Tools, which is a group of Javascript editing features for talk pages. Since we don't have a good idea of how much editing is done on no-JS browsers, we don't really know what the impact will be of not providing a no-JS fallback and whether that may impact some communities more than others.

The real thing that is driving this push, however, is our desire to finally publish some comprehensive guidelines about no-JS support across all our features to inform Engineering teams in their future work (especially around projects like Desktop Refresh where no-JS support is a big cost). These guidelines were written up way back in September 2019, but have never been finalized or published mainly because we are stalled on the editing question: Should editing be a feature we continue to provide no-JS support for? In the meantime, Engineering teams are continuing to make these discussions on an ad-hoc basis, often wasting lots of time and resources in the process.

So basically, there is no specific deadline, but this data will have a very large impact on decision making across Product, if for no other reason than it will unblock our publication of the no-JS guidelines.

@kaldari Maya and Olga chatted about this and have raised the priority to high; we'll review it in our team's next triage meeting (scheduled for Monday, April 20) and determine a timeline for tackling this at that time.

To summarize the outcome of those two tickets:

• T240697: We cannot accurately determine the percentage of edits made without JS due to tracking blockers. T263505 would be the next step forward on this.
• T253033: We did not measure percent of pageviews without JS, but instead used a proxy measurement of percent of pageviews from grade A browsers vs. lower grade browsers:

It would be good to break out Grade C and Grade X since they are treated very differently.