I think that the pov-team has quite little chances of fixing a bug
in Netscape 4. Send the bug report to netscape.com instead.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

Warp wrote:
>   I think that the pov-team has quite little chances of fixing a bug
> in Netscape 4. Send the bug report to netscape.com instead.

I have given up supporting it (all sites I do from now on will be xhtml
based), I will check to ensure everything is fully functional, and perhaps
tweak any style sheets to make the most of a bad situation but no way am I
spending hours hacking a site to bits just to get NS4.x to look perfect


--
Rick

Kitty5 WebDesign - http://Kitty5.com
POV-Ray News & Resources - http://Povray.co.uk
TEL : +44 (01270) 501101 - FAX : +44 (01270) 251105 - ICQ : 15776037

PGP Public Key
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x231E1CEA


---

Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.373 / Virus Database: 208 - Release Date: 01/07/2002

Post a reply to this message

On Wed, 10 Jul 2002 16:51:25 +0100, "Rick [Kitty5]" <ric### [at] kitty5com>
wrote:

>Warp wrote:
>>   I think that the pov-team has quite little chances of fixing a bug
>> in Netscape 4. Send the bug report to netscape.com instead.
>
>I have given up supporting it (all sites I do from now on will be xhtml
>based), I will check to ensure everything is fully functional, and perhaps
>tweak any style sheets to make the most of a bad situation but no way am I
>spending hours hacking a site to bits just to get NS4.x to look perfect

For what it's worth, Netscape 4.7 on the Windows OS renders the page
mentioned in this thread without a problem on my computer. Perhaps it
might even be some glitch in some graphics library or "toolkit"
peculiar to Solaris?

At any rate, I would tend to agree that it is nearly impossible to
make a classy-looking website that will render as planned in EVERY
browser that a person might want to use. At least this person could
view the POV-Ray website. I've seen a few websites that were totally
non-functional with certain mainstream browsers. There's no excuse for
something like that, but the POV site has nothing in common with a
site like that.



Later,
Glen

7no### [at] ezwvcom     (Remove the numeral "7")

Post a reply to this message

> I have given up supporting it ... no way am
> I spending hours hacking a site to bits just
> to get NS4.x to look perfect

Amen to that, brother...

Post a reply to this message

Glen Berry wrote:
> At any rate, I would tend to agree that it is nearly impossible to
> make a classy-looking website that will render as planned in EVERY
> browser that a person might want to use.

if your prepared to throw standards out the window and sometimes do browser
specific style sheets, you can get it looking 99% identical in all the top
browsers (inc NC4.7)

older browser require you to develop specific versions (html 3.2 and below)
--
Rick

Kitty5 WebDesign - http://Kitty5.com
POV-Ray News & Resources - http://Povray.co.uk
TEL : +44 (01270) 501101 - FAX : +44 (01270) 251105 - ICQ : 15776037

PGP Public Key
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x231E1CEA


---

Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.373 / Virus Database: 208 - Release Date: 02/07/2002

Post a reply to this message

> if your prepared to throw standards out the window and sometimes do
browser
> specific style sheets, you can get it looking 99% identical in all the top
> browsers (inc NC4.7)


To look identical, yes, you may have to do that.

But if all you want is for a page to "work" in every browser, standards are
the way to go. Take www.webstandards.org for instance. *Because* it uses
valid markup and CSS, its content is accessable in all browsers. Including
Mozilla, IE, NN4.x, Opera, Lynx, Palm Pilot browsers, screen readers, you
name it. A couple of browsers do have some CSS bugs that cause the menu to
be displayed off the screen (this is caused by the fact that the browser
meets the standard halfway; it would be better to ignore the CSS than to
interpret it incorrectly). But if you're going for 99% of the population to
be able to see your site, standards are what you want to use.

Of course, the page won't look identical in every browser. But what's more
important - the visual apperance of the page or the content on it? The site
will look *decent* in most browsers. In all browsers, the content will be
accessable.

Another benefit is that the site is more accessable to handicapped users,
such as someone using a screen reader or something of the sort.

 - Slime
[ http://www.slimeland.com/ ]

Post a reply to this message

Warp wrote in message <3d2b6d06@news.povray.org>...
>  I think that the pov-team has quite little chances of fixing a bug
>in Netscape 4. Send the bug report to netscape.com instead.

I've duplicated it with Netscape 4.72 under IRIX.  It appears to be caused
by the fact that the "search" button is about twice as tall under the window
managers those OSs use as it is under Windows/MacOS/etc.

--
Mark

The Universe is expanding.
The budget for its exploration is shrinking.

Post a reply to this message

Slime wrote:
[snip...]

exactly why I am sticking to XHTML 1.0 strict from now on (and meeting
triple A accessability standards :)


--
Rick

Kitty5 WebDesign - http://Kitty5.com
POV-Ray News & Resources - http://Povray.co.uk
TEL : +44 (01270) 501101 - FAX : +44 (01270) 251105 - ICQ : 15776037

PGP Public Key
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x231E1CEA


---

Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.373 / Virus Database: 208 - Release Date: 03/07/2002

Post a reply to this message

> exactly why I am sticking to XHTML 1.0 strict from now on (and meeting
> triple A accessability standards :)

Wowee, that's impressive. I use XHTML 1.0 strict, but haven't even read the
specs for AAA standards =)

 - Slime
[ http://www.slimeland.com/ ]

Post a reply to this message

Slime <slm### [at] slimelandcom> wrote:
> But if all you want is for a page to "work" in every browser, standards are
> the way to go. 

  If you use all the standards defined by the W3C, using the full capabitilites
they offer, you'll probably make a site which won't work in *any* browser
(because no current browser supports everything standardized by W3C).
  So it's not enough to just stick to the standard. You also have to know
which standards are widely implemented and supported, and which aren't.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message