- From: Anne van Kesteren <notifications@github.com>
- Date: Wed, 23 Mar 2016 03:45:14 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Wednesday, 23 March 2016 10:45:36 UTC
I don't care strongly what we do here, but this is something we need to decide on soon. This basically blocks both Shadow DOM and custom elements. Parsing custom elements like `template` seems high unlikely to be web-compatible, given that a lot more elements can then become children of `table`, `tr`, etc. So if we want to couple the behavior of `slot` and custom elements, the easiest path forward would be to give neither parsing behavior that is different from other unknown elements (apart from maybe supporting `/>` as per above). --- 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-200292259
Received on Wednesday, 23 March 2016 10:45:36 UTC