- From: <bugzilla@jessica.w3.org>
- Date: Fri, 08 Feb 2013 18:35:28 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20487 --- Comment #19 from Dimitri Glazkov <dglazkov@chromium.org> --- (In reply to comment #18) > Throwing seems fine to me. > > Ignoring it's declared as custom element because the namespace is wrong and > just creating HTMLUnknownElement also seems fine to me. After some thinking, this seems like the most consistent behavior. Conceptually, the model of the element-interface-concept hook is a table: (namespace, localName) -> interface if the namespace is wrong, then the result of this table lookup fails, and thus HTMLUnknownElement is returned. If we add throwing, then we need to add more hooks, and that seems less consistent with how things work now. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 8 February 2013 18:35:30 UTC