Simon Pieters

I still like this idea, although the bot could file the issue only when a PR with the label is merged (or an issue with the label is closed by...

So for example in https://infra.spec.whatwg.org/#collect-a-sequence-of-code-points this > Append that code point to the end of /result/. would need to be something like > Set /result/ to /result/ concatenated with that...

OK. Immutable does seem cleaner in that the spec will more closely map to an implementation, which seems like it would be easier to reason about. OTOH I'm not aware...

Should this property always be serialized with two values, so that it can roundtrip with both the prefixed and unprefixed variants? Demo http://software.hixie.ch/utilities/js/live-dom-viewer/saved/7809 Result in chrome ``` log: getting .style...

If they're parsed differently, always serializing two values seems better. Is there interest in trying to change the unprefixed property to match the -webkit- prefixed property as @fantasai suggested in...

I filed an issue for the CSS WG for those questions: https://github.com/w3c/csswg-drafts/issues/7802

See https://www.igvita.com/2013/06/20/http-archive-bigquery-web-performance-answers/ https://discuss.httparchive.org/ for more example queries. cc @igrigorik

...and how should aliasing work for pseudo-elements. (I think serializing should give the unprefixed name. `getComputedStyle()` is not relevant per spec since it only supports `::before` and `::after`.)

Hmm `getComputedStyle()` might be relevant after all, https://github.com/w3c/csswg-drafts/issues/717

srcset parser has something like this, but without a stack (it uses a dumb state machine).