browser-specs icon indicating copy to clipboard operation
browser-specs copied to clipboard

A machine-readable list of Web specifications

Results 66 browser-specs issues
Sort by recently updated
recently updated
newest added

Via https://github.com/w3c/browser-specs/pull/593 and https://github.com/w3c/browser-specs/pull/1058#pullrequestreview-1630650568

The NPM packages currently ship without a changelog. It should be relatively easy to create one automatically though, with some diff-ing logic (starting point exists in [`build-diff.js`](https://github.com/w3c/browser-specs/blob/637a18c318bcc94fff5dd976030342857e0a30cd/src/build-diff.js#L42)). At a minimum,...

List may now also contain non-browser specs, so no a priori reason anymore to ignore groups that do not publish specs targeted at browsers.

[Private Click Measurement](https://privacycg.github.io/private-click-measurement/) and [Attribution Reporting](https://wicg.github.io/conversion-measurement-api/), both in browser-specs, are two proposals with similar goals and overlapping definitions (e.g. `attributionDestination`). Only one of them should remain in the end, or...

The [nightly of WAI ARIA](https://w3c.github.io/aria/) is numbered 1.3, but browser-spec associates it with a 1.2 title, presumably because that's what specref knows about since it hasn't reached FPWD. I wonder...

See https://github.com/w3c/browser-specs/pull/325#pullrequestreview-698096555. - compute-shortname uses a similar list of regular expressions as those in parse-spec-url in particular. It would be good to merge the logic. - fetch-groups does its own...

Right now, our workflows determine when an ES spec reaches stage 3, but no signal is detected when a spec reaches stage 4 and thus should no longer be listed...

Build currently fails because one spec has an Editor's Draft link that targets the GitHub repo instead of the Editor's Draft. We can workaround the problem through a temporary override...

See discussion starting at https://github.com/w3c/browser-specs/pull/211#issuecomment-744383199. The new `sourcePath` entry only targets the entry point, but the contents of a spec may be assembled from a number of source files, through...