Hi there!
I find wpt.fyi very useful to keep track of the more niche browsers.
To me, knowing if a browser implements a deprecated/unspecified API may be interesting sometimes, but mostly i don't care about deprecated APIs. But it seems that wpt.fyi currently always displays results for these tests.
One example is document.execCommand, tested by https://github.com/web-platform-tests/wpt/tree/master/editing - According to MDN its a deprecated API.
I would love if there was some easy toggle or config somewhere to exclude these tests from results, to get a more accurate picture of how compatible the browser is with up-tp-date websites using current APIs.
It would probably make sense to habr multiple kinds of tags by which results could be filtered, for example one for what MDN considers deprecated, one for whether it has an accepted spec, etc.
I know this is likely a lot of work, and perhaps that data isn't in any way tracked for the tests in the first place, but because i don't know what would need to happen in other repos i've decided to start with the issue here.
Hi there!
I find wpt.fyi very useful to keep track of the more niche browsers.
To me, knowing if a browser implements a deprecated/unspecified API may be interesting sometimes, but mostly i don't care about deprecated APIs. But it seems that wpt.fyi currently always displays results for these tests.
One example is
document.execCommand, tested by https://github.com/web-platform-tests/wpt/tree/master/editing - According to MDN its a deprecated API.I would love if there was some easy toggle or config somewhere to exclude these tests from results, to get a more accurate picture of how compatible the browser is with up-tp-date websites using current APIs.
It would probably make sense to habr multiple kinds of tags by which results could be filtered, for example one for what MDN considers deprecated, one for whether it has an accepted spec, etc.
I know this is likely a lot of work, and perhaps that data isn't in any way tracked for the tests in the first place, but because i don't know what would need to happen in other repos i've decided to start with the issue here.