[andreashansen]

Custom elements v1: http://caniuse.com/#feat=custom-elementsv1

[ubersoldat2k7]

basically Chrome (I just saved you a click)

[andreashansen]

Although, their demo works perfectly fine in Firefox: https://corehacker-10883.firebaseapp.com/

[Mayzie]

It's probably using a polyfill for the functionality.[1]

[1] - https://www.webcomponents.org/polyfills#custom-elements-poly...

[adamdbradley]

Our testing and shown that it works in IE11 and above. Both Safari and Chrome support custom elements natively, so no polyfill is required. Additionally, Edge has it under construction, and Firefox has custom elements behind a flag. For Edge, IE and Firefox the polyfills are downloaded on demand, rather than every browser always downloading every polyfill.

[jazoom]

If this is true it's not practically useful yet. There must be more to it.

[u320]

You can use a polyfill to get it working in browsers without custom elements support.

[jeffhuys]

...and Safari? Which is actually a pretty popular browser (with good reason).

[LunaSea]

Safari 10.1 = 2.64%

Safari 10.0 = 0.64%

Safari 8.0 = 0.33%

Safari 9.1 = 0.27%

===================

Total = 3.88%

For July 2017 according to NetMarketshare.

I wouldn't call a 3.88% install base "pretty popular". It's also offers a terrible developer experience

cf: https://www.netmarketshare.com/browser-market-share.aspx?qpr...

[eppsilon]

"desktop market share" != "market share"

[pjmlp]

Safari as well.