[Bug 28353] New: [Shadow]: Use a parent/child relationship in the composed tree for some elements, i.e. <ol>/<li>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28353

            Bug ID: 28353
           Summary: [Shadow]: Use a parent/child relationship in the
                    composed tree for some elements, i.e. <ol>/<li>
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: hayato@chromium.org
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org
            Blocks: 14978

For example, suppose the following case:

<div id="shadow-host">
  <summary>summary</summary>
</div>


#shadow-root-of-the-shadow-host
  <details>
    <content></content>
    <div>details</div>
  </details>


Unfortunately, this should not be rendered as intended, if we interpret the
spec [1] strictly.

[1]: https://html.spec.whatwg.org/multipage/forms.html#the-summary-element

The spec says:

> Contexts in which this element, <summary>, can be used:
>   As the first child of a details element.


The same discussion might be also applied to the following elements, including,
but not limited to:

- <tr>/<td>
- <ol>/<li>

I've not investigated carefully yet. We have to investigate further.


In Blink, AFAIR, we've spent some efforts to support these elements so that
they are rendered correctly as intended even though they form a parent/child
relationship in the composed tree, rather than in a node tree. However, I'm
afraid that no one has a clear idea what behavior is correct.

If we are to support these cases, the spec must specify that somehow.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Friday, 27 March 2015 06:07:13 UTC