Forum Moderators: open
There were suggestions that it was "script" or "menu" in the file name (I forget which) that Opera didn't like, or that it was to do with the case of 8.3 file names. Eventually, I did a web search for mm_menu.js to find a web site that used the Netscape JavaScript menus (e.g. www.uwaterloo.ca) also used by Dreamweaver, a commonly used external script. This worked with Opera 6, so I cut a line from the source, modified the src parameter, and pasted it into my web page. Now, I can’t get it to fail, except by changing the src to a file that doesn’t exist. This is what I pasted:
<script language="JavaScript1.2" type="text/javascript" src="menus.js">
</script>
Originally, I had language="JavaScript" instead of "JavaScript1.2", but it still works if I change it back.
A couple comments here. Maybe it will help things to sort out further, and maybe not.
First, the language= attribute is deprecated for the "script" element. The updated version is type="text/javascript"
Second, the only reason I know of to use JavaScript1.2 is if there are features in the script that were not introduced until JavaScript1.2 and you're concerned about very old browsers trying to execute the script. Since version 1.2 of js was released way back in 1997 with Netscape 4.0, you'd basically be concerned about NN3 support.
In general version 6 of Opera had rather weak javascript support, and it was very easy to write a script that would fail. But if Opera was spoofing as Explorer, it would at least get you into the site.
Opera 6 was when they begin to gain some market strength, and to their credit, Opera released version 7 pretty quickly and they've been beefing up js support ever since. Obviously they couldn't grow their browser's market share if it won't support commonly used scripts -- no matter how nifty everything else is about it.
