- From: <bugzilla@jessica.w3.org>
- Date: Thu, 17 Jul 2014 12:35:11 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26365 --- Comment #6 from Boris Zbarsky <bzbarsky@mit.edu> --- > That should be *no impact*, I hope. This isn't something to hope; this is something to audit in the specs; comes with changing the fundamental conceptual model... That said, one of the very first hits on "in a Document" in HTML is in "reset the form owner", and in that case it's not clear to me that things inside a shadow DOM should be considered "in a document". So it does sound like shadow DOM should not be "in a document" by default but we need a new term X for "light DOM nodes are X if in a document, shadow DOM nodes are X if shadow host is X" that other specs then need to be adjusted to use. That means filing spec bugs on those specs. Normally this would happen either during specification or implementation; it's a bit disturbing to me that neither one happened here so far until we started implementing, since it suggests Chrome wasn't actually implementing what the spec says. :( -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 17 July 2014 12:35:12 UTC