Tonight after completing the transition from mootools to prototype/script.aculo.us that I discussed yesterday I fired up a copy of Opera. Bad news. The version 1.6.5 version of Scriptaculous with v1.50 RC1 prototype dies a horrible, nasty death in Opera. It seems like virtually every prototype function call generates some sort of fatal error. Specifically, using the PeriodicalExecuter didn’t work.
message: Statement on line 141: Type mismatch (usually a non-object value used where an object is required)
Opera did a lot of complaining about type errors and things like that. Bizarre. It looks like there are a few bugs in the system about Script.aculo.us/Opera compatibility… for now that’s just going to be the way it is. Later we can worry about work-arounds for Opera. For now if it works in Firefox, IE 6/7, and Safari that’s going to be good enough.
January 17, 2007 at 4:46 pm
I just had the exact same issue on a site I built for work. I remembered that the demos on the script.aculo.us site were supposed to work in Opera. I went back to the demos page and they did in fact work without throwing errors. After some work I discovered that the problem was that a new version of prototype.js is boxed with scriptaculous and that version doesn’t play well with Opera but the script.aculo.us site still uses the old version for demos. My solution? Copy the prototype.js file that is used on the demo page. It worked for the problems I was having with effects in Opera, I hope it can work for your problems too.
January 18, 2007 at 5:59 pm
Thanks for this tip — I was having the exact same problems in Opera, and copying the prototype.js used on the Scriptaculous demo site solved the issue.
January 18, 2007 at 8:09 pm
Likewise, here. New version of prototype (or should I say “old version”) and things work like magic.
I wonder what’s wrong with RC2.