You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #10234 we resolved to give insertRule the ability to parse and insert declaration blocks (as CSSNestedDeclarations rules).
As of recent spec edits, insertRule is now set up to parse a declaration block (after the regular rule parsing), and throw an error when that declaration block is empty. https://drafts.csswg.org/cssom/#insert-a-css-rule, Step 4.
Is this behavior indeed what we want? @emilio points out that it's possibly weird that potentially-unknown-property:foo throws, but potentially-unknown-property: foo; color:red doesn't.
On the other hand, the following would lead to no CSSNestedDeclarations rule when parsed normally:
So probably the specified behavior isn't too bad, but I'd like to discuss to either get a stamp for this change, or to see if we can do better somehow.
The text was updated successfully, but these errors were encountered:
In #10234 we resolved to give
insertRule
the ability to parse and insert declaration blocks (asCSSNestedDeclarations
rules).As of recent spec edits, insertRule is now set up to parse a declaration block (after the regular rule parsing), and throw an error when that declaration block is empty. https://drafts.csswg.org/cssom/#insert-a-css-rule, Step 4.
Is this behavior indeed what we want? @emilio points out that it's possibly weird that
potentially-unknown-property:foo
throws, butpotentially-unknown-property: foo; color:red
doesn't.On the other hand, the following would lead to no
CSSNestedDeclarations
rule when parsed normally:Whereas this would:
So probably the specified behavior isn't too bad, but I'd like to discuss to either get a stamp for this change, or to see if we can do better somehow.
The text was updated successfully, but these errors were encountered: