Closed
Bug 301175
Opened 19 years ago
Closed 19 years ago
images not lining uup
Categories
(Core :: Layout: Tables, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: adrian, Unassigned)
References
()
Details
(Keywords: testcase)
Attachments
(1 file)
|
341 bytes,
text/html
|
Details |
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) Build Identifier: 2 images within a table (which form my banner), dont display properly. it's like there is a carriage return between the images, but doesn't happen with IE. Go to any page at www.stillmymind.com. Otherwise, I love FireFox thank you Adrian Newington Reproducible: Always Steps to Reproduce: 1.Go to any page at www.stillmymind.com. 2. 3. Expected Results: 2 images should form 1 horizontal strip.
Comment 2•19 years ago
|
||
Adrian, the table width is 685 px, but the the both images + the first td are 686 px, therefore it moves the image down. You can try this out by changing the first image:s width to 362 or remove the from the first td. IE and Opera are expanding the table instead. I don't know what is correct here.
Keywords: testcase
Comment 3•19 years ago
|
||
Updated•19 years ago
|
Component: General → Layout: Tables
Product: Firefox → Core
QA Contact: general → layout.tables
Version: unspecified → Trunk
this is the famous <img><img> nowrap hack (see bug 97619 for the not so glory details), it should work if a) you remove the div and put the align on the td, I don't see the use of it anyway as the table is overconstrained, this requires that you keep a quirks mode doctype as you have now. b) you give the table enough space c) what is the first td exactly doing other than misaligning the banner with respect to ad below on the left, removing it would also help
The original url is now wfm. Seems that the reporter followed one of the many advises and it helped. So lets close this bug as invalid. Otherwise I would be sorry that I can't close the bug as wontfix.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•