François Daoust
François Daoust
This spec should be added to the list. On top of fixing `sourcePath`, it would be good to surface the fact that this is joint W3C/OGC work. Now our data...
@browser-specs-bot pr
@deniak The repository used for DID v1.1 was renamed. As a result, the link to the Editor's Draft that appears in all published versions of DID (v1.0 and FPWD of...
> @tidoust, so far, I'm not monitoring that kind of changes but I'm guessing we should have some tooling in place to update the ED and create the redirects from...
@browser-specs-bot pr
@msporny said: > I can't get DFNs to show up when including did-1.1 or did in xref in the downstream specs Adding the spec to browser-specs is the right first...
> I'm still not sure that this arrangement is actually possible I guess that is *possible* since Web IDL [does not forbid](https://webidl.spec.whatwg.org/#idl-constructors) throwing an exception from within constructor steps ("The...
Seems a good candidate for monitoring. Relevant [entry in Chromestatus](https://chromestatus.com/feature/5141940204208128) says "No active development", and links to recent standard positions requests that have not yet been reviewed. Let me try...
@browser-specs-bot monitor because Chrome status entry https://chromestatus.com/feature/5141940204208128 says no active development and no known standard positions yet
A dump of notes to document the impact of adding a spec to browser-specs. I see @Elchi3 proposed a breakout session at TPAC 2024 that takes a similar approach, see...