Skip to content

[Action] active calcite-actions don't change background color when used within selection-appearance="highlight" #13690

@isaacbraun

Description

@isaacbraun

monday.com sync: #10995170097

Check existing issues

Which Component

Action

Actual Behavior

When a calcite-action used inside of a calcite-action-bar with selection-appearance="highlight" is set to active, only the text color changes and not the background color.

Expected Behavior

The background color should be changed to --caclite-color-surface-highlight.

Reproduction Sample

https://codepen.io/isaacbraun/pen/jErVKag

Reproduction Steps

  1. Open the Sample
  2. Observe the first Action in the "Highlight selection ..." sample does not have its background color changed.

If the CDN version is changed to 5.0.0-next.61, the highlight color works but the active transparent Actions do not have the correct background color.

Reproduction Version

5.0.0-next.60

Relevant Info

This is a CSS specificity issue. A fix was attempted in #13686 but it broke the active styling for calcite-actions using appearance="transparent".

Regression?

5.0.0-next.17

Priority impact

impact - p1 - need for current milestone

Impact

No response

Calcite package

  • @esri/calcite-components
  • @esri/calcite-components-react
  • @esri/calcite-design-tokens
  • @esri/calcite-ui-icons
  • @esri/eslint-plugin-calcite-components

Esri team

Calcite (dev)

Metadata

Metadata

Assignees

Labels

5 - verifiedIssues that have been tested, confirmed as mitigated, and are ready to close.Calcite (dev)Issues logged by Calcite developers.bugBug reports for broken functionality. Issues should include a reproduction of the bug.c-actionIssues that pertain to the calcite-action componentcalcite-componentsIssues specific to the @esri/calcite-components package.estimate - 2Small fix or update, may require updates to tests.impact - p1 - need for current milestoneUser set priority impact status of p1 - need for current milestonep - highIssue should be addressed in the current milestone, impacts component or core functionalityregressionIssues that are caused by changes in a release, but were working before that.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions