Re: [w3c/webcomponents] WebPlatform Web Components F2F 2018 (#713)

> Could we bring up customized built-ins/extending native elements/custom elements with different parsing contexts to the agenda?

I second this.  I would like to add that there is a general need for the ability to create 'speculative polyfills' for unknown elements, which autonomous elements don't support.  Example <foo is="new-foo">

>I would say, >430 comments, hundreds of thumbs-ups, many participants in the single issue and even more if we count related issues, proves the need for it.

+1

> My understanding is that customized built-ins, as specced, have 3/4 implementer support. So they may not be a fruitful topic for discussion; instead web developers can bring up their concerns with their Apple representatives directly at another venue (e.g. in said centithread).

Is Chrome waiting on Safari to implement this?  If so they will be waiting a long time, I think.  Better to follow Mozilla's example and implement based on about as good a consensus as you are likely to get.  
Because the webcomponents speculative polyfill for built-ins are blocked on Chrome, apparently, so Web developers can't even vote with their feet.

At the very least, I think there's something to discuss.  My .02 cents.  

-- 
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/713#issuecomment-352038767