RE: [Dynapi-Dev] Error in Netscape 4

[Pascal B. <pa...@dy...>]

NS4.04  was buggy with code as far as I can remember
I'm not talking about what it supports, but how it supports...badly.

again this is what I remember from it

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net

  -----Oorspronkelijk bericht-----
  Van: dyn...@li...
[mailto:dyn...@li...]Namens Bart Bizon
  Verzonden: dinsdag 30 januari 2001 21:41
  Aan: dyn...@li...
  Onderwerp: SV: [Dynapi-Dev] Error in Netscape 4


  Well, from what I know Netscape 4.01 - 4.05 support Javascript 1.2,
  4.05+ support 1.3...
  And Javascript 1.2 has many "features" not found in later versions. Nor
prior.
  For instance, type conversion is turned off, i.e.
  ("345"==345 ) would be false. In Javascript 1.3 and 1.1 this would be
true.
  (to achieve the same effect in Javascript 1.3 you would do
 ("345"===345 ), where === is equality without typeconversion.)
  Also there are some differences where returning values are concerned. And
this is without mentioning all the bugs that exist ;)
    -----Ursprungligt meddelande-----
    Från: Pascal Bestebroer <pa...@dy...>
    Till: dyn...@li...
<dyn...@li...>
    Datum: den 30 januari 2001 19:23
    Ämne: RE: [Dynapi-Dev] Error in Netscape 4


    yep, NS4.04 sucks with code.

    The browser has some serious problems handling alot of basic javascript
things.  I guess I'll have to add a note about non NS4.04  compatiblity to
the f.a.q.

    There will probably be more problems even when adding the return lines
to the functions.
    Pascal Bestebroer
    pa...@dy...
    http://www.dynamic-core.net

      -----Oorspronkelijk bericht-----
      Van: dyn...@li...
[mailto:dyn...@li...]Namens Leon Reinders
      Verzonden: dinsdag 30 januari 2001 19:13
      Aan: dyn...@li...
      Onderwerp: [Dynapi-Dev] Error in Netscape 4


      Recently i've been testing Dynapi on my computer and have noticed that
i get errorrs in netscape 4.04 using  mouseevents. (Even in the latest
versions of Dynapi.)
      I found that placing a default return-false in a subroutine would
easily fix this.
      Could anybody comfirm my findings?

      Thanks.