What there contradicts what I said? I'm aware of innerHTML hacks that make it possible to work around but those are not valid attribute names. I'm not even against the syntax; i like it, but that doesn't change the fact that it is invalid html.
User pfooti's comment referenced the specification[1]. You said that a browsers' implementation of the DOM API proves that it is illegal. I then linked to an issue with a detailed discussion of how the DOM API isn't consistent with itself, much less the HTML specification.
Comments
It's illegal. Go to your console and type el.setAttribute("(foo)", "bar") and see what happens.
No it is not. See the discussion here: https://github.com/angular/angular/issues/133
What there contradicts what I said? I'm aware of innerHTML hacks that make it possible to work around but those are not valid attribute names. I'm not even against the syntax; i like it, but that doesn't change the fact that it is invalid html.
Parent quotes the W3 Spec to prove that it's legal, and your response is "it's illegal because $BROWSER say's so"?
I trust the spec more than an implementation.
The parent didn't quote the spec, they quoted a GitHub issue with 71 participants. If you want to post a link to the spec text please do.
If true I'm not sure it matters if every browser throws an exception.
User pfooti's comment referenced the specification[1]. You said that a browsers' implementation of the DOM API proves that it is illegal. I then linked to an issue with a detailed discussion of how the DOM API isn't consistent with itself, much less the HTML specification.
[1]:http://www.w3.org/TR/html-markup/syntax.html#syntax-attribut...