Remove zero with negative sign in wijmo input number

Remove zero with negative sign in wijmo input number

Posted by: tmurugasamy on 4 December 2017, 4:26 am EST

• 

  tmurugasamy

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 4 December 2017, 4:26 am EST

  Hi Guys,

  When i press negative sign in wijmo input number field, zero has been automatically added as -0.

  My requirement is zero should be added when press negative sign. Please guide me how to implement it.

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 4 December 2017, 10:41 pm EST

  Hi,
  
  We are investigating on this. We will update you soon.

  ~Manish

• 

  tmurugasamy

  • Post Options:
  • Link
    Copy

  Posted 5 December 2017, 1:26 am EST

  Hi Manish,

  A Typo error in my prior post.

  Here is my requirement - Zero should not be added when press negative sign.

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 5 December 2017, 4:27 pm EST

  Hi,
  
  The behavior you are observing is by design. As you enter (-) sign, 0 gets added with negative sign further as you type a number. 0 gets replaced with digit. On focusing out from control without entering any digit after pressing (-) sign, control value set to 0.

  Please elaborate your requirement with desired behavior.

  ~Manish

• 

  tmurugasamy

  • Post Options:
  • Link
    Copy

  Posted 5 December 2017, 6:11 pm EST

  Hi Mnish,

  Please, see the below link and enter (-) sign in the inputNumber field
  
  http://jsfiddle.net/rmsthiyagu/Cf9L9/75/

  I need the same behavior. 0 should be removed with negative sign when i enter (-) sign

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 6 December 2017, 11:34 pm EST

  Hi,
  
  We have forwarded your request to the concerned team for further investigation with internal tracking id 299899.

  We will let you know as we get any update on this.

  ~Manish

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 19 January 2018, 8:56 pm EST

  Hi,
  
  We are sorry for the late reply.
  
  This issue has been found fixed with pre-release build 5.20173.404. Please verify the issue with following fiddle:
  
  http://jsfiddle.net/mkgupta911/Cf9L9/76/

  This fix will be included in the build 5.20173.404+. Probably, the release will be announced in March 2018.

  ~Manish

• 

  tmurugasamy

  • Post Options:
  • Link
    Copy

  Posted 19 January 2018, 10:51 pm EST

  Thanks Manish