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

Right, OK, it seems like we are converging on "Stay custom with same definition", with it not being Mozilla's preference, but they're willing to live with it. Thank you for being willing to compromise!

I'll work on speccing this over the next day or two, unless I misread and we're still not agreed.

Do people want to introduce adoptedCallback at the same time? Seems kind of nice, "while we're there". But on the other hand it also seems kind of silly to introduce adoptedCallback when all the other v2 callback ideas are still not discussed, including e.g. the much more common clonedCallback. I could go either way.

---
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-230764837

Received on Wednesday, 6 July 2016 13:04:48 UTC