Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
InputText is written wrongly
See original GitHub issueAs stated in the screenshot below, instead of writing luigiverdi@toduba.it, the driver does not write the @ symbol but adds the quotes instead
Issue Analytics
- State:
- Created a year ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
How do I display an error message if the input is wrong on HTML
Im trying to display an error message in RED beside the input field to let the user know, however I dont know why...
Read more ><input type="text"> - HTML: HyperText Markup Language | MDN
<input> elements of type text create basic single-line text fields. ... is of the wrong type, and so forth) is entered into your...
Read more >Input validation showing 'wrong' for text-box without requir
When I click on an input box that does not have validation, then click out of it without editing it, the validation error...
Read more >Pen input is detected wrongly. - Microsoft Community
The pen doesn't detect exactly were it's touching. So at times, while I want to write in one area, it is written in...
Read more >Wrong input information is written in the contactlist
After I delete the contacts completely to use the same email addresses again for further testing, the contact list will always show the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@MenilV thanks for reporting and the test cases. The issue is different from what @smsimone mentioned, but is nonetheless valid. I have addressed it in #122 (going to be released today/tomorrow).
@smsimone I have confirmed that the issue you are facing is related to the system input method (aka keyboard language). The simplest way to fix it is to switch to a US English keyboard layout. In the meantime, I am looking for a smarter way to resolve it.
Android part of the bug was addressed in #122 and is now available in Maestro 1.4.1