Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.3.0.GA
-
Fix Version/s: EE-3.3.0.GA_P01, 4.0.BETA, 4.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:-
-
Assignee Priority:P1
-
Salesforce Case Reference:
-
Workaround Exists:Yes
-
Workaround Description:Do not use h:panelGrid in this circumstance.
Description
Instructions to reproduce:
1. Click to edit a table row
2. Select a date from calendar
3. Click the commandLink titled 'Click Me'
4. Try selecting another date. The ace:dateTimeEntry will no longer popup
There are no suspicious errors in the server logs and focus is attempting to be applied to the calendar:
[window] persisted focus for element "j_idt9:genAnnounceTable:0:fromDateInput_input". The issue is caused by the following h:panelGrid. The table is located inside index.xhtml. Test case attached.
<h:panelGrid>
<h:panelGroup>
<h:form>
<ui:include src="./index.xhtml" />
</h:form>
</h:panelGroup>
</h:panelGrid>
1. Click to edit a table row
2. Select a date from calendar
3. Click the commandLink titled 'Click Me'
4. Try selecting another date. The ace:dateTimeEntry will no longer popup
There are no suspicious errors in the server logs and focus is attempting to be applied to the calendar:
[window] persisted focus for element "j_idt9:genAnnounceTable:0:fromDateInput_input". The issue is caused by the following h:panelGrid. The table is located inside index.xhtml. Test case attached.
<h:panelGrid>
<h:panelGroup>
<h:form>
<ui:include src="./index.xhtml" />
</h:form>
</h:panelGroup>
</h:panelGrid>
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Assigning to Mark for re-assignment as necessary.
Show
Deryk Sinotte
added a comment - Assigning to Mark for re-assignment as necessary.
From the test case's debugAB, we can see that the issue of TEXT nodes being aggregated to cause a DOM difference was a key issue for the full update. So, I updated to the newest icefaces3 trunk and ICEfaces EE 3.3.0 P01 code, and tested for that with them and they came up clean. So no lingering code issues, and an app work-around for the old code shows this is resolved.