CSS / Table breaks in one browser but works everywhere else

[digleif]

I'm struggling to fix an annoying CSS problem. I've built a nav bar in
a table and use css to control the hover state, which colours the
background of the table cell.

In every browser I've tested it works fine, but in Safari (1.3.2) the
table breaks between cells causing extra space to appear. The nature of
this project is such that it HAS to work in Safari.

You can see the page (no graphics, embedded styles) at:
http://staging.digitaloilfield.com/cssproblem.html

Can someone help me figure out what is happening? I'm going nuts and my
boss is getting impatient...

Leif

[Ben C]

On 2006-10-18, di*****@yahoo.com <di*****@yahoo.comwrote:

I'm struggling to fix an annoying CSS problem. I've built a nav bar in
a table and use css to control the hover state, which colours the
background of the table cell.

In every browser I've tested it works fine, but in Safari (1.3.2) the
table breaks between cells causing extra space to appear. The nature of
this project is such that it HAS to work in Safari.

You can see the page (no graphics, embedded styles) at:
http://staging.digitaloilfield.com/cssproblem.html

Can someone help me figure out what is happening? I'm going nuts and my
boss is getting impatient...

I tried it in Konqueror 3.4.2, which is based on mostly the same code as
Safari, and it worked OK.

I don't have Safari itself. So I can't reproduce your problem, it looks
OK to me.

The only thing I can suggest trying is take away the "width=100%" on the
<tdelements, but leave the width=100% on the table itself. The cells
should fill the complete width anyway. Perhaps those 100%s are causing
Safari some confusion.

[dorayme]

In article <sl*********************@bowser.marioworld>,
Ben C <sp******@spam.eggswrote:

On 2006-10-18, di*****@yahoo.com <di*****@yahoo.comwrote:

I'm struggling to fix an annoying CSS problem. I've built a nav bar in
a table and use css to control the hover state, which colours the
background of the table cell.

In every browser I've tested it works fine, but in Safari (1.3.2) the
table breaks between cells causing extra space to appear. The nature of
this project is such that it HAS to work in Safari.

You can see the page (no graphics, embedded styles) at:
http://staging.digitaloilfield.com/cssproblem.html

Can someone help me figure out what is happening? I'm going nuts and my
boss is getting impatient...

I tried it in Konqueror 3.4.2, which is based on mostly the same code as
Safari, and it worked OK.

I don't have Safari itself. So I can't reproduce your problem, it looks
OK to me.

The only thing I can suggest trying is take away the "width=100%" on the
<tdelements, but leave the width=100% on the table itself. The cells
should fill the complete width anyway. Perhaps those 100%s are causing
Safari some confusion.

First thing to do is fix all the errors. Safari is beaut this
way, it has poor error correction. CSS is strewn with failures to
assign to assign units to numbers. The css is above and below the
head. Look if you don't believe it. The doctype is below the
<htmland so on...

--
dorayme

[Ben C]

On 2006-10-19, dorayme <do************@optusnet.com.auwrote:

In article <sl*********************@bowser.marioworld>,
Ben C <sp******@spam.eggswrote:

>On 2006-10-18, di*****@yahoo.com <di*****@yahoo.comwrote:

I'm struggling to fix an annoying CSS problem. I've built a nav bar in
a table and use css to control the hover state, which colours the
background of the table cell.

In every browser I've tested it works fine, but in Safari (1.3.2) the
table breaks between cells causing extra space to appear. The nature of
this project is such that it HAS to work in Safari.

You can see the page (no graphics, embedded styles) at:
http://staging.digitaloilfield.com/cssproblem.html

Can someone help me figure out what is happening? I'm going nuts and my
boss is getting impatient...

I tried it in Konqueror 3.4.2, which is based on mostly the same code as
Safari, and it worked OK.

I don't have Safari itself. So I can't reproduce your problem, it looks
OK to me.

The only thing I can suggest trying is take away the "width=100%" on the
<tdelements, but leave the width=100% on the table itself. The cells
should fill the complete width anyway. Perhaps those 100%s are causing
Safari some confusion.

First thing to do is fix all the errors. Safari is beaut this
way, it has poor error correction. CSS is strewn with failures to
assign to assign units to numbers. The css is above and below the
head. Look if you don't believe it. The doctype is below the
<htmland so on...

When I said it "looks OK", I meant the output not the source.

The source does look OK, but as you say there are units missing and the
doctype is in the wrong place.

You're right, the OP should fix those errors first, there is a chance
that has something to do with it.

[dorayme]

In article <sl*********************@bowser.marioworld>,
Ben C <sp******@spam.eggswrote:

On 2006-10-19, dorayme <do************@optusnet.com.auwrote:

In article <sl*********************@bowser.marioworld>,
Ben C <sp******@spam.eggswrote:

The only thing I can suggest trying is take away the "width=100%" on the
<tdelements, but leave the width=100% on the table itself. The cells
should fill the complete width anyway. Perhaps those 100%s are causing
Safari some confusion.

First thing to do is fix all the errors. Safari is beaut this
way, it has poor error correction. CSS is strewn with failures to
assign to assign units to numbers. The css is above and below the
head. Look if you don't believe it. The doctype is below the
<htmland so on...

When I said it "looks OK", I meant the output not the source.

The source does look OK, but as you say there are units missing and the
doctype is in the wrong place.

You're right, the OP should fix those errors first, there is a chance
that has something to do with it.

I was not in any way criticising you, Ben. Just really saying
something to OP...

--
dorayme

[Stephen Poley]

On Thu, 19 Oct 2006 18:29:44 +1000, dorayme
<do************@optusnet.com.auwrote:

>Safari is beaut this
way, it has poor error correction. CSS is strewn with failures to
assign to assign units to numbers.

Assuming those two sentences are intended to be related: CSS is quite
explicit that user agents MUST ignore (for example) declarations with
illegal values. "Poor error correction" for CSS does not exist AFAIK
anywhere other than Internet Explorer.

--
Stephen Poley

http://www.xs4all.nl/~sbpoley/webmatters/

[dorayme]

In article <oq********************************@4ax.com>,
Stephen Poley <sb******************@xs4all.nlwrote:

On Thu, 19 Oct 2006 18:29:44 +1000, dorayme
<do************@optusnet.com.auwrote:

Safari is beaut this
way, it has poor error correction. CSS is strewn with failures to
assign to assign units to numbers.

Assuming those two sentences are intended to be related: CSS is quite
explicit that user agents MUST ignore (for example) declarations with
illegal values. "Poor error correction" for CSS does not exist AFAIK
anywhere other than Internet Explorer.

Not quite _intended_ to be related ... sloppy of me! And good
point you make.

I was thinking the other bits were important cause, when i listed
also:

The css is above and below the
head. Look if you don't believe it. The doctype is below the
<htmland so on...

and was just meaning: "fix up all the errors and then see..."

--
dorayme