-
### What is the issue with the HTML Standard?
The next meeting for the joint OpenUI-WHATWG/HTML-CSSWG task force on styleable form controls is scheduled for Thursday September 19, 2024 at 8am PT.
-
This has somewhat come up before in #221 but I think it's worth raising again.
With this specification being the core base to many other specifications, (e.g. [FedCM](https://w3c-fedid.github.io/Fe…
-
The vocab base URL should be: `https://w3id.org/vc-barcodes#`:
https://w3id.org/vc-barcodes/v1 => https://github.com/w3c-ccg/vc-barcodes/blob/main/contexts/vc-barcodes-v1.jsonld
See spec: https:…
-
Via https://github.com/w3c/browser-specs/pull/1477#discussion_r1740609914. The criteria have always been fuzzy. That makes it hard to evaluate when a new spec should join (and/or what standing to give…
-
@reillyeon reports in https://github.com/WICG/idle-detection/pull/55#discussion_r1752504934 that browsers retrieve the permission state asynchronously, so use of permission state in specs needs to be …
-
In our platform we have generic request handling pipelines where the caller and the downstream resource servers may support Zipkin B3 headers, W3C Trace Context, etc.
We therefore would like to und…
-
-
Via discussion in https://github.com/tobie/specref/pull/810#discussion_r1722985394
Various specs in W3C come in levels that belong to the same series. Both levels and series have shortnames in W3C,…
-
We also want to look to add the follow features to our netlify publications:
- [ ] links in the comment from netlify to all specs that were edited by the PR, like: https://deploy-preview-2284--wai-ar…
-
Ref: https://github.com/w3c/webrtc-pc/issues/2930.
With the conversion of `RTCIceCandidatePair` from a dictionary to an interface, the XRef database contains some ambiguous duplicate definitions wi…