Skip to content

Input Date Picker: Incorrect variable usage #13804

@fishNimo

Description

@fishNimo

monday.com sync: #11127783197

Check existing issues

Which Component

N/A, Input Date Picker

Actual Behavior

It uses selected-background-color instead of range-background-color.

--calcite-date-picker-day-range-background-color: var(--calcite-input-date-picker-calendar-selected-background-color)
Image

Expected Behavior

It should use range-background-color.

Reproduction Sample

Reproduction Steps

Sample 1

  1. Open the codePen
  2. Open a new tab for the demo container.
    Image
  3. Inspect the day DOM and observe.
    Image

Sample 2

  1. Open the sample
  2. Observe the first example using range-named tokens are not displaying as-expected
  3. Observe the second example with range is displaying the specified --calcite-input-date-picker-calendar-selected-background-color (the workaround, but not expected behavior)

Reproduction Version

[email protected]

Relevant Info

No response

Regression?

Last working version was 3.2.1, regression introduced at 3.3.0

Priority impact

impact - p0 - emergency

Impact

We're targeting the release of a new widget in 26R1, which will meet the needs of users and the internal team (e.g., LRS). This bug is currently blocking the development of this new widget with the input style.

Image

Calcite package

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

Esri team

ArcGIS Experience Builder

Metadata

Metadata

Assignees

No one assigned

    Labels

    ArcGIS Experience BuilderIssues logged by ArcGIS Experience Builder team membersbugBug reports for broken functionality. Issues should include a reproduction of the bug.c-input-date-pickerIssues that pertain to the calcite-input-date-picker componentcalcite-componentsIssues specific to the @esri/calcite-components package.estimate - 3A day or two of work, likely requires updates to tests.impact - p0 - emergencyUser set priority impact status of p0 - emergencyp - 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