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
After writing #44 (comment), I realized the same argument applies to the empty attribute syntax.
That is, given the tokens div contenteditable ? (foo) , it's ambiguous whether foo toggles the contenteditable attribute, or is the body of the div.
One possible fix is to swap the tokens around: div contenteditable(foo)?. This reminds me of Rust's ? operator, which is nice. On the other hand this new syntax doesn't look much like an attribute.
The text was updated successfully, but these errors were encountered:
After writing #44 (comment), I realized the same argument applies to the empty attribute syntax.
That is, given the tokens
div contenteditable ? (foo)
, it's ambiguous whetherfoo
toggles thecontenteditable
attribute, or is the body of thediv
.One possible fix is to swap the tokens around:
div contenteditable(foo)?
. This reminds me of Rust's?
operator, which is nice. On the other hand this new syntax doesn't look much like an attribute.The text was updated successfully, but these errors were encountered: