Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.0.BETA
-
Fix Version/s: 4.0
-
Component/s: ACE-Components, Bridge
-
Labels:None
-
Environment:ICEfaces4 trunk# 40367
Server: Tomcat7
Browser: IE8
-
Assignee Priority:P1
Description
In IE8, the bridge cannot find a node (a panel expansion row, containing 'exp' in the client id), when contracting an expanded row of an ace:dataTable with scrollable=true. This results in placing the cells in a wrong order/position.
See http://jira.icesoft.org/browse/ICE-9829?focusedCommentId=52108&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-52108
This issue can be reproduced with showcase > ace:dataTable > Grouping demo in IE8:
A browser console error is seen, and the row cells become mis-arranged, when trying to repeatedly expand and contract a row:
[window] Error [status: malformedXML code: 200]: During update: form:carTable_exp_6 not found
..................
See http://jira.icesoft.org/browse/ICE-9829?focusedCommentId=52108&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-52108
This issue can be reproduced with showcase > ace:dataTable > Grouping demo in IE8:
A browser console error is seen, and the row cells become mis-arranged, when trying to repeatedly expand and contract a row:
[window] Error [status: malformedXML code: 200]: During update: form:carTable_exp_6 not found
..................
Modified ice.ace.DataTable.prototype.toggleExpansion to avoid removing TR element in 'fadeOut' callback to let the partial update modify the element (and not throw errors). The element has its display property set to 'none' instead.