Re: table rendering glitch?
I've attached a testcase showing this behaviour, should I be filing this as a bug or am I overlooking something. If you want this to get any attention, you'd be far better off: a) Making sure it has the correct DOCTYPE b) Making sure it passes the W3C's Validator c) Filing a bug in Bugzilla and attaching the files :-) Gerv
Re: table rendering glitch?
In article [EMAIL PROTECTED], Rob Hoopman [EMAIL PROTECTED] wrote:
I've been looking at this, glancing at it from the corners of my eyes,
put it away for a few days, printed it an put it under my pillow at
night, chanting black/white and other magic at it, stared at it some
more and finally concluded I'm probably too stupid to figure it out.
Maybe one of you could take a stab at this.
In short:
I've got a pretty straightforward page that renders differently in IE5
and Mozilla 0.8.
It has got 4 nested tables with some images, a form and a linked
stylesheet.
The way I see it IE renders it correctly while Mozilla adds some 3
pixels bottom margin to each cell and it is driving me up the walls.
I've attached a testcase showing this behaviour, should I be filing this
as a bug or am I overlooking something.
Have you tried:
td img {vertical-align: bottom}
The default is baseline and would explain the extra pixels you are seeing.
ian.
\ /
(@_@) http://www.eclipse.co.uk/sweetdespise/ (dark literature)
/()\ http://www.eclipse.co.uk/sweetdespise/libertycaptions/ (art)
| |
Re: table rendering glitch?
Ian Davey wrote:
In article [EMAIL PROTECTED], Rob Hoopman [EMAIL PROTECTED] wrote:
snip
Have you tried:
td img {vertical-align: bottom}
I have now and this does remove the extra pixels.
Thanks a bundle.
The default is baseline and would explain the extra pixels you are seeing.
I thought this would not be an issue seeing that the td height attributes exactly
match the height of the images for that row.
Although I know the height attribute is depricated and only a recommendation. I
expected it to be rendered without margins.
Rob
Re: table rendering glitch?
In article [EMAIL PROTECTED], Rob Hoopman [EMAIL PROTECTED] wrote:
The default is baseline and would explain the extra pixels you are seeing.
I thought this would not be an issue seeing that the td height attributes
exactly match the height of the images for that row.
It's an issue because it aligns to the baseline of text, so if you have the
following:
dropped img src=".."
With "img {vertical-align: baseline}" the bottom of the image will align to
the bottom of the d (the default), with "img {vertical-align: bottom}" it
aligns to the bottom of the p.
I imagine the space occurs because the image is an inline element within the
table cell.You could probably also get rid of it by changing the image to
display as a block element.
ian.
\ /
(@_@) http://www.eclipse.co.uk/sweetdespise/ (dark literature)
/()\ http://www.eclipse.co.uk/sweetdespise/libertycaptions/ (art)
| |
Re: table rendering glitch?
Rob Hoopman wrote: snip I've attached a testcase showing this behaviour, should I be filing this as a bug or am I overlooking something. I've been at the screen for too long again, there should be one more "/td/tbody/table" to properly close all tables in that file. This does not change the rendering behaviour though, it's just shoddy html. Rob
