Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Won't Fix
-
Affects Version/s: EE-3.3.0.GA_P03, EE-4.1.0.GA
-
Fix Version/s: 4.2, EE-3.3.0.GA_P05
-
Component/s: ACE-Components
-
Labels:None
-
Environment:All
-
Assignee Priority:P1
-
Support Case References:Support Case #13820 - https://icesoft.my.salesforce.com/5007000001caCLi
-
Workaround Exists:Yes
-
Workaround Description:HideThe first scenario is easily fixed by wrapping the text in an h:panelGroup and setting the value of the 'for' attribute in ace:tooltip to the ID of this h:panelGroup, so that the text inside will be updated/replaced, but the tooltip listener will remain on the wrapper throughout updates.
As for the second scenario, what works best is using the delegate mode of the ace:tooltip. The delegate demo in the showcase is a very clear example of how to use the tooltip in this mode to maintain the tooltip triggers throughout dynamic updates, while still being able to access row-specific data.ShowThe first scenario is easily fixed by wrapping the text in an h:panelGroup and setting the value of the 'for' attribute in ace:tooltip to the ID of this h:panelGroup, so that the text inside will be updated/replaced, but the tooltip listener will remain on the wrapper throughout updates. As for the second scenario, what works best is using the delegate mode of the ace:tooltip. The delegate demo in the showcase is a very clear example of how to use the tooltip in this mode to maintain the tooltip triggers throughout dynamic updates, while still being able to access row-specific data.
Description
-
Hide
- Case13820Example.zip
- 20 kB
- Arran Mccullough
-
- Case13820Example/build.xml 3 kB
- Case13820Example/.../ant-deploy.xml 2 kB
- Case13820Example/.../build-impl.xml 80 kB
- Case13820Example/.../genfiles.properties 0.5 kB
- Case13820Example/.../private.properties 0.6 kB
- Case13820Example/.../project.properties 4 kB
- Case13820Example/nbproject/project.xml 0.9 kB
- Case13820Example/src/conf/MANIFEST.MF 0.0 kB
- Case13820Example/src/.../support/Item.java 0.6 kB
- Case13820Example/src/.../TestBean.java 1 kB
- Case13820Example/web/index.xhtml 0.5 kB
- Case13820Example/web/.../context.xml 0.1 kB
- Case13820Example/web/WEB-INF/web.xml 2 kB
- Case13820Example/.../welcomeICEfaces.xhtml 3 kB
-
Hide
- Case13820Example.war
- 9.88 MB
- Arran Mccullough
-
- META-INF/MANIFEST.MF 0.1 kB
- META-INF/context.xml 0.1 kB
- WEB-INF/classes/com/.../support/Item.class 0.8 kB
- WEB-INF/classes/.../support/TestBean.class 2 kB
- WEB-INF/lib/icefaces-ee-ace.jar 6.15 MB
- WEB-INF/lib/icefaces-ee-ext.jar 51 kB
- WEB-INF/lib/icefaces-ee.jar 690 kB
- WEB-INF/lib/javax.faces-2.2.13.jar 2.99 MB
- WEB-INF/web.xml 2 kB
- index.xhtml 0.5 kB
- welcomeICEfaces.xhtml 3 kB
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Setting alwaysExecuteContents="true" on the dataTable doesn't change the reported behavior.
Sounds like the tooltip's association with the datatable cell isn't surviving the cell update.
This is the expected behaviour, and it's not exclusive to the ace:dataTable. Any element, acting as a trigger for a tooltip, that is dynamically updated (i.e. the original node is replaced) won't have the tooltip listener applied to the new node, unless the tooltip component is updated as well.
The first scenario is easily fixed by wrapping the text in an h:panelGroup and setting the value of the 'for' attribute in ace:tooltip to the ID of this h:panelGroup, so that the text inside will be updated/replaced, but the tooltip listener will remain on the wrapper throughout updates.
As for the second scenario, because of the nature of the cell editor component, the cells will be dynamically updated with the input and output facets, when entering/exiting the edit mode, respectively. It is not possible to simply add a wrapper to the cell editor component, as it has to be a first-level child of the column. For this scenario, what works best is using the delegate mode of the ace:tooltip. The delegate demo in the showcase is a very clear example of how to use the tooltip in this mode to maintain the tooltip triggers throughout dynamic updates, while still being able to access row-specific data.
Attached test case that shows a few scenarios of this issue.
Scenario #1 Steps:
Scenario #2 Steps: