Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.0.0.GA
-
Fix Version/s: EE-3.0.0.GA
-
Component/s: Accessible Components
-
Labels:None
-
Environment:*
Description
Split from IPCK-352.
Navigating the paginator to another page results in the table being blanked out. Both the paginator submit and the subsequent table render are done OK and the table update is in the response body. See screenshot-1.png. However, when it comes time to update on the client side, the original table is gone and the framework reports a malformed XML error. See screenshot-2.png. Between the submit and the response the table has somehow disappeared on the client side.
Navigating the paginator to another page results in the table being blanked out. Both the paginator submit and the subsequent table render are done OK and the table update is in the response body. See screenshot-1.png. However, when it comes time to update on the client side, the original table is gone and the framework reports a malformed XML error. See screenshot-2.png. Between the submit and the response the table has somehow disappeared on the client side.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
In the TableRenderer append row index to the clientID of the row component to make sure that the assiged element IDs are unique.
Show
Mircea Toma
added a comment - In the TableRenderer append row index to the clientID of the row component to make sure that the assiged element IDs are unique.
All the rendered 'TR' elements corresponding to the data table rows have the same 'ID' attribute. This causes the failure in the JSF bridge because the browser gets confused which element is supposed to pick (before update is applied).