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

Since `ShadowRoot` is a new API, it should be fine to return a slot element in `ShadowRoot.activeElement`.  I don't see why `activeElement` always need to return a focusable element either.  The primary reason an author uses `activeElement` is to determine where the focus is.  For that use case, it's a lot more useful for `activeElement` to return the slot than `null`.

Furthermore, whether an element generates a CSS box or not is nothing to do with whether an element is focusable or not.  For example, elements in the fallback contents of a canvas element can be focusable but they never generate CSS boxes.

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