Need a way to skip info from Specref for a spec #1606
Comments
tidoust
added a commit
that referenced
this issue
Jan 10, 2025
This provides a more generic solution to #1606. Browser-specs has become the main source for Specref for WICG specs and W3C Editor's Drafts. The code no longer attempts to fetch info for these specs from Specref as a result. Tested locally, this will adjust a handful of spec titles (to match the actual spec title, which seems good). Interestingly, it will also adjust a few WICG entries for which the spec says the status is "Unofficial Draft", which will also switch the standing for these specs to "pending". That seems good as well although we may want to review these changes before we release a new version. I propose to do that separately in any case. Specs in that category include: Web Share Target API, preferCurrentTab, the CSS Parser API. Note: Specref is still being used as source, mainly for WHATWG specs.
tidoust
added a commit
that referenced
this issue
Jan 13, 2025
This provides a more generic solution to #1606. Browser-specs has become the main source for Specref for WICG specs and W3C Editor's Drafts. The code no longer attempts to fetch info for these specs from Specref as a result. Tested locally, this will adjust a handful of spec titles (to match the actual spec title, which seems good). Interestingly, it will also adjust a few WICG entries for which the spec says the status is "Unofficial Draft", which will also switch the standing for these specs to "pending". That seems good as well although we may want to review these changes before we release a new version. I propose to do that separately in any case. Specs in that category include: Web Share Target API, preferCurrentTab, the CSS Parser API. Note: Specref is still being used as source, mainly for WHATWG specs.
|
Handled with a more generic mechanism. That should be enough for now! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some entries in Specref are currently hardcoded in
biblio.jsonbut could rather be contributed by browser-specs, with more accurate information. There's no way to do that properly today because browser-specs leverages the info from Specref whenever it can. Some mechanism is needed to tell browser-specs not to fetch the information from Specref for some specs.That's typically a temporary need, while the entry gets moved in Specref from
biblio.jsontobrowser-specs.json.The text was updated successfully, but these errors were encountered: