- From: Trey Shugart <notifications@github.com>
- Date: Mon, 01 Feb 2016 01:39:05 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Monday, 1 February 2016 09:39:38 UTC
A whitelist is a safe approach, but from reading this it would seem the only elements that *really* need blacklisting are those that don't allow html / text content. I've many times created custom buttons where I'm projecting content into them, even if it's only text-content. I've avoided using `is=""` in the past because of the contention. The only other option is to create a custom element that renders a button and project the content of the custom element into the button. Even so, there are compound components where extending a single element doesn't make sense like an input + button search component. What about blacklisting void elements and allowing everything else? --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/110#issuecomment-177876949
Received on Monday, 1 February 2016 09:39:38 UTC