Re: [webcomponents] Use a parent/child relationship in the flat tree in the definition of some elements, i.e. <tr>/<td> (#404)

I am okay to close this because I do not have a plan to support this soon.

What this issue is asking is:

For example, in a light tree:
```
<x-foo>
  <td>...</td>
  <td>...</td>
</x-foo>
```

in `x-foo`'s shadow tree:
```
<table>
  <tr>
    <slot></slot>
  </tr>
</table>  
```

For example, according to https://html.spec.whatwg.org/#the-tr-element,
> The sectionRowIndex attribute must, if the element has a parent table, tbody, thead, or tfoot element, return the index of the tr element in the parent element's rows collection (for tables, that's the HTMLTableElement.rows collection; for table sections, that's the HTMLTableRowElement.rows collection). If there is no such parent element, then the attribute must return −1.

The element's definition is using a *raw* parent, which prevents these examples from working as intended. If we are to support this kind of example to work, we might want to consider to replace a *parent* with *flat-tree-parent' in each definition.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/404#issuecomment-202289212