Closed
Bug 150621
Opened 23 years ago
Closed 23 years ago
Large row of empty space in a table.
Categories
(Core :: Layout: Tables, defect, P4)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mattraymond, Assigned: karnaze)
References
()
Details
(Whiteboard: wontfix?)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530
BuildID: 2002053012
Above the last row in the main table, there is a row of extreme height filled
with nothing but empty space. Problem seems to occur on other URLs from this
sight. Might be they are generate from the same template document.
Note: Looking at the code, this may just be an exploitation of a bug in Internet
Explorer. It looks as if one specific image is being resized to be several
hundred pixels high, thereby altering the row and table height. Let me know if
this is correct.
Reproducible: Always
Steps to Reproduce:
1. View URL in Mozilla.
Actual Results: Table height is extremely tall.
Expected Results: Table is only tall enought to show the content properly.
|
||
Updated•23 years ago
|
QA Contact: petersen → amar
|
||
Comment 3•23 years ago
|
||
The page goes astray due to a single <link> element that is contained in the
right hand column of that table. This also depends on most elements in the table
having
'height="100%"', and in a very convoluted rowspan/colspan arrangement (which I
doubt even the author of that page really understands). However, if that single
<link> element is moved out of the table's <td> and into the <head> where it
belongs, the page lays out correctly.
I'd say WONTFIX. Way too fluky to bother with.
Assignee: attinasi → karnaze
Component: Layout → HTMLTables
Whiteboard: wontfix?
|
|
||
Updated•23 years ago
|
Priority: -- → P4
|
|
||
Comment 4•23 years ago
|
||
Isn't it almost a Tech Evangelism bug.. I mean.. this page on gamespy.com is not
compliant with W3C standards with this <link> tag that has lost it <head> path..
|
|
||
Comment 6•23 years ago
|
||
wontfix. Doesn't even show up on the original url anymore.
You need to log in
before you can comment on or make changes to this bug.
Description
•