Re: [WICG/webcomponents] Reference Target: Which attributes are in scope? (Issue #1091)

+1 to supporting everything if possible, including `aria-owns`. 

@aleventhal 
>  I think we'd want to create most of the same stability tests we have for aria-owns=IDREF but using ariaOwnsElements.

The web components community group likely can help fill in WPT for this, if that helps.

> Also, we put a request out there for use cases for aria-owns to cross shadow boundaries but heard nothing.

Sorry, I missed this. I don't have practical experience with `aria-owns`, but if it's still needed for cases like [combo-box](https://www.digitala11y.com/aria-owns-properties/#ariaowns-example), it would not be uncommon for, say, the input to be in a custom element's shadowRoot and the list of items to be its children, thus crossing shadow scopes. In general, it seems like `aria-owns` is necessary for exotic, tricky rendering which is potentially a good candidate to encapsulate in a custom element. This is contrived, but imagine an element that sorts children into groups based on some given grouping attributes and renders them visually in a grid (e.g. into even and odd: `odd: 1, 3, 5 even: 2, 4, 6`).

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

Message ID: <WICG/webcomponents/issues/1091/2548464660@github.com>