Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.8.1
-
Fix Version/s: 1.8.2-EE-Beta, 1.8.2-EE-GA, 1.8.3
-
Component/s: ICE-Components
-
Labels:None
-
Environment:Liferay 5.2.3 + Tomcat 6 + IE7
Description
When using an ice:panelDivider in Liferay Portal, viewed in IE7 it causes a JS error to be reported by IE when it loads. The basic functionality continues to work but it looks like the error is related to sizing the panel divider properly.
Even though changing the split direction works you can see that the split region for the horizontal direction doesn't stretch for the entire
width of the pane. The JS error occurs in Ice.PanelDivider.adjustSecondPaneSize which confirms that the error is
really related to Panel Divider JS code.
Even though changing the split direction works you can see that the split region for the horizontal direction doesn't stretch for the entire
width of the pane. The JS error occurs in Ice.PanelDivider.adjustSecondPaneSize which confirms that the error is
really related to Panel Divider JS code.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Seems it's not working well in FF either, although there are no errors in FF. See screenshot-3.
After setting com.icesoft.faces.compressResources=false in web.xml, basic functionally is working, but the Microsoft Script Debugger still comes up blank.
Seems in this particular scenario the the event for adjusting the dimensions of the divided panels occurred too soon. Somehow IE returns zero for some measurements even though the elements should have been parsed already.
Changed to delay event handling until window onload event happens.
Fixed. See screen shots 4 and 5.
Show
yip.ng
added a comment - - edited Seems in this particular scenario the the event for adjusting the dimensions of the divided panels occurred too soon. Somehow IE returns zero for some measurements even though the elements should have been parsed already.
Changed to delay event handling until window onload event happens.
Fixed. See screen shots 4 and 5.
Couldn't even see the basic functionality working. After clicking through a number of meaningless errors, I got the screen as in screenshot-1. If I tried to debug the errors, the Microsoft Script Debugger would come up as totally empty as in screenshot-2.