-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Disclosure Component #6633
Comments
Are there any plans on pursuing this? I've seen a lot of teams using an OverflowMenu to achieve such interfaces which mostly results in invalid HTML (by not using I think a component like this which would allow for a wider range of use cases is desperately needed. |
@janhassel yes! 100%. I think the plan is to see if we can get it into the next sprint and tackle the exact case that you mentioned. Let me know if you want to help out at all with it! Happy to loop you in on any conversations if you're interested 😄 |
@janhassel just a heads up, we have a related component to this (Popover) that will be used in conjunction with the Disclosure component. Let me know if you want to help us test it out! |
We've seen a use-case crop up for a generic component that combines a trigger and a pop-up to enable a variety of use-cases. This primitive can be used by teams to build a variety of accessible functionality in their product.
At its core, this component would have two pieces:
Depending on the type of content, it may be useful for the pop-up to contain a way to close the pop-up (like a
X
present in a modal). Similarly, focus may need to be placed on the first item for certain cases like in a dialog pattern.In terms of focus order, the content in the pop-up should appear after the trigger. This means that a user can do the following:
2021 Release:
The text was updated successfully, but these errors were encountered: