Completed
Last Updated: 08 Aug 2022 13:17 by ADMIN
Release R3 2022 - Increment 2 (03.08.2022)

Describe the bug
When we have multiple TimePickers on a page and start expanding their popups, the popups that are already expanded are not automatically closing.

To Reproduce

  1. Open this StackBlitz example
  2. Click on the "clock" icon of a random TimePicker to open its popup
  3. Repeat step 2 over other randomly selected TimePicker

Expected behavior
The visible popup of a TimepPicker should be automatically closed when we expand the popup of another TimePicker

Screenshots
image

Completed
Last Updated: 04 Apr 2022 12:24 by ADMIN

Describe the bug
The Native TimePicker component throws a console error when a value is passed to its steps property.

To Reproduce

  1. Open this StackBlitz example
  2. Click on the TimePicker to expand its popup
  3. Open the browser's console

Expected behavior
There shouldn't be any Javascript errors when working with the Timepicker

Screenshots
image

Completed
Last Updated: 04 Apr 2022 12:22 by ADMIN
Created by: jake
Comments: 0
Category: TimePicker
Type: Bug Report
1

Describe the bug
There are issues with the selection of the "min" and "max" values of the TimePicker when such are selected for the component.

  • The 'min' value cannot be the first selection the user makes after the initialization of the component. If the user opens the TimePicker's popup, the min value is selected by default. If one clicks on the "Set" button the min value should be selected but instead, the value is 12:00 AM.
    If the user selects a value different from the min, and then tries to select the min, the minimum value is correctly selected.
  • The max value is correctly selected but the component treats it as an invalid value.

To Reproduce

  1. Open this StackBlitz example
  2. To test the min value issue open the TimePicker and click on the "Set" button
  3. To test the max value issue, open the TimePicker and select 10:15 PM in the popup

Expected behavior
Both the min and max values defined for the component should be selectable and valid values in all use-case scenarios of the TimePicker.

Completed
Last Updated: 04 Apr 2022 07:27 by ADMIN

Describe the bug
The TimePicker with custom inputs is working correctly until we use the Tab button to switch from one input to another. When the Tab button is pressed, an error appears in the console and breaks the application.

To Reproduce

  1. Open this StackBlitz example
  2. Focus the first input inside the component
  3. Press the Tab button

Expected behavior
The focus should be changed to the second input

Screenshots
image