Browser fails to display page -- significantly different

RESOLVED WORKSFORME

Status

SeaMonkey
General
RESOLVED WORKSFORME
15 years ago
14 years ago

People

(Reporter: Robert La Ferla, Unassigned)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030912
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030912

http://www.sherwin-williams.com/productsservices/default.asp

Reproducible: Always

Steps to Reproduce:
1.  Open http://www.sherwin-williams.com/productsservices/default.asp
2.
3.
(Reporter)

Comment 1

15 years ago
I forgot to mention that it renders perfectly with Internet Exploiter (Explorer)...
Um... The rendering is correct.  The page has a bunch of divs with a fixed
width, then a bunch of tables (which have to come below the divs).  None of
these items are floated, so the just stack vertically.

What is the bug, exactly?
(Reporter)

Comment 3

15 years ago
Created attachment 131364 [details]
Screenshot
(Reporter)

Comment 4

15 years ago
Ummmm.  Did you compare it against IE?  Did you use today's build?  Look at the
attached JPG screenshot.
Yes, I compared it to IE.  And what I see in Mozilla is exactly what your
screenshot shows.  And that rendering is correct given the HTML and CSS on the
page.  I have no idea why IE decides to render what it does, but if it's getting
sent the same HTML/CSS as Mozilla, what it renders is just totally incorrect.

Comment 6

15 years ago
Shervin Williams now does server side browser sniffing and gives a diffrent page
to IE6.  The page it gives Moz renders just fine.

Side note mozilla renders IE6's page fine except the menus does not work.
-> Tech Evang ?
no, just worksforme since there is no bug here (page renders fine).
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.