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

[Button & Action]: Referenced tooltip isn't invoked on mobile devices #9273

Open
2 of 8 tasks
geospatialem opened this issue May 7, 2024 · 1 comment
Open
2 of 8 tasks
Assignees
Labels
1 - assigned Issues that are assigned to a sprint and a team member. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. Calcite (dev) Issues logged by Calcite developers. calcite-components Issues specific to the @esri/calcite-components package. estimate - 3 A day or two of work, likely requires updates to tests. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive p - medium Issue is non core or affecting less that 60% of people using the library spike Issues that cannot be estimated well enough until the team has done further research

Comments

@geospatialem
Copy link
Member

Check existing issues

Actual Behavior

On mobile devices both button and action components will not invoke a referenced tooltip on tap.

ios-demo.mp4

Expected Behavior

  • button should trigger a referenced tooltip on mobile devices on tap, similar to click
  • action should trigger a referenced tooltip on mobile devices on tap, similar to click

desktop

Reproduction Sample

https://codepen.io/geospatialem/pen/OJGKGrY

Reproduction Steps

  1. Open the sample on a mobile device
  2. Try to tap on either the button or action to invoke the associated tooltip
  3. Observe the behavior

Reproduction Version

2.8.0

Relevant Info

Tested on iOS

Regression?

No response

Priority impact

p4 - not time sensitive

Impact

No response

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 (dev)

@geospatialem geospatialem added bug Bug reports for broken functionality. Issues should include a reproduction of the bug. 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. labels May 7, 2024
@github-actions github-actions bot added calcite-components Issues specific to the @esri/calcite-components package. Calcite (dev) Issues logged by Calcite developers. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive labels May 7, 2024
@macandcheese
Copy link
Contributor

IMO this might be p2/p3 - this prevents mobile use of a lot of UI interactions.

@geospatialem geospatialem added the p - medium Issue is non core or affecting less that 60% of people using the library label May 8, 2024
@geospatialem geospatialem added estimate - 3 A day or two of work, likely requires updates to tests. spike Issues that cannot be estimated well enough until the team has done further research and removed needs triage Planning workflow - pending design/dev review. labels May 28, 2024
@geospatialem geospatialem added this to the 2024-08-27 - Aug Release milestone May 28, 2024
@driskull driskull self-assigned this May 31, 2024
@driskull driskull added 1 - assigned Issues that are assigned to a sprint and a team member. and removed 0 - new New issues that need assignment. labels May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - assigned Issues that are assigned to a sprint and a team member. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. Calcite (dev) Issues logged by Calcite developers. calcite-components Issues specific to the @esri/calcite-components package. estimate - 3 A day or two of work, likely requires updates to tests. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive p - medium Issue is non core or affecting less that 60% of people using the library spike Issues that cannot be estimated well enough until the team has done further research
Projects
None yet
Development

No branches or pull requests

3 participants