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

> It seemed to me that only three new flags were necessary and could be plumbed through the existing DOM:

Nice. This doesn't seem so bad. You also need hidden parent I believe.

However, @annevk was pretty convinced this kind of plumbing would be infeasible. Anne, does the above analysis change your opinion? If not, maybe you could remind us why it's so hard with a quick counterexample?

> I think this could work in conjunction with Parser-created Constructors.

Probably can avoid this and just use the Dmitry proposal with constructor trick to get the best of all worlds. I suppose I should write that up some time so we can refer to it...

> Also, these flags and states could be managed by a proxy just as easily--does this proposal just boil down to a specific kind of Proxy object?

This isn't really clear to me. E.g. `Element.prototype.getAttribute.call(proxyObj, "foo")` would not be properly disallowed for any simple proxy I can imagine. I think the flags are a better way of thinking of this.

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