24379 2014-01-24 06:26:11 +0000 Shadow DOM: Consider defining inertness in terms of the composed tree 2017-07-27 10:26:38 +0000 1 1 1 Unclassified WHATWG HTML unspecified PC All RESOLVED MOVED blocked on Shadow DOM being mature P2 normal Unsorted 1 falken ian annevk falken ian kochi mike contributor oldest_to_newest 98982 0 falken 2014-01-24 06:26:11 +0000 (This bug was originally https://www.w3.org/Bugs/Public/show_bug.cgi?id=22898) In the HTML spec, any node that is not an ancestor or descendant of the active modal dialog is marked inert.[1] It seems the ancestor/descendant relation should be based on the composed tree (a Shadow DOM concept). Otherwise, children that have been transposed into a modal <dialog>'s subtree are considered inert, although they are rendered as if they are real children of the <dialog>. This is surprising to the user interacting with the dialog. I guess to spec the desired behavior, the HTML spec will need to make a mention of the Shadow DOM spec. See also https://code.google.com/p/chromium/issues/detail?id=269842 [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/editing.html#inert 99043 1 ian 2014-01-24 23:32:33 +0000 The way I did this in XBL, IIRC, was to define a merged tree that CSS works on, and to say that certain algorithms work on that tree instead of the "real" tree. I'd rather not have to mention shadow trees in all the relevant algorithms in HTML, at least not until the Shadow DOM stuff is far more established (at which time maybe we would just merge it into the DOM spec and update HTML accordingly). 125605 2 annevk 2016-03-23 12:55:26 +0000 Matt, is this something you'd be willing to patch in HTML? 128791 3 kochi 2017-07-27 10:26:38 +0000 Moved to https://github.com/w3c/webcomponents/issues/653