Re: [WICG/webcomponents] [element-internals] How to get internals in base class and subclass, without leaking it to public (Issue #962)

aarongustafson left a comment (WICG/webcomponents#962)

I know it’s slightly off-topic, but in this discussion it’s worth considering that any changes to protect `ElementInternals` needs to be done in such a way that it doesn’t undermine our ability to test the accessibility of a custom element. Directly interacting with the Accessibility Object Model is one of the core functions of this feature. If we can’t access `ElementInternals` to read how the custom element is plumbed into the AOM, there’s no way to test for issues. That said, read-only access to the current state would be fine.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/962#issuecomment-2898874564
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/962/2898874564@github.com>