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

Input-named components behavior in line with inline-editable behavior #6566

Closed
geospatialem opened this issue Mar 4, 2023 · 1 comment
Closed
Labels
0 - new New issues that need assignment. Calcite (dev) Issues logged by Calcite developers. enhancement Issues tied to a new feature or request. estimate - 8 Requires input from team, consider smaller steps. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. p - medium Issue is non core or affecting less that 60% of people using the library

Comments

@geospatialem
Copy link
Member

Description

Update input-* components with inline-editable behavior common for all inputs. cc #5144

Acceptance Criteria

Similar behavior with inline-editable

Relevant Info

No response

Which Component

  • Input
  • Input number
  • Input text
  • Input date picker
  • Input time picker

Example Use Case

No response

Esri team

Calcite (dev)

@geospatialem geospatialem added enhancement Issues tied to a new feature or request. 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. labels Mar 4, 2023
@github-actions github-actions bot added the Calcite (dev) Issues logged by Calcite developers. label Mar 4, 2023
@geospatialem geospatialem added p - medium Issue is non core or affecting less that 60% 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 Jan 22, 2024
@geospatialem
Copy link
Member Author

Closing in favor of #6153 - added context that support should include all input-named components.

@geospatialem geospatialem closed this as not planned Won't fix, can't repro, duplicate, stale Jan 22, 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 (dev) Issues logged by Calcite developers. enhancement Issues tied to a new feature or request. estimate - 8 Requires input from team, consider smaller steps. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. p - medium Issue is non core or affecting less that 60% of people using the library
Projects
None yet
Development

No branches or pull requests

1 participant