-
Notifications
You must be signed in to change notification settings - Fork 8
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
nimble-toggle-tip Component #1876
Comments
We should consider re-enabling the tooltip matrix tests when we work on this feature. #1106 |
# Pull Request ## 🤨 Rationale Define the interaction design patterns needed to implement the [nimble-toggle-tip Component](#1876) ## 👩💻 Implementation Leveraged much of the pattern established by the Accordion IxD spec. ## 🧪 Testing None ## ✅ Checklist <!--- Review the list and put an x in the boxes that apply or ~~strike through~~ around items that don't (along with an explanation). --> - [x] I have updated the project documentation to reflect my changes or determined no changes are needed.
The SLE schedule view introduced a toggle-tip-like component in this PR. It uses the info icon but only shows more info on hover, not click. When this component is available we should look at replacing that (and see if there are other SLE apps that have adopted similar patterns, possibly by searching source for that icon). Edit: there's also the context help shared SLE component |
😯 Problem to Solve
Complex forms and editor views built with nimble input components require field specific context help. While we've previously considered creating a nimble-tooltip to show contextual information, a nimble-toggle-tip has several benefits over the tooltip.
Persistence: A toggle-tip stays visible until the user decides to close it. This allows the user to interact with the information, such as copying text or clicking links. Tooltips, on the other hand, typically disappear when the user moves the cursor.
Keyboard accessibility: The user can use the keyboard to focus on the toggle-tip icon and open or close the toggle-tip with only the keyboard.
Complex Information: Toggle-tips can be better for displaying more complex information, including images, links, or formatted text. Tooltips are usually limited to simple, short text.
Mobile Friendliness: Toggle-tips can be more mobile-friendly as they can be triggered by taps and remain visible. Tooltips often rely on hover interactions, which don't translate well to touch interfaces.
💁 Proposed Solution
The toggle-tip will be predominately added to control labels.
Consider:
References:
Other reference components:
📋 Tasks
nimble-toggle-tip interaction design issueThe text was updated successfully, but these errors were encountered: