Re: [dom] Attributes do not need a name slot for web compat (#110)

Thanks @bzbarsky, that is very helpful!

My concern was that the spec says "Unless explicitly given when an attribute is created, its name is set to its local name" and that perhaps there might be some edge case in HTML or XML parsing where the Gecko's "qualified name" *is* explicitly given, and wouldn't be the same as the computed value in Blink.

If that is not the case, then it would be nice to clarify the spec so that it's clear that the name slot doesn't need to be stored.

I agree that there's no need to spec a two-pass lookup, as steps 2 and 3 in the "new model" above are mutually exclusive.

Thoughts, @annevk?

In any event, this issue won't need to block https://code.google.com/p/chromium/issues/detail?id=502301, I'll just assume that a computed prefix+":"+localName string is and will continue to be equivalent to what the spec says. (Possible to optimize, of course.)

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/110#issuecomment-158889552