- From: Preet <notifications@github.com>
- Date: Tue, 24 Sep 2019 08:16:20 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 24 September 2019 15:16:41 UTC
I think this is easy to dismiss, but `<p>` for example, is a very commonly used tag that often contains more than text - images and videos in it.
```html
<p>
<my-element>
<div>caption</div>
</my-element>
</p>
```
gets parsed as:
```html
<p>
<my-element>
</my-element>
</p>
<div>caption</div>
```
I don't like the idea of not being able to create inline custom-elements inside a paragraph. For example, a custom picture or video element.
Even if the output was the following, it would have worked for most cases:
```html
<p>
</p>
<my-element>
<div>caption</div>
</my-element>
```
There may be no appetite to change the HTML parser, but if you are thinking of Web Components, this is pretty sucky behavior.
--
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/630#issuecomment-534606860
Received on Tuesday, 24 September 2019 15:16:41 UTC