Closed Bug 87323 Opened 23 years ago Closed 23 years ago

table position incorrect

Categories

(Core :: Layout, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: jiang_wq, Assigned: asa)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.1+)
Gecko/20010622
BuildID:    20010622

The table for products is shown in a place that is far
right to where it is supposed to be.


Reproducible: Always
Steps to Reproduce:
1.go to http://www.futureshop.ca (then click "English" to choose language)
2.click on the "computers" tab
3.in the left column click "CD-RW drives"
4.in the left column click "more CD-RW drives"

Actual Results:  the list of CD-RW drives is moved from its rightful place into far
right.

Expected Results:  The list should nest within the page.  Use an IE or other browser
to make a comparison.
Confirming. I see it too with today build 2001062204 on WindowsME. It is not a
dup of the recently fixed bug 86075 (BTW by the same reporter - good job Wenquing!).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Component --> Layout (best guess)
Component: Browser-General → Layout
This is most likely invalid.  Take a look at this page through the w3c html
validator:  http://validator.w3.org/

It is a mess.  Of course, you can ignore the statements like "missing alt
attribute on img" or "unrecognized entity", but there are also lots of </tr> and
</td> tags that were never opened.  IE tries to correct for this mistake.  I
don't think Mozilla should have to.

This one should be marked invalid or go to Evangelism

Jake
The HTML is a MESS.. however Nav4 renders it as intended and even Mozilla
Composer renders it properly.  This shows a great benefit of Composer-- fixing
HTML.  If you save the file and load it in Mozilla, it actually renders as
intended.  So there is something different in the way that Composer and
Navigator handle tables.
No longer reproducible (page has changed?)  Marking INVALID.  Please REOPEN if
you can still see this bug.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.