François Daoust

Ah, right, I see a number of such attributes in the IDL definitions, including `[Throws]`, `[SetterThrows]`, `[NeedsSubjectPrincipal]`, `[BinaryName]`, `[Pure]`, `[Cached]`, `[ChromeOnly]`, `[Pref]`. Many of them I don't understand. Some of...

Ahem, I'm afraid my fix for headings in #2358 unfortunately broke the import of cross-references because I actually restricted import to `dfn` types + sections, excluding all non `dfn` terms...

Fix proposed in #2364.

Thanks for the nudge, that proved useful to push the issue to the top of the pile ;) CSS extracts in Webref now include an `href` key for all entries...

All extracts that didn't have more specific links back to the spec now have such links in `href` properties attached to most objects: CSS extracts, idlparsed extracts, and elements extracts....

Refreshing the list of duplicate definitions and completing with the list of IDL terms that are defined more than once (before patches are applied): Duplicate dfns with same type (64...

Reflecting on the duplicate IDL dfns: - `DOMParser`: definition in [Trusted Types](https://w3c.github.io/trusted-types/dist/spec/#domparser) appears in an IDL block flagged with an `"exclude"` class. Definitions should probably not be extracted at all....

Discussions here and elsewhere led to the [web-features project](https://github.com/web-platform-dx/web-features/) within the WebDX Community Group. I'm closing this issue accordingly.

Did you set the [Prepare for TR](https://speced.github.io/bikeshed/#metadata-prepare-for-tr) boolish? That should move the stylesheet to the right position for PubRules.

> But not all browser-specs are in this linking database, and it's not clear how to add them. I ran into this today because https://w3c.github.io/webappsec-credential-management/#algorithm-request isn't in there. There may...