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

Thanks @bicknellr for the updates in detail!

@rniwa, I don't buy the "ShadowRoot.activeElement is a new API and we can do anything
as we like" argument much. What @haytatoito put is not a concern about compatibility
for Blink's legacy implementation, but I understand that Document and ShadowRoot should
keep consistent API semantics as much as possible if they share the same interface, and
if they diverge, it gets confusing to users, error prone to implement etc.  So the option B.

On the other hand, I understand it would be nice for a developer to have a way to know
if a shadow root has focus within or its slots' assigned descendants flat tree-wise.
How about having one in a different name for https://github.com/w3c/webcomponents/issues/358#issuecomment-202256430 or https://github.com/w3c/webcomponents/issues/358#issuecomment-202655660 ?

---
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/358#issuecomment-203767069