Rants are excused as per section 309.575.696.8 of the 'unwritten' guide to
conversing with programmers which states "rant all you want, just don't
forget what the code is for".  Not to mention that I always wear protective
gear when coding as to prevent injuries.

I can only test those components which can be used on a Win98 machine using
IE5.5, NS 6.01, NS 4.76.

My original recommendation was to modify the browser.js file to allow for
proper detection of at least IE and NS on either Win32 or Mac platforms so
that we can ensure that the DynAPI does not report false bugs due to an error
in browser detection.

Known Bug for detecting Opera in current browser.js - Opera allows for
spoofing.  By default it will spoof as MSIE 5.  This results in is.opera and
is.ie5 being set to true when in fact its not IE5.  If we plan to support
Opera whenever they finally get around to providing accurate DOM support then
we should start with accurate detection.  Modifying the browser.js might get
us a few steps closer to Goal # 1.

Goal #3 - As I understand it, most future browsers will be using the Gecko
Engine to implement DOM support.  By modifying browser.js to detect the Gecko
Engine, we can more accurately support it based on the Gecko Engine and
possibly eliminate the need to do a complete browser check.

Just my thoughts based on tidbits of information that I have picked up here
and there.

Doug Melvin Wrote  :  
>Current goals as I understand them:
>
>1) Fix all know bugs in IE 4.x &5.x and NS 4.x on PC and MAC (linux?)
>2) Ensure that all code works (consistantly) with IE 4.x &5.x and NS 4.x =
>on PC and MAC (linux?)
>3) Implement WC3 DOM support using NS6 as a test basis
>
>4) and THEN we tackle improving size and speed
>5) release "official" DynAPI 2.0 FINAL version.
>6) figure out what we do for our next trick.
>
>Doug Melvin
>
>Please excuse my previous rants if they hurt yer head alittle, I'm a =
>very big bitch without my coffe

Reply via email to