On Wed, Feb 20, 2013 at 3:01 AM, Scott Miles sjmi...@google.com wrote:
Perhaps one other COST of the localName issue is the question of
document.createElement.
document.createElement('x-button') creates button is='x-button', people
complain because the tag names do not match.
On 2/20/13 7:26 AM, Anne van Kesteren wrote:
These already cannot be just localName checks
They often are in practice for extensions and web script.
For browser code or better-written extensions and web script they're
typically localName + namespaceURI checks.
I also fail to see exactly
On Feb 19, 2013 3:54 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
2) Custom element constructor runs at the time of parsing HTML, as the
tree is constructed.
PROBLEM: Several implementers let me know that allowing to run JS
while parsing HTML is not something they can accommodate in a
I think you captured it well, thank you for distillation.
Perhaps one other COST of the localName issue is the question of
document.createElement.
document.createElement('x-button') creates button is='x-button', people
complain because the tag names do not match.
Adding Blake and William, the Mozilla folks working on this. I
apologize for not thinking of you guys earlier :)
On Tue, Feb 19, 2013 at 7:01 PM, Scott Miles sjmi...@google.com wrote:
I think you captured it well, thank you for distillation.
Perhaps one other COST of the localName issue is the
