- From: <bugzilla@jessica.w3.org>
- Date: Thu, 12 Jun 2014 18:35:24 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26033
--- Comment #5 from William Chen <wchen@mozilla.com> ---
(In reply to Hayato Ito from comment #4)
> I'm afraid that I couldn't figure out what this mean. Could you give us the
> concrete example so that every one can know the impact of the change?
Consider the following example:
Light DOM:
<div id="host">
<span id="one">
<span id="two">
Youngest Shadow DOM on #host:
<Youngest SR>
<content select="#one">
<shadow>
<span id="three">
Older Shadow DOM on #host:
<Older SR>
<content>
In the current spec, the composed tree looks like this:
<div id="host">
<span id="one">
<span id="two"> (distributed left over node)
With <shadow> as function call, the composed tree looks like this:
<div id="host">
<span id="one">
<span id="three"> (distributed <shadow> child)
With the change I am proposing, the composed tree looks like this:
<div id="host">
<span id="one">
This allows us to introduce <shadow> as a function call moving forward without
breaking anything (as long as developers are not using children of <shadow>
elements for anything).
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 12 June 2014 18:35:26 UTC