Skip to content

Core: Support groups and info icon in highlight popover menu #31475

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

Merged
merged 8 commits into from
May 15, 2025

Conversation

ghengeveld
Copy link
Member

@ghengeveld ghengeveld commented May 14, 2025

Closes #31414

What I did

Split up the a11y popover menu to have a separate "Learn how to resolve this violation" button which links out to the Axe documentation. In order to support this I had to introduce the concept of groups to the menu structure, so it now expects an array of arrays of items rather than an array of items.

A handful of icons have been introduced in order to support the desired UX.

Screen.Recording.2025-05-14.at.15.45.53.mov

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

  • stories
  • unit tests
  • integration tests
  • end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

  • Add or update documentation reflecting your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Checklist for Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

  • Make sure this PR contains one of the labels below:

    Available labels
    • bug: Internal changes that fixes incorrect behavior.
    • maintenance: User-facing maintenance tasks.
    • dependencies: Upgrading (sometimes downgrading) dependencies.
    • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
    • cleanup: Minor cleanup style change. Will not show up in release changelog.
    • documentation: Documentation only changes. Will not show up in release changelog.
    • feature request: Introducing a new feature.
    • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
    • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

Greptile Summary

Enhanced the highlight popover menu functionality by adding support for grouped menu items and info icons, improving accessibility violation descriptions and links in the Storybook UI.

  • Added menuGroups property in code/core/src/highlight/types.ts to support nested menu item grouping
  • Updated normalizeOptions in code/core/src/highlight/utils.ts to handle both legacy and new highlight formats
  • Added new MenuGroups story in code/core/src/highlight/useHighlights.stories.tsx demonstrating grouped items with info icons
  • Fixed SVG attribute naming from camelCase to kebab-case in code/core/src/highlight/useHighlights.ts
  • Added null check for removeHighlight function to prevent errors

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

5 file(s) reviewed, 3 comment(s)
Edit PR Review Bot Settings | Greptile

Copy link

nx-cloud bot commented May 14, 2025

View your CI Pipeline Execution ↗ for commit 262cf42.

Command Status Duration Result
nx run-many -t build --parallel=3 ✅ Succeeded 1m 27s View ↗

☁️ Nx Cloud last updated this comment at 2025-05-14 14:09:03 UTC

@ghengeveld ghengeveld force-pushed the a11y-popover-content branch from a30bde5 to 666cc67 Compare May 14, 2025 12:11
document.getElementById(key)?.scrollIntoView({ behavior: 'smooth', block: 'center' });
}, 100);
const { helpUrl, nodes } = results?.[type as RuleType]?.find((r) => r.id === id) || {};
const openedWindow = helpUrl && window.open(helpUrl, '_blank', 'noopener,noreferrer');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isn't it bad for a11y if the link opens in a new tab?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe, I don't know. UX wise at least we have an icon to indicate this behavior. For screenreaders I have no idea whether this is okay or not. Either way I think as a general rule we should always be opening 3rd party links in a new tab.

@ghengeveld ghengeveld requested a review from ndelangen May 15, 2025 07:10
@storybook-pr-benchmarking
Copy link

Package Benchmarks

Commit: 4ea0d89, ran on 15 May 2025 at 07:35:17 UTC

The following packages have significant changes to their size or dependencies:

@storybook/vue3-vite

Before After Difference
Dependency count 103 103 0
Self size 34 KB 34 KB 0 B
Dependency size 42.77 MB 42.68 MB 🎉 -87 KB 🎉
Bundle Size Analyzer Link Link

@ghengeveld ghengeveld merged commit f150ac5 into next May 15, 2025
54 checks passed
@ghengeveld ghengeveld deleted the a11y-popover-content branch May 15, 2025 09:21
@github-actions github-actions bot mentioned this pull request May 16, 2025
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Accessibility addon: Violation content is not correct
2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy