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

Allow native focus options to be passed in to setFocus #8132

Open
2 of 5 tasks
LanceStasinski opened this issue Nov 6, 2023 · 0 comments
Open
2 of 5 tasks

Allow native focus options to be passed in to setFocus #8132

LanceStasinski opened this issue Nov 6, 2023 · 0 comments
Labels
0 - new New issues that need assignment. ArcGIS Field Apps Issues logged by ArcGIS Field Apps team members. calcite-components Issues specific to the @esri/calcite-components package. enhancement Issues tied to a new feature or request. estimate - 8 Requires input from team, consider smaller steps. 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 - low Issue is non core or affecting less that 10% of people using the library

Comments

@LanceStasinski
Copy link

Check existing issues

Description

Since the setFocus method on calcite-input calls the native focus method, setFocus should accept the native focus options: https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/focus#parameters. For example, the preventScroll option is useful to prevent clashing between css animations and browser scrolling.

Acceptance Criteria

The setFocus method on a calcite-input element should accept native focus methods and call focus with those options.

Relevant Info

https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/focus#parameters

Which Component

Any component with a setFocus method (eg. calcite-input, calcite-input-number, calcite-input-text, etc.).

Example Use Case

calciteInput.setFocus({ preventScroll: true })

Priority impact

p4 - not time sensitive

Calcite package

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

Esri team

ArcGIS Field Apps

@LanceStasinski LanceStasinski added 0 - new New issues that need assignment. enhancement Issues tied to a new feature or request. needs triage Planning workflow - pending design/dev review. labels Nov 6, 2023
@github-actions github-actions bot added calcite-components Issues specific to the @esri/calcite-components package. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive ArcGIS Field Apps Issues logged by ArcGIS Field Apps team members. labels Nov 6, 2023
@geospatialem geospatialem added p - low Issue is non core or affecting less that 10% of people using the library estimate - 8 Requires input from team, consider smaller steps. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. and removed needs triage Planning workflow - pending design/dev review. labels Aug 6, 2024
@geospatialem geospatialem added this to the 2025-03-25 - Mar Release milestone Sep 10, 2024
@geospatialem geospatialem removed the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Sep 10, 2024
@geospatialem geospatialem added the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Feb 24, 2025
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. ArcGIS Field Apps Issues logged by ArcGIS Field Apps team members. calcite-components Issues specific to the @esri/calcite-components package. enhancement Issues tied to a new feature or request. estimate - 8 Requires input from team, consider smaller steps. 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 - low Issue is non core or affecting less that 10% of people using the library
Projects
None yet
Development

No branches or pull requests

3 participants