browser-specs
browser-specs copied to clipboard
w3c
A machine-readable list of Web specifications
Close #1549, adding the suggested spec to the list. ### Changes to `index.json` This update would trigger the following changes in `index.json`: Add spec (1) ```json { "url": "https://wicg.github.io/web_audio_playout/", "seriesComposition":...
### URL https://wicg.github.io/web_audio_playout/ ### Rationale Still flagged as an unofficial draft, but under incubation in WICG and now making progress. Implementation plans are not yet clear, but it seems worth...
### URL https://wicg.github.io/explicit-javascript-compile-hints-file-based/ ### Rationale - See repository: [WICG/explicit-javascript-compile-hints-file-based](https://github.com/WICG/explicit-javascript-compile-hints-file-based) - Would-be shortname: `explicit-javascript-compile-hints-file-based` ### Additional properties ```json {} ```
For new W3C specs, browser-specs gets the group from the `w3c.json` file. Exchanging with @plh, it would be good to rely on [`w3c/groups/repositories.json`](https://github.com/w3c/groups/blob/main/repositories.json) instead, which has a notion of curation....
Specs we monitor are tracked in `monitor.json`. Now that new specs get reported as issues, it would seem useful to keep those that need to enter a monitoring state as...
The bot that finds new specs correctly reports the /TR URL of a spec recently published as FPWD (see #1509 for an example). But the issue cannot be addressed through...