Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624)

as a developer using custom elements I would really like self-closing custom elements. It makes no sense to me if I have a `<custom-box color='RED' />` , that my browser even stops and ignores the remaining html code. I must specify a separate closing tag for the custom-box before it even works. 

- Developer friendly: allow self-closing custom elements for custom element users

Another motivation is; when someone is using the custom element and that element has no nested content or elements, that developer wants to cleanup its code by changing it to a self closing element. It just looks ugly.

Another motivation is; when the custom element needs a separate closing element, the developer might assume that the custom element accepts content; which it might not. 

 - I would vote for the custom element IDE to issue a warning on ignored content for:
```

<custom-box color="RED">ignored text</custom-box>
<custom-box color="RED"><p>ignored child element with text</p></custom-box>

```


-- 
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/624#issuecomment-390596283