237837 - Incorrect Page Rendering

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[S.Green]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

Text spacing too large -- over prints graphics

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



Expected Results:  
It looks okay in IE.  
This site advertizes that it was "supported" (designed for??) Microsoft.

Comment 1

[Ali Ebrahim]

--> Browser

Comment 2

[Olivier Cahagne]

site looks the same for me using IE6 and FF 20040317 on Win2k, please attach a
screenshot.

Comment 3

[S.Green]

Attachment: 2 pages shown via FF & IE

per your request, here are screen prints of 2 pages shown with FF and IE.  To
me the FF rendering is distorted.  Incidently, I've downloaded and installed
the latest (I hope) build of FF  v0.8+ 20040310

Comment 4

[S.Green]

Attachment: Page1 via FF

1 of 4: Guess you won't accept .zip files so I'll send them up individually

Comment 5

[S.Green]

Attachment: Page 1 via IE

2 of 4: Guess you won't accept .zip files so I'll send them up individually

Comment 6

[S.Green]

Attachment: Page 2 via FF

3 of 4: Guess you won't accept .zip files so I'll send them up individually

Comment 7

[S.Green]

Attachment: Page 2 via IE

4 of 4: Guess you won't accept .zip files so I'll send them up individually

Comment 8

[Ali Ebrahim]

Reporter, the latest build of Windows Firefox is actually this:
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-i586-pc-msvc.zip
(the other names are misleading, and there is a bug to get them removed)

Could you please test with that and also the latest version of Mozilla? You can
find that here:

ftp://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/mozilla-i586-pc-msvc.zip

Please let us know how it renders in each. FWIW, it works fine for me in both
(it renders in Firefox like it does in your images for IE).

Comment 9

[S.Green]

Attachment: Page 1 in FF of 2004-03-19

#1 of 4.
Thanks for jumping on this.  I installed 2004-03-19 but it hasn't cured the
rendering on my system.  See 4 screen prints

Comment 10

[S.Green]

Attachment: Page 2 in FF of 2004-03-19

#2 of 4.

Comment 11

[S.Green]

Attachment: Page 3 in FF of 2004-03-19

#3 of 4

Comment 12

[S.Green]

Attachment: Page 3 in IE

#4 of 4.

Comment 13

[Jesiah S]

The problem is that the top two images appear on separate lines when the width
of the browser is too small.  This pushes the #div_nav down and into #gutter
(left menu area) and #trans (content) which are both positioned absolutely.
This can fix this by changing the width of TABLE from 100% to 800.

Comment 14

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 15

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.