Wj-input-number partially broken if used outside <form>

Wj-input-number partially broken if used outside <form>

Posted by: patrick.maurer on 13 April 2018, 5:18 am EST

• 

  patrick.maurer

  • Post Options:
  • Link
    Copy

  Posted 13 April 2018, 5:18 am EST

  We noticed a regression in the wj-input-number for empty (null or undefind) values if the control is used with ngModel but outside element.

  If the value is null, it displays 0 even though isRequired is false.

  Reproduction:

  https://stackblitz.com/edit/angular-ueettn?file=app%2Fapp.component.html

  If using inside it works as expected.

• 

  abhishek.dutta

  

  • Post Options:
  • Link
    Copy

  Posted 16 April 2018, 4:21 am EST

  Hi,

  We were able to replicate the issue at our end and it seems like a bug. The issue has been forwarded to the concerned team.

  Thanks for reporting the issue.

  Tracking ID ( Internal) - 317591