Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.0
-
Fix Version/s: EE-4.0.0.GA, 4.1
-
Component/s: ICECORE-Components
-
Labels:None
-
Environment:jsf 2.2 icecore
-
Assignee Priority:P1
-
Workaround Description:if element is always visible in the app, this will not be a problem (not always feasible).
Description
writer.startElement("script", null);
writer.writeText("ice.onUserInactivity(", null);
writer.writeText(getInterval(), null);
writer.writeText(", function() { document.getElementById('", null);
writer.writeText(containerID, null);
writer.writeText("').style.visibility = 'visible'; }", null);
writer.writeText(", function() { document.getElementById('", null);
writer.writeText(containerID, null);
writer.writeText("').style.visibility = 'hidden'; });", null);
writer.endElement("script");
should be modified so that null check is done before applying style.
In showcase app, if you select icecore:idleMonitor and then go to another example page, this component is still active and trying to change the style. Ideally, this is something visible on template throughout the entire application, but can foresee some instances (currently exhibited in showcase even if this was in the header for example so always visible, would still not be available in mobile showcase...)
So null check should be done.
writer.writeText("ice.onUserInactivity(", null);
writer.writeText(getInterval(), null);
writer.writeText(", function() { document.getElementById('", null);
writer.writeText(containerID, null);
writer.writeText("').style.visibility = 'visible'; }", null);
writer.writeText(", function() { document.getElementById('", null);
writer.writeText(containerID, null);
writer.writeText("').style.visibility = 'hidden'; });", null);
writer.endElement("script");
should be modified so that null check is done before applying style.
In showcase app, if you select icecore:idleMonitor and then go to another example page, this component is still active and trying to change the style. Ideally, this is something visible on template throughout the entire application, but can foresee some instances (currently exhibited in showcase even if this was in the header for example so always visible, would still not be available in mobile showcase...)
So null check should be done.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion