Details
Bug
Major
Description
The same could be reproduced with the sample app given at http://wiki.icesoft.org/display/ICE/Using+Single+Submit
Following are the steps to reproduce the issue:
1.Suppose that you have multiple fields in form and you enter something in say, 'Age' textfield.
2. Select another field by (mouse click or tab or whatever)
3. Select the 'Age' textfield again and remove by contents in it by a ctrl A + backspace.
4. Select any other field in the form.
5. Now, select any other field in the form (may include the 'Age' textfield, but cannot include the one selected at step 4)
At this point the original contents typed in at step 1 will be reappeared in the 'Age' textField.
Following are the steps to reproduce the issue:
1.Suppose that you have multiple fields in form and you enter something in say, 'Age' textfield.
2. Select another field by (mouse click or tab or whatever)
3. Select the 'Age' textfield again and remove by contents in it by a ctrl A + backspace.
4. Select any other field in the form.
5. Now, select any other field in the form (may include the 'Age' textfield, but cannot include the one selected at step 4)
At this point the original contents typed in at step 1 will be reappeared in the 'Age' textField.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Feel free to assign this back to me if there's no emergency, but I will not be able to look at it until September.
Show
Ted Goddard
added a comment - Feel free to assign this back to me if there's no emergency, but I will not be able to look at it until September.
The attached sample page textEntry.xhtml does use h:inpuText, not ace:inputText, so additional testing from the forum users is required.
Show
Ted Goddard
added a comment - The attached sample page textEntry.xhtml does use h:inpuText, not ace:inputText, so additional testing from the forum users is required.
Use the attached textEntry.xhtml to replace samples/showcase/showcase/src/main/webapp/resources/examples/ace/textEntry/textEntry.xhtml
The described steps were followed, but the problem was not reproduced. Could this be browser-dependent, or caused by browser autofill?