-
Moving this over from , given that's apparently appropriate nowadays.
CSS should somewhere (hence the lack of any tagged spec!) define which subresources block the load event; at least when that bu…
-
When we switched to JSON-SEQ a while back (https://github.com/quicwg/qlog/issues/172), we assumed that using record separators instead of newline-delimited JSON wouldn't cause too much pain. I think i…
-
Moving this over from https://github.com/w3c/aria/issues/337.
Should aria-placeholder be part of the accessible description calculation?
-
The request signing extension currently only supports Ed25519 for signing requests. In the event that future research indicates this algorithm shouldn't be used, there should be a well-defined way for…
-
The `string-set` property (and companion `string()` and `content()` functions are defined twice:
- in [css-content-3](https://drafts.csswg.org/css-content-3/#string-set)
- in [css-gcpm-3](https://dr…
-
Is it EXIF-based resolution-x/resolution-y? How does it work when they're not 1:1?
Is it based on something else? Format specific?
noamr updated
4 years ago
-
The BSF spec says:
> Valid top-level boxes such as pdin, free, and sidx are allowed to appear before the moov box. These boxes must be accepted and ignored by the user agent and are not considered pa…
-
It has been suggested that the abstract data model in DID Core creates unnecessary complexity and that a more concrete data model should be selected, based on implementation experience over the past t…
-
Currently Chromium has [unspecified heuristics](https://github.com/w3c/largest-contentful-paint/issues/79) that ignore LCP candidates when the document's opacity is 0, and only expose those candidates…
-
There should be a way to (1) check if the browser supports and (2) specify that a stream contains a mixture of encrypted and unencrypted content. This is particularly important in the case of dynamic …