On Apr 24, 5:56 pm, maya <maya778...@yah oo.comwrote:
hi,
http://www.mayacove.com/design/nav/nav.html
this dynamic menu is working fine in FF and IE7, but in IE6 can only
test in that "stand-alone" IE6
(http://browsers.evolt.org/?ie/32bit/standalone,
IE has very different structure from other browsers on the market. Its
JScript engine and XML parsers are not part of the browser itself but
shared resources from %windows% subfolders. Don't forget that JScript
in Windows is the same as AppleScript in MacOS, it is used to run
system scripts (WSH) as well. This way JScript is a separate
jscript.dll library in %windows%\syste m32 folder. It is used by IE
among other applications - but it has no specific relations with IE.
Each newer IE installation overrides it - but say Windows Script Host
installation may override it as well. It is overall fixed now in
Windows XP, but earlier I had to help people with highly bizarre
situations like newest IE6 failing to do some task because the JScript
engine was 5.0, occasionally overwritten during WSH installation after
IE installation.
Back to the topic: while it is possible - with some tricks - to have
both IE6 and IE7 on the same system, Windows doesn't provide a
mechanic of having two equally named DLL in the same location
conditionally chosen by this or that application. Actually I doubt
that any OS at all has such option but here I may be mistaken. That
means that with both IE6 and IE7 installed you either will have
JScript 5.6.x for both, or JScript 5.6.y for both - with all funny
result you may expect out of that. Many developers still do install
both IE and do testing without knowing the catch: because unlike say
5.0 and 5.6 the difference is very small here: JScript 5.6 for IE7 is
lesser-minor update of 5.6 for IE6 with the only really noticeable
difference of XHR made as a separate host object and not an ActiveX.