Rowspan height distribution questionable

NEW
Unassigned

Status

()

Core
Layout: Tables
P4
normal
16 years ago
9 years ago

People

(Reporter: Andrzej Taramina, Unassigned)

Tracking

({testcase})

Trunk
Future
x86
Windows 2000
testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826

In the page at http://www.chaeron.com/gryffyn/mozilla.html, the menu is rendered
way down near the bottom of the page with Mozilla.  All other browsers seem to
properly calculate the rowspans and row sizes, and show the cell with the menu
at the top of the page (as the align="top" should do).

A correct view (with HTML changed to work around this bug) can be found at
http://www.chaeron.com/gryffyn/software.html

Thanks!


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

16 years ago
Can you attach a minimized testcase? And does the problem occur in a new build?

Comment 2

16 years ago
I see the problem with trunk build: 2002-11-15-12 on WINXP.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P4

Updated

16 years ago
Target Milestone: --- → Future

Comment 3

15 years ago
Created attachment 124783 [details]
Testcase

The align=top that you mentionned (actually, valign=top) only positions data
within a cell, it does not position the cell. Not in Mozilla, nor in IE.

The problem here is that in IE, the bottom left column takes all the extra
room, while in Mozilla, the top left column takes all the extra room.

Comment 4

14 years ago
The rowspan rendering error display correctly in the Macintosh build.

Updated

10 years ago
Keywords: testcase

Updated

9 years ago
Summary: Rowspan not rendered correctly → Rowspan height distribution questionable
Assignee: layout.tables → nobody
QA Contact: amar → layout.tables
You need to log in before you can comment on or make changes to this bug.