Open Bug 1109958 Opened 5 years ago Updated Last year
[meta] Using Telemetry for measuring Web Compatibility issues
Often we are struggling discovering if a code pattern in CSS or JS creating Web compatibility issues is worth fighting for (through outreach and direct contact) or just support it in the browser core engine. We have often a kind of decision process which looks like more "wet finger in the wind", aka we have an impression that we should do this or that. It would be better if we could back that up a bit more with hard data. The goals: 1. Having hard data about Web compatibility issues 2. Evaluating if possible if it's happening in some precise circumstances (such as happening only in China or happening only with the use of this JS library) 3. Making better recommendations to the platform team on priority for implementations (new features implemented in other engines not used anywhere or used everywhere) 4. help priorities for documentation and advocacy 5. more things? Some background info: * Adding a new Telemetry probe. https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Adding_a_new_Telemetry_probe For meta discussions about what we want to measure, please discuss on email@example.com (Publicly archived). https://groups.google.com/forum/#!forum/mozilla.compatibility For patches to probe telemetry, please add a dependency to this bug.
SeeAlso Chromium Dashboard https://www.chromestatus.com/
You got a candidate to track? Head to https://wiki.mozilla.org/Compatibility/Telemetry
Component: Desktop → General
Product: Tech Evangelism → Web Compatibility Tools
You need to log in before you can comment on or make changes to this bug.