-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reflection proposal: Expose internal elements to be referenced from the outside #23
Comments
I wonder how many use cases we have outside of label for going in both directions. Perhaps if we address labels semantically with a FACE proposal we can sidestep that use case entirely. |
And even for I guess the question is whether the custom element can be both the target and originator of a labelledby pointer and that seems highly implausible. |
@mrego Is your main concern with the name "reflection"? In the explainer, this is sometimes called "exporting." |
The name is confusing to me, as I think about ARIA attribute reflection when I read it; and this is something else. And yeah I guess that's why the explainer uses a different name in some parts. Anyway it would be nice to agree on a good name for this. |
I'm not a fan of the name "Cross-root ARIA Reflection" that's why the title of the issue is longer than expected. I think it can be confused with ARIA attribute reflection and be misleading in some situations.
The problem is that you want to make a relationship between something that is in a shadow tree and something from outside the shadow tree, somehow exposing/exporting/reflecting that information outside of the Shadow DOM.
Anyway this issue is to discuss what's the best approach to solve this issue. In the explainer we're describing a few options. Let's discuss them here.
Once we agree on a proposal we can bikeshed about the best name and syntax for it.
The text was updated successfully, but these errors were encountered: