setComponentError in TextField switches to current value
Open
Nobody has claimed this yet.
bug
Stale
v7
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
Originally by JohannesL
When I use the method setComponentError in a TextField component, in Internet Explorer 11 the input is changed to the current value. This value isn't the current input, so generally the input ist thrown away. There is no problem in Firefox or Chrome.
Imported from https://dev.vaadin.com/ issue #19461
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in Internet Explorer 11 around TextField.setComponentError and compare the behavior with Firefox or Chrome. Trace the setComponentError path to determine why the input is replaced by the current value; done means preserving the user's current input in IE11 without regressing the other browsers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100