Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566)

Assuming your comment at https://github.com/w3c/webcomponents/issues/566#issuecomment-371034662 still withstands, it seems like we (Apple) and Mozilla's position more or less align.

Given two browser vendors support this feature, it seems okay to proceed with adding this feature to the specification.

Whilst I don't like adding new features with with a clear opposition from one browser vendor (Google), the fact customized builtin has been merged into the HTML5 specification despite of Apple's clear and repeated objection and opposition seems to establish a clear precedent that a feature with two browser vendor support can be added to the specification even when there is a clear opposition from the third.

It's particularly notable that there is no security or privacy implication from this feature, and the opposition is more of a design principle disagreement

-- 
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/566#issuecomment-544198307