# \[IGN-2441\] Text Area Property Change not Firing with On-Screen Keyboard **URL:** \ **Category:** Ignition\ **Tags:** ignition81, vision\ **Created:** [September 10, 2024, 8:29pm UTC](https://forum.inductiveautomation.com/t/ign-2441-text-area-property-change-not-firing-with-on-screen-keyboard/95818 "2024-09-10T20:29:42Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [September 10, 2024, 8:29pm UTC](https://forum.inductiveautomation.com/t/ign-2441-text-area-property-change-not-firing-with-on-screen-keyboard/95818/1 "2024-09-10T20:29:42Z")
I've opened a ticket and awaiting a response, but I think I just found a bug with the Vision Text Area component. If I use a regular keyboard and update a value in a text area, my named query update binding works as expected, but if I have a touchscreen and use the on-screen keyboard to change the value, the binding never fires after pressing enter on the on-screen keyboard, and even after losing focus, it also never updates. As a test, I put a propertyChange script on it also to just show a message box with the new value whenever the text property changes, and it does the same. It never fires with the on-screen keyboard (even after focus loss), but using a regular keyboard after losing focus, it fires. Anyone else seen this? Any fixes or anything I'm missing while I wait on support? Edit: Support came back with an internal bug ticket IGN-2441 which I tagged in the title now for reference, but they suggested trying to run my update to my database using the focusLost event, which is working as a workaround. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [September 10, 2024, 8:32pm UTC](https://forum.inductiveautomation.com/t/ign-2441-text-area-property-change-not-firing-with-on-screen-keyboard/95818/2 "2024-09-10T20:32:05Z")
It isn't just your case. It doesn't fire when a value is delivered by a binding, either. I'm not sure what version introduced it. Bindings to `.text` only get some updates. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [September 10, 2024, 9:45pm UTC](https://forum.inductiveautomation.com/t/ign-2441-text-area-property-change-not-firing-with-on-screen-keyboard/95818/4 "2024-09-10T21:45:51Z")
Just as a test, I bound a label text property to the text area's text property, and exactly as you described, my label showed blank even though my text area had a value from the binding. If I entered a new value using a regular keyboard and changed focus, then it updated the label, but the on-screen keyboard changes didn't cause the label to update either. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [September 10, 2024, 10:51pm UTC](https://forum.inductiveautomation.com/t/ign-2441-text-area-property-change-not-firing-with-on-screen-keyboard/95818/5 "2024-09-10T22:51:08Z")
The workaround I used was to another custom property, move the original `.text` binding to it, and bidirectionally bind from `.text` to `.custom`. Then did any other binding and propertyChange checking against `.custom`. Not sure if that would fix the on-screen keyboard behavior.