# \[BUG?\]Browser Virtual Keyboard Extensions don't write into input field text prop

**URL:** <https://forum.inductiveautomation.com/t/bug-browser-virtual-keyboard-extensions-dont-write-into-input-field-text-prop/76689>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [July 21, 2023, 2:15am UTC](https://forum.inductiveautomation.com/t/bug-browser-virtual-keyboard-extensions-dont-write-into-input-field-text-prop/76689 "2023-07-21T02:15:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [July 21, 2023, 5:19am UTC](https://forum.inductiveautomation.com/t/bug-browser-virtual-keyboard-extensions-dont-write-into-input-field-text-prop/76689/2 "2023-07-21T05:19:17Z")

</div>

None of the exchange resources can overcome this in windows 10? I saw a similar conversation about this earlier this week:

> [@Num-Keypad In Perspective](https://forum.inductiveautomation.com/t/num-keypad-in-perspective/76435):
>
> Is there an easy/best solution for a keypad in Perspective for a touchscreen?

---

_[View the full topic](https://forum.inductiveautomation.com/t/bug-browser-virtual-keyboard-extensions-dont-write-into-input-field-text-prop/76689)._