Skip to content

chore: Fix style specificity issue in custom style flashbar#4684

Draft
at-susie wants to merge 2 commits into
mainfrom
onetheme/flashbar-style-fix
Draft

chore: Fix style specificity issue in custom style flashbar#4684
at-susie wants to merge 2 commits into
mainfrom
onetheme/flashbar-style-fix

Conversation

@at-susie

@at-susie at-susie commented Jul 1, 2026

Copy link
Copy Markdown
Member

Description

This PR fixes the specificity issue that we found in the regression in a screenshot test in the pages/flashbar/style-custom.page.tsx page, which was introduced in #4671

Related links, issue #, if available: n/a

How has this been tested?

Review checklist

The following items are to be evaluated by the author(s) and the reviewer(s).

Correctness

  • Changes include appropriate documentation updates.
  • Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
  • Changes do not include unsupported browser features, see CONTRIBUTING.md.
  • Changes were manually tested for accessibility, see accessibility guidelines.

Security

Testing

  • Changes are covered with new/existing unit tests?
  • Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@codecov

codecov Bot commented Jul 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.57%. Comparing base (92c5d7e) to head (ff6da7f).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4684   +/-   ##
=======================================
  Coverage   97.57%   97.57%           
=======================================
  Files         948      948           
  Lines       30496    30502    +6     
  Branches    11155    11160    +5     
=======================================
+ Hits        29756    29762    +6     
+ Misses        733      693   -40     
- Partials        7       47   +40     

☔ View full report in Codecov by Harness.
📢 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.

…mponents

Revert flashbar-icon button variant to use colorTextInteractiveInverted*
tokens instead of colorTextInteractive*. The previous approach overrode
colorTextInteractiveDefault in flashbar contexts, which broke
board-components (and any other package using that token inside a flashbar).

The fix uses colorTextInteractiveInvertedDefault/Hover in contexts where
the dismiss button needs different colors:
- VR/classic flashbar: inherits global inverted values (light on dark)
- VR flashbar-warning: overrides inverted to dark values (dark on light)
- One-theme flashbar/warning: overrides inverted to dark values (dark on light)
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 this pull request may close these issues.

1 participant