49
Views
2
Comments
[iMask Js] Imask Bugs
imask-js
Reactive icon
Forge asset by Paulo Moreira
Application Type
Reactive

Hi!

I've been testing iMask in depth, and I have found two addtional bugs.


First one is on copy&paste values. If mask supports a specific format, should allow copy&paste values with this format. But, if you have a value like this "12.345,67" and you paste IT into iMask input, the result is this one: "12,34".


In the other hand, the second problem is because of how I think it works internally, creating a second input, that is visible and has the "masked vale". If you put "configs", or change parameters in execution time, or put events, this element are not present in the "masked input", so are a few elements that are not working: 

  • configurations in some propertys , like prompt, etc.
  • events like blur, focus, etc
  • changing values in execution time in input, for example enable or disable input with a variable, or change a class with a function (all this change are applied to original input).
  • Use widget Id to anything (because this id is the ID of original hidden input)


Best regards,
Carlos.

UserImage.jpg
Tiago Alves

Hello,


Can you provide an oml with this example, for our team can analyze it?


Best Regards,
Tiago Alves

2017-03-14 07-04-32
Carlos Olías

Sure!

Fist bug you can test it in iMask demo page, putting a Thousand separator "." and pasting this value: 1.234,56
https://personal-ylsejvx2.outsystemscloud.com/iMaskJsDemo/Number_Decimal


Second one, I attach a example OML.

In this example you can see how prompt is setted, but is showed only in original input, how when you click "set has enabled = false" OS put disabled in original input but not in masked input, same with a class, and how are a few events that type in javascript console, but logs are not showed (because the event is attached to original input). I believe that any config o change maded in original  input should be applied to masked input, even when these changes are produced dynamically by OS changes or by JS accesing by id to original input (widget.id), but this sounds really hard

This is an snapshot of chrome inspector:


Regards,

TestImaks.oml
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.