You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I already had some weird issues before with the attribute value on anything else then text and integers, but I think I found the culprit.
The generic approach for getting any attribute through the getAttribute() function doesn't work with value. That's why decimal inputs don't update when you bind the value with attribute.value(...).
You can just bind it to some string. Then try to type 121.23. you will see that the dot will never be inserted. If you use any special character like ",", ";" it will completely remove the input. When you comment out the attribute.value input it will undo the wrong binding.
The text was updated successfully, but these errors were encountered:
Bug
I already had some weird issues before with the attribute value on anything else then text and integers, but I think I found the culprit.
The generic approach for getting any attribute through the
getAttribute()
function doesn't work with value. That's why decimal inputs don't update when you bind the value withattribute.value(...)
.https://stackoverflow.com/questions/11973678/difference-between-element-value-and-element-getattributevalue
Maybe for
attribute.value
we can write a hack that will check for attribute name value and useelement.value
instead of the getAttribute(..).Steps to reproduce
Write something like this:
You can just bind it to some string. Then try to type
121.23
. you will see that the dot will never be inserted. If you use any special character like ",", ";" it will completely remove the input. When you comment out theattribute.value
input it will undo the wrong binding.The text was updated successfully, but these errors were encountered: