Re: [webcomponents] [Shadow] activeElement behavior seems to break encapsulation (#358)

My preference is option B in https://github.com/w3c/webcomponents/issues/358#issuecomment-168970241. Unless there is a use case where developers have a significant trouble with it, I think we can live in option B as the first step. I prefer keeping activeElement simple and understandable. I am not a fan of making it too magical one.

If we find a use case where we need an intelligent *magical* API, such as `x-foo.shadowRoot.magicalActiveElement -> slot`, we might want to provide such an magical API as another API, if it's difficult to implement in JS. However, developers still need a plain old activeElement anyway, I think. That's an orthogonal issue. Both cover different use cases. Thus, just making activeElement act a plain simple role should not be a bad choice.




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