Background image in cell with rowspan getting cut off in Netscape 6

[superslurpee]

Hi!

I've got a Netscape 6 problem with a background image in a table cell that has a rowspan. Although NN6 will display the background image, it cuts it off as soon as the second row starts (again, it's in a cell that has a rowspan="3" although any rowspan seems to cause the cut off).

Anyways, the background image displays properly (the entire thing covering the entire rowspaned cell) in all other browsers (NN7, IE, etc.) In NN6 I get part of the background image but as soon as row 2 starts there is no more image but just white.

If anyone has any thoughts on this I'd appreciate it. I use strictly CSS and XHTML (i.e. no bgcolor or stuff like that!) There's nothing technically wrong with the code itself, it just seems to be a NN6 bug. Any work arounds?!

Thanks!

 

[NigeW]

Hey superslurpee

Any chance of supplying the code - it might help !

Cheers

Nigel Wilson
"kiwi-kid"

http://www.potentialunlimited.co.nz

 

[superslurpee]

Hi,

The code is quite simple:

<table border=&quot;1&quot;>
<tr><td rowspan=&quot;3&quot; width=&quot;100&quot; height=&quot;150&quot; style=&quot;background-image:url('images/logo.gif'); background-repeat:no-repeat;&quot;>Cell rowspanned with background image</td><td>Row 1</td></tr>
<tr><td>Row 2</td></tr>
<tr><td>Row 3</td></tr>
</table>

It must be a bug in NN6 but I can't find any documentiona on it. Just replace the 'logo.gif' with any image and you'll see what I mean in NN6. Every browser properly puts the background image covering the entire rowspanned cell (spanning all 3 rows) but NN6 just cuts it off as soon as row 2 starts! So you get part of the image (that where row 1 is), and then just white (where row 2 and 3 are).

Putting another table inside the cell doesn't work and neither does 'repeat-y'. Very weird! If anyone has any thoughts, reply!

Thanks in advance!

 

[BillyRayPreachersSon]

I think this could be one of NN6's infamous display bugs. NN6 was very buggy - especially early releases of it.

Sorry I can't give you any better news!

You might be able to get around it by re-jigging your table to obsolete the need to use ROWSPAN.

Dan