[Dynapi-Help] Opera may change its handling of old (and current?) DynAPI versions

[Hallvord R. M. S. <hal...@on...>]

Dear DynAPI developers and users,
I work for Opera Software with JavaScript testing and development. 
Currently one of the things I'm working on is a set of features that 
lets Opera adapt to broken JavaScripts. This builds on our "user 
javascript" feature which already is being used to fix broken sites.

As you may or may not be aware, older versions of DynAPI do not run 
well in Opera because they detect Opera as "Opera" and important 
parts of the script branches for NN and IE only. This means important 
objects and variables have not been defined and the script fails to 
run correctly.

As a fix for this, I've written a script which will detect when a 
page is about to use an external script with an address ending in 
"dynapi/api/browser.js". If this is the case, Opera will set its 
"navigator.appName" property to "Microsoft Internet Explorer" while 
executing that script.

This obviously has implications for any version of DynAPI that uses 
the same file name/directory structure. You may not be able to detect 
Opera reliably. If you believe this will cause problems for current 
or future versions please voice your concerns..
-- 
Hallvord Reiar Michaelsen Steen
http://www.hallvord.com/

-- 
Hallvord Reiar Michaelsen Steen
http://www.hallvord.com/