Update components to account for new v4.0 calcite-action
design
#10777
Labels
0 - new
New issues that need assignment.
blocked
This issue is blocked by another issue.
Calcite (design)
Issues logged by Calcite designers.
calcite-components
Issues specific to the @esri/calcite-components package.
design
Issues that need design consultation prior to development.
enhancement
Issues tied to a new feature or request.
estimate - 5
A few days of work, definitely requires updates to tests.
impact - p3 - not time sensitive
User set priority impact status of p3 - not time sensitive
needs milestone
Planning workflow - pending milestone assignment, has priority and/or estimate.
p - high
Issue should be addressed in the current milestone, impacts component or core functionality
ready for dev
Issues ready for development implementation.
visual changes
Issues with visual changes that are added for consistency, but are not backwards compatible.
Check existing issues
Description
The changes to Actions from issue #10759 necessitate updates to any components that use Actions. Outlined below on a per-component basis:
Overview example using a representative set of components showing updated spacing and improved alignment:

Acceptance Criteria
Accordion Item
Alert
calcite-action
for close buttonBlock
Chip
calcite-action
for close buttonCombobox / Input Time Zone
calcite-action
for clear buttonFlow / Flow Item
Inline Editable
calcite-action
for clear buttonInput & Input Text
calcite-action
for clear buttonList
List Item
Navigation
Notice
calcite-action
for close buttonPanel / Dialog
Popover
calcite-action
for close buttonTab Title
calcite-action
for close buttonTable
Tip / Tip Manager
Tree Item
Relevant Info
Part of 4.0's Phase 2
Blocked by: #10759
Which Component
See above.
Example Use Case
No response
Priority impact
impact - p3 - not time sensitive
Calcite package
Esri team
Calcite (design)
The text was updated successfully, but these errors were encountered: