Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Dropdown]: Enhance component's interactivity states #10019

Open
1 of 8 tasks
DitwanP opened this issue Aug 8, 2024 · 1 comment
Open
1 of 8 tasks

[Dropdown]: Enhance component's interactivity states #10019

DitwanP opened this issue Aug 8, 2024 · 1 comment
Labels
0 - new New issues that need assignment. 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 - 2 Small fix or update, may require updates to tests. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone p - high Issue should be addressed in the current milestone, impacts component or core functionality ready for dev Issues ready for development implementation.

Comments

@DitwanP
Copy link
Contributor

DitwanP commented Aug 8, 2024

Check existing issues

Description

Updates the dropdown's interactive states as part of the larger epic in #9299.

Current state

image

Acceptance Criteria

  • Remove icon color change on hover & press
  • Add 2px brand border on press

image

Relevant Info

No response

Which Component

dropdown

Example Use Case

No response

Priority impact

impact - p3 - not time sensitive

Calcite package

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

Esri team

Calcite (design)

@DitwanP DitwanP added enhancement Issues tied to a new feature or request. design Issues that need design consultation prior to development. p - high Issue should be addressed in the current milestone, impacts component or core functionality 0 - new New issues that need assignment. estimate - 2 Small fix or update, may require updates to tests. ready for dev Issues ready for development implementation. labels Aug 8, 2024
@github-actions github-actions bot added Calcite (design) Issues logged by Calcite designers. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. calcite-components Issues specific to the @esri/calcite-components package. labels Aug 8, 2024
Copy link
Contributor

github-actions bot commented Aug 8, 2024

cc @geospatialem, @brittneytewks

@DitwanP DitwanP added this to the 2025-04-29 - Apr Release milestone Aug 8, 2024
@github-actions github-actions bot added the impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive label Aug 8, 2024
@DitwanP DitwanP added impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone and removed needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive labels Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - new New issues that need assignment. 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 - 2 Small fix or update, may require updates to tests. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone p - high Issue should be addressed in the current milestone, impacts component or core functionality ready for dev Issues ready for development implementation.
Projects
None yet
Development

No branches or pull requests

1 participant