François Daoust

Adding links to past discussions on the topic: - https://github.com/w3c/browser-specs/issues/58#issuecomment-636017113 - https://github.com/w3c/browser-specs/issues/1008#issuecomment-1700538283 Since then (or in parallel): - The spec was added as a potential deliverable to the new [Web...

Closing as the execCommand spec was added to the list. The spec was added with a "pending" [standing](https://github.com/w3c/browser-specs/?tab=readme-ov-file#standing), pending proper adoption in the Web Editing WG and initial updates to...

HTML vs. EPUB is the main case that creates duplication but note https://github.com/w3c/webref/issues/1337 lists a few additional cases where elements are defined in more than one spec.

As [done in css-sizing-4](https://drafts.csswg.org/css-sizing-4/#sizing-values), css-anchor-position would ideally list the impacted CSS properties in a table with a "New Values" row instead of [only saying so in prose](https://drafts.csswg.org/css-anchor-position-1/#sizing). On top of...

Great, thanks for reporting the issue!

That introduces a duplicate `path` element. That's not ideal but we don't guarantee uniqueness and we have duplicates in the package already (see #1337), so (clunky) business as usual.

Publishing to get the new `` element in HTML

That seems good, but the contents of the spec are still in the [FedCM spec](https://www.w3.org/TR/fedcm/#browser-api-login-status), so adding it would create duplicates. Perhaps worth waiting until the FedCM spec gets updated?

@browser-specs-bot monitor because FedCM still contains the Login Status API as sub-section for now (and TR link actually targets it, which will likely confuse tooling)

> In particular, https://github.com/w3c/webref/pull/1288 stems for our tests currently flagging in css-mixins-1 as duplicate of in selectors-4, whereas the two names are not in the same namespace: the latter is...