Replace inconsistent shadow styles with new shadow tokens #10050
Labels
1 - assigned
Issues that are assigned to a sprint and a team member.
ArcGIS Online
Issues logged by ArcGIS Online team members.
calcite-components
Issues specific to the @esri/calcite-components package.
calcite-components-react
Issues specific to the @esri/calcite-components-react package.
calcite-design-tokens
Issues specific to the @esri/calcite-design-tokens package.
design
Issues that need design consultation prior to development.
design-tokens
Issues requiring design tokens.
enhancement
Issues tied to a new feature or request.
impact - p2 - want for an upcoming milestone
User set priority impact status of p2 - want for an upcoming milestone
p - low
Issue is non core or affecting less that 10% of people using the library
ready for dev
Issues ready for development implementation.
Milestone
Check existing issues
Blocked issues: #9758
Description
A handful of Calcite components use a different shadow style than the tailwind style
shadow.2
. Most of them currently use the style "0 0 16px 0 rgba(0, 0, 0, 0.16)." Some are inheriting the style from the classes "calcite-floating-ui-anim" + "calcite-floating-ui-anim--active." Those components' shadow styles need to be replaced withshadow.2
in the code.Acceptance Criteria
Ensure the opacities used in shadow tokens are set in core
Add new semantic black color tokens for use with shadows:
color.shadow.1
color.shadow.2
color.shadow.3
Add new semantic shadow tokens:
shadow.sm
= box-shadow: 0px 2px 8px 0px {semantic.color.shadow.3}, 0px 2px 8px 0px {semantic.color.shadow.1};shadow.md
= box-shadow: 0px 6px 20px -4px {semantic.color.shadow.3}, 0px 4px 12px -2px {semantic.color.shadow.2};Apply shadow tokens as listed in Which Component section below.
Relevant Info
Figma spec reference
Which Component
shadow.sm
display-mode=“float-all” | “float-content” | “overlay”
shadow.md
Priority impact
impact - p2 - want for an upcoming milestone
Calcite package
Esri team
ArcGIS Online
The text was updated successfully, but these errors were encountered: