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

> We investigated the adoption agency algorithm in the past and found that it can't create a custom element although it's possible to have is= on them. This was yet another reason we didn't want to support is= since it's just not possible to run arbitrary scripts during the adoption agency algorithm safely.

By "create" do you mean "remove and re-insert"? I am not concerned about creating as much as with removing from one iframe and reinserting in another.

> This is generally true already because pre-insert needs to ensure pre-insertion validity which can throw a bunch of exceptions such as HierarchyRequestError and NotFoundError.

Right, but those exceptions cannot happen when called from browser code, because browser code never violates the invariants they are enforcing.

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