Skip to content
This repository was archived by the owner on May 29, 2019. It is now read-only.

Timepicker form validation is wrong when min or max timepicker attribute is used #6088

Closed
reinisp opened this issue Jul 13, 2016 · 1 comment

Comments

@reinisp
Copy link

reinisp commented Jul 13, 2016

Bug description: When updating invalid time with timpicker arrow buttons form is marked as valid even timepicker min time is greater than timepicker ng-model value.

Steps to reproduce:

  1. Open plunker demo
  2. Check that arrow to decrease minutes are disabled as current timepicker model equals min time
  3. Manually set timepicker minutes to e.g. 25
  4. Check that form is marked as invalid
  5. Use timepicker arrow button to increase minute value.

Observed Timepicker is marked as valid
Expected Timepicker is still invalid as min time is greater than timepicker model time

Link to minimally-working plunker that reproduces the issue: http://plnkr.co/edit/klAzTHNfGQE6jE5EhdMK?p=preview

Version of Angular, UIBS, and Bootstrap

Angular: 1.5.3

UIBS: 1.3.3

Bootstrap: 3.3.6

@icfantv
Copy link
Contributor

icfantv commented Jul 19, 2016

Closing in favor of #5957 as this will result in a complete rewrite of the widget, addressing all the outstanding issues.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants