Pierre-Yves Gérardy

It really depends on how much CSS there's on the page, and how dynamic the styles end up being. An O(n) API makes this approach unworkable for larger apps (and...

n is the number of RuleSets, or the number of sheets in the page. If you want both an o(1) API for insertions and indexability by number, you must recompute...

How much of the Web still uses quirks mode? Wouldn't it make sense to discourage its use by disabling the new features when rendering in quirks mode (as in, either...

I'm coming late here (apologies, I've been living under a rock for the past year). Couldn't the adoptedStyleSheets be placed in the cascade as if they were part of style...

Adding some more thoughts: while the `after` position makes sense for app writers, the `before` slot would seem a natural fit for library authors.

Wait, there's more... I haven't updated `fixed.exec` (and I wonder how the tests actually pass). Looking deeper into this, I should also probably revise `XRegexp.match` and possibly other methods. It's...

As long as we deal with `[is]`, we have a render bug in the update phase. `is` should be considered part of the element identity along with the tag name...

> @pygy looks like you had some edits in the project. did you try and get a benchmark together for luvit? @kbrock no, it was Lapis-related, sorry...

If I'm not mistaken, there's no need to add any delimiter, unless you want to allow variable names in the ranges. ``` foo 1,2 fighter bar ,3 tender baz 4,...

@faddee that 's not bullet-proof either: https://regexr.com/3h6r5 You want to match and skip strings (and maybe comments?) ```JS const DECL_REGEX = /.([^:{]+)(:[^{]+)?{((?:"(?:\\[\s\S]|[^"])*"|'(?:\\[\s\S]|[^'])*'|[^}])+)}/g; ``` https://regexr.com/3h6r8 For completeness, you can add `|\/\*[\s\S]*?\*\/`...