> My main use-case for this dashboard atm is to monitor position: sticky across browsers

That's great feedback, actually. May I ask, beyond just seeing the data, what kinds of actions do you expect to take, and what would make that easier for you?

A good question! We are interested in getting feature-parity for position: sticky across the browsers, so some thoughts off the top of my head:

1. Sort/filter by pass/fail percentage alongside the textual search, so that only failing tests can be shown. Just makes it a little quicker to locate failing tests.

2. A quick way to file a bug for each browser for a specific test (or multiple tests?).

3. More generally, a way to associate a test with a bug link for a given browser so that it's clear from a glance when a browser vendor knows that they have failing behavior and when they don't.

4. Spec link for each test. Less useful I think, but might still be useful on occasion.

> Sort/filter by pass/fail percentage alongside the textual search, so that only failing tests can be shown. Just makes it a little quicker to locate failing tests.

Here, are you interested in conformance, or interoperability? The difference is that for conformance you'd want to look at the most failing tests, while for interoperability you'd look for the tests with the least consistent results, where all failing is OK.

> A quick way to file a bug for each browser for a specific test (or multiple tests?)
> More generally, a way to associate a test with a bug link for a given browser so that it's clear from a glance when a browser vendor knows that they have failing behavior and when they don't

Yeah, I think something like that would be good, although it would take years to populate. Since you'd want to be able to associate existing bugs, it also implies that some people have edit access, i.e. some auth system is needed.

> Spec link for each test. Less useful I think, but might still be useful on occasion.

Do you mean a deep spec link, or just a link to the spec that corresponds to the directory?

> Here, are you interested in conformance, or interoperability? The difference is that for conformance you'd want
> to look at the most failing tests, while for interoperability you'd look for the tests with the least consistent
> results, where all failing is OK.

Probably more interoperability - we want to know what behavior Chromium implements (or doesn't!) that the other vendors do/don't.

> Yeah, I think something like that would be good, although it would take years to populate. Since you'd want to
> be able to associate existing bugs, it also implies that some people have edit access, i.e. some auth system
> is needed.

Yes, I have no idea how this could be done :(. It would be cool though.

> Do you mean a deep spec link, or just a link to the spec that corresponds to the directory?

Unfortunately it's all the same for sticky really since it's quite a shallow spec (each test links to a particular anchor in the css-position-3 spec, so whether we linked at directory level or test level it's quite easy to get the info you want.) I suspect it would be better to ask maintainers of some more nested features? :/



+flackr, +rbyers in case they have other thoughts on the questions posed in this bug for the WPT dashboard - either for sticky or just in general.

Sorry for the delay - thanks for the feedback and thanks for using wpt.fyi!

The UI is currently very WIP and this feedback is great for shaping it. GitHub is going to be our primary bug tracker, so I'll make bugs for each of the things you mentioned:

Have a way of viewing all tests in a directory
https://github.com/GoogleChrome/wptdashboard/issues/27

Filter only passing or only failing tests for a given browser
https://github.com/GoogleChrome/wptdashboard/issues/28

Be able to associate a test (or tests) with a spec
https://github.com/GoogleChrome/wptdashboard/issues/29

Be able to associate a test (or tests) with a browser bug
https://github.com/GoogleChrome/wptdashboard/issues/30

I'll keep this bug open for discussion but if you have any thoughts specific to any of those bugs please voice them there.

@smcgruer your original suggested use case is now possible: http://wpt.fyi/css/css-position-3