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

`aria-owns` is tricky because there are so many ways to get into loops and other pathological situations which need to be guarded against and tested for, since they can cause crashes. There are [a bunch of WPT tests](https://github.com/web-platform-tests/wpt/tree/39138b0492366aa07ef3e0cce12f67ff2de966a3/accessibility/crashtests) for crash scenarios just with vanilla `aria-owns`, plus [several more chrome-internal tests](https://source.chromium.org/search?q=f:content%2Ftest%2Fdata%2Faccessibility%20aria-owns%20crash&sq=&ss=chromium) (and probably others not picked up by that search).

I think to add `aria-owns` support we would probably at the very least need to write tests for cases similar to the cases already tested for vanilla `aria-owns`, for various combinations of
- `ariaOwnsElements`
- `ariaOwnsElements` on `ElementInternals`
- `referenceTarget`

It seems that the Firefox team are confident in their implementation of `ariaOwnsElements`, so they're happy to ship it, but I think the Chromium team feel that more work needs to be done before they would be comfortable doing the same. I'm not sure where WebKit stands, actually. But yeah, until Chromium is comfortable with shipping it, it won't be available in _all_ major engines.

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

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