Re: [webcomponents] Parse <slot> like <template> (#59)

tl;dr: I can live with different parsing for `slot` and custom elements.

Rendering of `<table><custom-foo><tr><td>...` would indeed be broken unless it's `display:contents` by default, at least when it's a child of table/tbody/tfoot/thead/tr.

If people working on this see a clear benefit for `template`-like parsing for `slot` but less benefit and higher risk for custom elements, I don't want to block making `slot` as useful as it can be. I just wanted to point out that enabling it could lead to developers opting to abuse the element for other purposes than what `slot` was intended for to get better parsing when what they actually wanted was a custom element.

---
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/59#issuecomment-200296711