Methinks we missed each others points.  I totally agree with you that we
should not build pages that are based on pre-beta or even beta software
unless you have a specific need (for example, an intranet app that will be
using NS6 and only NS6 when released).

One the other hand, as web developer looking for a critique of my site, I
would like to know where it does/does not work properly regardless of the
version or platform.  I can only test so much at my location and having
others running a wide array of browsers on dissimilar platforms check out my
site is a big plus, even if a few of them are using NS6PR2 or some other
obscure environment.

Now if I could just find a way to test on AOL without having to pay for
access like I can for WebTV! :)

Norman

----- Original Message -----
From: Dennis Lapcewich <dlapcewich(at)intira.com>
To: <hwg-critique(at)hwg.org>
Cc: Juliana Halvorson <juliana(at)graphmaster.com>; 'Norman Bunn'
<norman.bunn(at)craftedsolutions.com>
Sent: Friday, September 29, 2000 11:14 AM
Subject: RE: Critique


> As you wish, Norm.  However, I think you missed my point.
>
> For all intents and purposes NS6 is a beta software.  While the folks on
> this and other HTML lists, as well as the techno types may be using it on
a
> regular basis, the *vast* majority of browser users do not.  They use the
> ready-to-use-just-add-water browsers, as they should.
>
> It's fine to test new pages and web sites with beta browsers but once you
go
> into site deployment and production, one should make sure the pages/site
> work in the production browsers.  Adding any do-dads which only are
> exploited in a beta browsers is dangerous, especially when the final
product
> may have just enough changes from its beta that your pages clunks. :)
>
> That the problem exists in IE5x is one thing (a production browser).  That
> the problem exists in NS6x is quite another (a beta browser).  Better one
> test in IE 4xSP2 and IE5x, as well as NS4x, and *ignore* NS6x entirely.
>
> Dennis
>
>
> > I beg to disagree, Dennis.  If the problem was only in NS6PR2, then she
> > should take the results with a grain of salt.  However, the problem
exists
> > in IE5 (Win98) & IE5.5 (Win NT).  The fact that it crosses vendor
browsers
> > could provide her with additional information to help resolve the issue.
> I,
> > for one, prefer the extra information so I can sort out what's important
> and
> > what's not.  I'm sure others would as well.
> >
> > Norman
> >
> >
> >
> > >
> > > > Just realized that there is a bug with the mouse-over
> > > > effects.  They don't work in IE or NS6.  Seem fine in
> > NS4.6 & NS4.7.
> > > >
> > > > Norman
> > > >
> > >
> > > Gonna be pedantic.
> > >
> > > NS6 is a preview release (Ummm, ah, a.k.a., Preview Release 2 is the
> > current
> > > preview version available).
> > >
> > > Not a good idea to test customer web pages with something
> > that isn't a
> > > formal release yet.  Unless, of course, you have money to
> > burn and time on
> > > your side when the final release is out and your NS6-PR2
> > pages need to be
> > > recoded because they don't work properly.  :)
> > >
> > > Dennis
> >

HTML: hwg-critique mailing list archives, maintained by Webmaster @ IWA