Skip to content
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

Clarify the scope #27

Open
annevk opened this issue Mar 14, 2023 · 4 comments · May be fixed by #28
Open

Clarify the scope #27

annevk opened this issue Mar 14, 2023 · 4 comments · May be fixed by #28

Comments

@annevk
Copy link

annevk commented Mar 14, 2023

As far as I can tell there's only 8 ARIA attributes that can point to elsewhere in the tree. It would be useful to call those out to make it clear exactly what problems are attempted at being solved.

@alice
Copy link

alice commented Mar 15, 2023

+1, I'd love to have a good set of working examples to reason about.

@leobalter
Copy link
Owner

pinging @nolanlawson @gonzalocordero @caridy for support here.

nolanlawson added a commit that referenced this issue Mar 20, 2023
Fixes #27

I also went ahead and renamed "popup" to "popover," since [that's the new name](https://developer.chrome.com/docs/web-platform/popover-api/).
@nolanlawson
Copy link
Collaborator

Opened a PR: #28

@alice
Copy link

alice commented Jun 12, 2023

The list helps, but I think we need more.

For each attribute, it would be good to have pointers to some usage examples, preferably in production code (e.g. a demo page for a component or whatever).

I think the critical issue @annevk is trying to understand is whether for each attribute there's a tendency to refer either in to shadow roots or out of them, with a view to understanding whether something like CSS parts could do the job for both the referring-into problem and the serialization problem (i.e. that you could set things up so references always go inwards, and use a CSS parts-like design which is inherently serializable).

I think I'm trying to generally understand the contours of the interlocking refer-into-shadow-root and serialization problems. For example, my assumption is that except in the "semantic delegate" type case (where the fact that you're referring into a shadow root is really an implementation detail), references into a shadow root involve some degree of knowledge of what's inside (e.g. if you're referring to an active descendant within a shadow root, you know that the thing you're referring to has an appropriate role). (This is why I find the CSS parts-style solution somewhat appealing, because it kind of makes that explicit by providing a "public API"; however, it wouldn't necessarily solve the serialization problem.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants