Hi,
I'm evaluating this nice menu system in a test site to see if it's suitable before buying any licences. All's going well in Firefox, Opera, and MSIE6 except for this:
In about 1 out of 5 refreshes of the site in MSIE6 a javascript error occurs that I can't debug because it's in an anonymous function (or so the debugger says). I've minimized the javascript being used and left the menus out and found that it occurs only when this line is included:
<script type="text/javascript" src="menu/mmenudom.js"></script>
... and when nested deep inside the page this line is included:
<script type="text/javascript"><!-- // if I remove this script block then no errors occur //--></script>
It is so weird because without that empty script block the error never occurs. This smells like it's got something to do with a timer and with walking the DOM tree. I suspect therefore that it's caused by code that injects the MILONIC text into the menu.
Try it for yourself to find out... just remove that script block and no more errors occur.
This site is here (but will change soon as it's in development):
http://bioreform.ath.cx/
It's validated xhtml 1.1.
No script errors ever occur in Firefox and Opera.
Please help...
Random bug with MSIE6 & mmenudom.js & nested <scr
Causes and solution found
Hi,
I found a solution to the bug.
It occurs when you use MSIE6, mmenudom.js, and a <script>..</script> block anywhere below a table row element that has a calculated height using the MSIE specific css command 'height: expression(...)'. My expression contains references to different elements in the page using getElementById(...). Somehow without the combination of all 3 of the bug's requirements mentioned above, the expression is evaluated after the elements have been created by the browser. If all 3 of the bug's requirements are met, then in about 1 in 5 browser refreshes, the css height expression is evaluated before the elements it references have been created.
The solution is to use javascript to set the expression at the bottom of the body or in a onload handler.
Really weird!
I found a solution to the bug.
It occurs when you use MSIE6, mmenudom.js, and a <script>..</script> block anywhere below a table row element that has a calculated height using the MSIE specific css command 'height: expression(...)'. My expression contains references to different elements in the page using getElementById(...). Somehow without the combination of all 3 of the bug's requirements mentioned above, the expression is evaluated after the elements have been created by the browser. If all 3 of the bug's requirements are met, then in about 1 in 5 browser refreshes, the css height expression is evaluated before the elements it references have been created.
The solution is to use javascript to set the expression at the bottom of the body or in a onload handler.
Really weird!
Hi,-
I don´t understand, maybe you´ll provide an explanation, but which application requires the use of the Milonic files without a menu_data.js and instead of that an empty, as you say "<script>..</script> block anywhere below a table row element that has a calculated height using the MSIE specific css command 'height: expression(...)'. ".... ??
Michael
I don´t understand, maybe you´ll provide an explanation, but which application requires the use of the Milonic files without a menu_data.js and instead of that an empty, as you say "<script>..</script> block anywhere below a table row element that has a calculated height using the MSIE specific css command 'height: expression(...)'. ".... ??
what but ? Bug of IE6 ? A Milonic menu-systems bug ?I found a solution to the bug.
Michael
