[meta] Interop 2022 tracking
Categories
(Web Compatibility :: Tooling & Investigations, task)
Tracking
(Not tracked)
People
(Reporter: annevk, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: meta)
This is a tracking bug for things we should either consider testing as part of Interop 2022 (if they fit in a focus area) or raise as part of the investigate areas.
Reporter | ||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 1•3 years ago
|
||
What's the difference between this bug and bug 1749421?
Sebastian
Reporter | ||
Comment 2•3 years ago
|
||
It seems that bug is about improving our score. This bug is about using Interop 2022 to improve webcompat.
Comment 3•3 years ago
|
||
But improving web compatibility is required for improving the score. If I understand you correctly, this is about fixing bugs that cause compatibility issues in the areas tracked by Interop 2022 while the other one is for tracking the overall improvement of the score including bug fixes and new features. If that assumption is correct, this one should rather be blocking bug 1749421.
As a concrete example, should bug 1759675 (as part of the Viewport Units focus area) be blocking this one or the other one or both?
Currently, the summaries and aliases of these two bugs are too similar to clearly distinct them, in my opinion.
Sebastian
Reporter | ||
Comment 4•3 years ago
|
||
This isn't about fixing bugs. This is about collecting webcompat bugs that need to be fed back into Interop 2022 in some way. Either through its investigate areas or as additional tests for one of the focus areas.
Description
•