Skip to content

[Design Tokens] Update light-mode border colors for 4.0 #10755

@geospatialem

Description

@geospatialem

Check existing issues

Description

Update values of semantic tokens border color tokens.

Blocked issues: #10769

🔗 Figma Specs: https://www.figma.com/design/i2p9r2mzxWqQmEW6Ya9nwg/%5BToken%5D-Update-border-colors-for-4.0?node-id=4501-714&m=dev

Image

Acceptance Criteria

Light mode border colors updated:

  • border.1=core.neutral.blk.040
  • border.2=core.neutral.blk.030
  • border.3=core.neutral.blk.020

Relevant Info

Part of 4.0's Phase I - Colors

Which Component

Tokens

Example Use Case

Refer to relevant info above.

Priority impact

impact - p3 - not time sensitive

Calcite package

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

Esri team

Calcite (design)

monday.com sync: #9367059839

Metadata

Metadata

Assignees

No one assigned

    Labels

    0 - newNew issues that need assignment.Calcite (design)Issues logged by Calcite designers.calcite-componentsIssues specific to the @esri/calcite-components package.calcite-design-tokensIssues specific to the @esri/calcite-design-tokens package.designIssues that need design consultation prior to, or during, development.design-tokensIssues requiring design tokens.enhancementIssues tied to a new feature or request.estimate - 3A day or two of work, likely requires updates to tests.impact - p3 - not time sensitiveUser set priority impact status of p3 - not time sensitivemonday.com syncMonday.com syncp - highIssue should be addressed in the current milestone, impacts component or core functionalityready for devIssues ready for development implementation.visual changesIssues with visual changes that are added for consistency, but are not backwards compatible.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions