Re: [webcomponents] [Custom Elements] Write-up proposal for using a "state object" (#287)

Well, with this https://dom.spec.whatwg.org/#concept-node-remove could fail. It can never fail now. So all callers would need to be updated to account for that. And all their callers too (e.g., replace all uses remove, and other bits, such as `innerHTML`, use replace all). Then for cases like `innerHTML` implementations would probably not want to regress performance, but now they need to do a check, so they might need to sprinkle some "has readonly child" bits around and make sure they get updated.

It's not impossible, but it comes at a cost, which I'm not sure we're willing to pay.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/287#issuecomment-126265914