Closed Bug 206709 Opened 22 years ago Closed 21 years ago

mis-rendering of the webpage www.washingtonpost.com

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: mbougon, Unassigned)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4b) Gecko/20030507 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4b) Gecko/20030507 Mis-rendering of the webpage http://www.washingtonpost.com/wp-dyn/articles/A23265-2003May21.html?nav=hptop_tb Reproducible: Always Steps to Reproduce: 1. 2. 3.
*** Bug 208622 has been marked as a duplicate of this bug. ***
*** Bug 208617 has been marked as a duplicate of this bug. ***
please attach screenshot. related: bug 207289, bug 202547.
WFM: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030604 Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5a) Gecko/20030606 Compared to IE6.
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5a) Gecko/20030607 Can you test with a new profile, created just for testing? What windows are you using, win98 or win98SE ? Do you have Pipelining enabled? ( Preferences->Advanced->HTTP Networking ) Did you deinstall before installing? Bug 208622 was erroneously marked duplicate, it is not related to this bug.
Summary: mis-rendering of the webpage → mis-rendering of the webpage www.washingtonpost.com
What happens if you are reloading with 'Reload', and 'Shift-Reload' ? I saw this misrendering shortly, when I loaded the testcase from another bug, also washingtonpost.com. I´m loading links in the background, and when I was switching to this page while loading, I saw it shortly misrendered, but it continued rendering until it was rendered ok. Did you tweak your preferences? There is a pref for a time after which mozilla starts drawing. What is the speed of your CPU, what are your cache prefs? My cache compare pref is: Every time I view the page. Cache size 50 MB. I was wondering why I wasn´t asked for cookies, but looking in cookiemanager I saw I had allowed cookies for washingtonpost.com. May have happened last time I tested a bug with it. Info for bug-readers: Screenshots to this bug are attached in bug 208617 misrendered: http://bugzilla.mozilla.org/attachment.cgi?id=125142&action=view
Worksforme with Mozilla 1.7 ALpha on windows.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.