Re: [WICG/webcomponents] Reference Target: Which attributes are in scope? (Issue #1091) from Aaron Leventhal on 2024-12-16 (public-webapps-github@w3.org from December 2024)

From: Aaron Leventhal <notifications@github.com>
Date: Mon, 16 Dec 2024 08:02:00 -0800
To: WICG/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <WICG/webcomponents/issues/1091/2546018425@github.com>

+1 to what Alice said. I think we'd want to create most of the same stability tests we have for aria-owns=IDREF but using ariaOwnsElements. Also, we put a request out there for use cases for aria-owns to cross shadow boundaries but heard nothing. I wanted to avoid a situation where a high implementation cost did not pay back in terms of supported use case. Note that regular aria-owns was really, really hard to get right. It's always been one of the leading culprits when the engine hits an assertion indicating that the current tree and processing were in an inconsistent state. It has funny ways of combining with other markup,

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

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

Received on Monday, 16 December 2024 16:02:04 UTC