Open marcoscaceres opened 2 years ago
- If data is static, once on TR, the results will be out of date.
Maybe the ideal is to stick a snapshot in the implementation report, which folks expect to be static, and have live links to wpt in the text. That's great until son-of-wpt gets all the attention and wpt gets out of date (worse if someone gets the domain name). This could kinda be solved with an indirectly where sections in a REC point to a page which includes live wpt links. If wpt gets replaced with something cooler or some miscreant pwns wpt, we can laboriously update those indirect pages to point to something else.
For record keeping, MDN has both Desktop and Mobile data... (some) specs already show this data inline.
Collecting screenshots.... MDN boxes:
Can I use:
Updated WPT view:
Some more...
Part of "ClearSpec" project. CC @plehegar @sideshowbarker
The idea is to give a better indication of browser support for a particular spec. The can be done by showing the results from WPT.
Bikeshed is experimenting with: https://drafts.csswg.org/css-conditional-4/
and ReSpec has an experimental PR: https://github.com/w3c/respec/pull/3870
There are significant limitations: