Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512)

See https://www.w3.org/Bugs/Public/show_bug.cgi?id=20567#c69 onward for the conclusions from last time. That was mainly blocked on custom elements getting defined.

I don't think Mozilla's position on this has changed. We'd still favor changing prototypes for built-ins and giving custom elements the opportunity to do so (or do it automatically?) so as to reduce the risk of leaking globals.

Not sure how keen @bholley is on doing this debate again, but paging him just the same.

---
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/512#issuecomment-223501537