Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Improve context menu theming for light and dark mode#690

Open
theEquinoxDev wants to merge 17 commits intowebpack:main from
theEquinoxDev:improve-contextmenu-theming
Open

Improve context menu theming for light and dark mode #690
theEquinoxDev wants to merge 17 commits intowebpack:main from
theEquinoxDev:improve-contextmenu-theming

Conversation

@theEquinoxDev
Copy link
Contributor

@theEquinoxDev theEquinoxDev commented Jan 12, 2026
edited
Loading

This PR updates the context menu styling to better align with the existing theme variables.

Context

While reviewing tooltips and context menus as part of the recent dark mode work, I noticed that the right-click context menu was still using hard-coded colors and that disabled items had low contrast. This behavior exists in both light and dark mode, but is more noticeable in dark mode.

What changed

  • Context menu background and border now use existing theme variables (--bg-primary, --border-color)
  • Disabled context menu items use the existing --text-secondary variable to preserve the disabled appearance
  • Hover and interaction behavior remains unchanged

Screenshots

Light mode
(Earlier PR)
Screenshot 2026年01月12日 223406

(Latest PR)
Screenshot 2026年01月13日 130503

Dark mode
(Earlier PR)
Screenshot 2026年01月12日 223353

(Latest PR)
Screenshot 2026年01月13日 130447

Could you please let me know if this level of contrast matches what you had in mind, or if you'd prefer it to be adjusted further?
Happy to iterate based on feedback.

here's the screenshot of the contrast ratio -
image

theEquinoxDev and others added 13 commits December 9, 2025 10:15
- Fix PR link to point to webpack/webpack-bundle-analyzer
- Add proper GitHub profile attribution @theEquinoxDev
- Follow established changelog format consistency
Copy link
Member

@theEquinoxDev thanks! The disabled option isn't really different enough from the available one, at least in the screenshot you gave. Can you check that?

Copy link
Contributor Author

Thanks for the feedback!
I agree, the disabled state might not be distinct enough from the enabled one. I'll tweak it further and and make it more clearly differentiated and update the PR with new screenshots.

Copy link
Contributor Author

I updated the disabled styling to make it more visually distinct and replaced the screenshots with the latest version. Could you please take another look?

Copy link
Member

Ah sorry, were the menu buttons always disabled? I thought that some parts of the menu would be clickable while others weren't but was it so that all these menu buttons in your screenshots have always been disabled?

You could use some a11y contrast tool, maybe Silktide https://silktide.com/toolbar/ or the browser native color contrast tools to verify if they have at least 4.5:1 color contrast to be readable enough.

Copy link
Contributor Author

Thanks for checking! from what i noticed, these buttons were always disabled. I tried clicking them, but it was disabled from the start.
I'll also run the colors through a contrast checker as suggested and report back if any adjustments seems necessary.

Copy link
Member

Huh... I wonder how this feature used to work. Maybe it was tied to the checkboxes in the side navigation somehow? 😅

Copy link
Contributor Author

I haven't touched the enable/disable logic at all, only the styling.
From my testing, the options shown in the screenshots are disabled based on the current selection state, and I wasn't able to find a scenario where those particular items become enabled.
It's possible they were intended to be tied more closely to sidebar selection or checkboxes earlier on, but I didn’t dig into historical behavior beyond what;s currently observable.
Though, if you could guide me, I can take a look upon this. let me know what exactly do i need to check.

Copy link
Contributor Author

I checked the contrast using the browser contrast tools and it says - the disabled menu items have a contrast ratio of 6.37:1,

From an accessibility standpoint this should be readable enough but if you'd still prefer the disabled state to be visually more emphasized beyond that, I'm happy to adjust the styling further. I've also attached the screenshot of the contrast ratio. you can have a look at that.

Copy link
Contributor Author

Just a quick follow-up on this - I verified the contrast (6.37:1, WCAG AA) and updated the screenshots accordingly.
Let me know if this looks good to you or if you'd prefer the disabled state to be emphasized more. Happy to adjust either way

Copy link
Member

Ok thanks! I'll get back to this PR after the rest of the refactoring pull requests we're currently doing in this repository are over.

Copy link
Contributor Author

Sounds good, thanks for the update! I'll wait until the refactoring PRs are done.😊

Copy link

codecov bot commented Feb 16, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.35%. Comparing base (2588e54) to head (4620cc5).

Additional details and impacted files
@@ Coverage Diff @@
## main #690 +/- ##
=======================================
 Coverage 70.35% 70.35% 
=======================================
 Files 17 17 
 Lines 914 914 
 Branches 308 308 
=======================================
 Hits 643 643 
 Misses 238 238 
 Partials 33 33 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@alexander-akait alexander-akait alexander-akait approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Comments

AltStyle によって変換されたページ (->オリジナル) /