On 16/04/2019 12:17, Anne van Kesteren wrote:
On Mon, Apr 15, 2019 at 7:16 PM Jonathan Watt <jw...@jwatt.org> wrote:
These are all really great. Thanks, James!
Indeed, thanks a lot for working on this! This will help a lot with
prioritizing work and also with standards development.
Some feedback for the Interop Dashboard:
* It would help me a bit if it clarified which versions of Chrome,
Firefox, Safari are represented to make local comparisons more easily.
In general we are always using the latest experimental versions
available for the platforms we have (Firefox Nightly / Linux, Chrome dev
/ Linux and Safari TP / macOS). The wpt.fyi link should have more
details about the specific versions used for the currently loaded run; I
could add that somewhere in the dashboard if it's helpful.
* It would also be nice to be able to give a wpt path rather than have
to find the corresponding bug component.
It's not the best UI but you can select "Any" as the bug component and
then filter by path. That does end up loading all the data though.
Allowing to select by either component or path at the top level would be
a larger change, but it's certainly possible if people would find it
useful. The idea of making component the top-level selector was to
enable workflows analogous to bug triage where the work is divided up by
component.
* I don't see all the bug components, e.g., DOM::Core: Networking is missing.
The mapping from component to test directories is in
testing/web-platform/moz.build Per that file there aren't any tests
covering DOM::Core: Networking. More likely the component to path labels
contain some errors that should be fixed.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
