Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.1, EE-3.0.0.GA_P01
-
Fix Version/s: EE-3.0.0.GA_P01, 3.2
-
Component/s: ACE-Components
-
Labels:None
-
Environment:icefaces-3.0.x-maintenance revision# 30501
Last passing revision# 30469
Browser: IE, Chrome, Firefox
Description
Clearing the dateTimeEntry input of a popup calendar and submitting the field causes the input to automatically repopulate it's value with the value that was present before clearing the field.
Tests are located at: http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/dateTimeEntry
To reproduce:
1. Build / deploy test app
2. Navigate to '/calendarAttribute.jsf'
3. Clear the dateTimeEntry input field and push enter
Notice the value of the dateTimeEntry returns
Tests are located at: http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/dateTimeEntry
To reproduce:
1. Build / deploy test app
2. Navigate to '/calendarAttribute.jsf'
3. Clear the dateTimeEntry input field and push enter
Notice the value of the dateTimeEntry returns
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
I can see a difference in behaviour between IE+Chrome+Safari versus Firefox. In Firefox the cleared value is put back after enter key is pressed while in the other browsers the input remains empty.
On the other hand I don't see any difference in behaviour between revision 30469 and current trunk, when using the same browser.
Show
Mircea Toma
added a comment - I can see a difference in behaviour between IE+Chrome+Safari versus Firefox. In Firefox the cleared value is put back after enter key is pressed while in the other browsers the input remains empty.
On the other hand I don't see any difference in behaviour between revision 30469 and current trunk, when using the same browser.
Attached fixed calendarAttribute.xhtml file.
The fixes for this test are to include the "output" outputText component in the form with the ace:dateTimeEntry, and to limit the execution of the ace:dateTimeEntry on top to itself, to avoid constantly failing due to the empty "required=true" ace:dateTimeEntry at the bottom.
Might want to consider removing the bottom ace:dateTimeEntry altogether, or moving into a page of it's own.