Re: [w3ctag/design-reviews] Reference Target (Issue #961)

I'm not sure I see a practical difference between the two contexts that you're referencing @LeaVerou. While the code above is a very reduced reproduction, the workflow I outlined applies to the work I've seen or been a part of across a number of roles I've worked in. Whether building [Spectrum Web Components](https://opensource.adobe.com/spectrum-web-components) where we commonly worked to translate examples like those found in [ARIA APG](https://www.w3.org/WAI/ARIA/apg/) into abstract reusable/customizable element or building interactive virtual classrooms, digital asset management or creativity tools that rely on larger custom element architectures, I see this approach being valuable in the way that it manages ID references much like they would be used without shadow DOM.

But, maybe I'm misunderstanding the context you're outlining. Would you be able to share some code outlining how that context would be different? Something that helped clarify how this context would benefit from managing ID references via this net new API surface?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/961#issuecomment-2438417124
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/961/2438417124@github.com>