Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-4.1.0.GA
-
Component/s: ACE-Components
-
Labels:None
-
Environment:All
-
Assignee Priority:P1
-
Support Case References:Support Case #13899 - https://icesoft.my.salesforce.com/5007000001eqonB
Description
When two ace:dataTable components are rendered on the same page and both use a paginator, the top tables paginator doesn't resize itself based off of the available browser area.
The paginator sticks to the size it was orginally rendered as. The second table resizes itself accordingly. If the second table is removed from the page, the top table paginator resizes itself correctly.
The paginator sticks to the size it was orginally rendered as. The second table resizes itself accordingly. If the second table is removed from the page, the top table paginator resizes itself correctly.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
r49365: added checks to only unbind the resize callbacks from the window if they have already been defined, in order to avoid unbinding all resize callbacks of all tables (and other components) on the page
Because the destroy() method is always called before initializing a table, and that destroy() method unbinds all the resize callbacks of the table from the window object, but those callbacks aren't defined yet at that point, then all resize callbacks where being removed from the window object, so only the last table got to keep its resize listeners. This was fixed by first checking that these callbacks are defined, before unbinding them.
Show
Arturo Zambrano
added a comment - r49365: added checks to only unbind the resize callbacks from the window if they have already been defined, in order to avoid unbinding all resize callbacks of all tables (and other components) on the page
Because the destroy() method is always called before initializing a table, and that destroy() method unbinds all the resize callbacks of the table from the window object, but those callbacks aren't defined yet at that point, then all resize callbacks where being removed from the window object, so only the last table got to keep its resize listeners. This was fixed by first checking that these callbacks are defined, before unbinding them.
Note: this only happens on the ICEfaces 4 code base.
Show
Arran Mccullough
added a comment - Note: this only happens on the ICEfaces 4 code base.
Attached test case that shows the issue.
Steps:
- Open welcomeICEfaces.jsf
- Resize the browser, the top table paginator won't resize itself based off of the browser window.
Show
Arran Mccullough
added a comment - Attached test case that shows the issue.
Steps:
Open welcomeICEfaces.jsf
Resize the browser, the top table paginator won't resize itself based off of the browser window.
Verified ICEfaces4 trunk r 49367 with attached test case on IE11, MS Edge38, Chrome53, FF47.
Ran all ace:dataTable QA tests on FF47; verified manually column alignment on dataTable with Paginator tests (IE11, MS Edge38, FF47, Chrome53).