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

[Leif W <war...@us...>]

> From: "Hallvord Reiar Michaelsen Steen" <hal...@on...>
> Sent: 2005 August 15 Monday 13:57

[snip]

> 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..

I believe that is the DynAPI 2 or older way.  Currently we're not doing 
anything with DynAPI 2.  Ideally I'd like to update the older APIs, but 
right now I'm spending my time trying to fix bugs for a DynAPI 3 
release.  I'm not opposed to updating DynAPI 1 or 2, if someone came 
forward with something and said, "Here, I did it, I tested it, here's a 
bunch of test cases for previous and updated version, try it yourself." 
Then I'd have little extra to do but test, merge and commit.  Until 
then, I guess I can't be opposed to hacks that may work-around any 
broken problems.  But, it'd be nice if the user can turn the feature on 
or off globally, as well as per-site, incase we do get something fixed 
up.  But that's a long ways off, if ever.  Currently DynAPI 3 has moved 
the browser detect stuff into "dynapi/src/dynapi.js", though some may 
choose to install just /src/ on the site under a different dirname like 
/scripts/dynapi/dynapi.js or something.  So I don't think it would 
affect current or future versions.  But well, if anyone else sees a 
problem, be sure to speak up!

Leif