Skip to content

[calcite-input-time-picker]: programmatically setting value after change doesn't always update value #12391

Open
@isaacbraun

Description

@isaacbraun

Check existing issues

Actual Behavior

When the value is programmatically set when calciteInputTimePickerChange fires, the value is not always set when the same part of the picker is changed three (3) times in a row.

On the third time the calciteInputTimePickerChange event does not fire, so the value is not reset. If the goal was to prevent a change from happening, using event.preventDefault() would be a workaround, but this issue could potentially present itself if a user wants to modify a value after the change happens.

Original discussion: #9259 (comment)

Expected Behavior

When setting the value programmatically while listening to the calciteInputTimePickerChange event, the value should be set every time an input is made.

Reproduction Sample

https://codepen.io/isaacbraun/pen/JodmpxN

Reproduction Steps

Steps listed in CodePen.

Reproduction Version

3.3.0-next.20

Relevant Info

No response

Regression?

No response

Priority impact

impact - p3 - not time sensitive

Impact

No response

Calcite package

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

Esri team

Calcite (dev)

Metadata

Metadata

Assignees

No one assigned

    Labels

    0 - newNew issues that need assignment.Calcite (dev)Issues logged by Calcite developers.bugBug reports for broken functionality. Issues should include a reproduction of the bug.impact - p3 - not time sensitiveUser set priority impact status of p3 - not time sensitiveneeds triagePlanning workflow - pending design/dev review.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions