Closed
Bug 48819
Opened 25 years ago
Closed 25 years ago
Page completely messed
Categories
(SeaMonkey :: General, defect, P3)
Tracking
(Not tracked)
People
(Reporter: devotip, Assigned: asa)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; m18) Gecko/20000812
BuildID: 2000081208
Just look
Reproducible: Always
Steps to Reproduce:
1. open http://www.cpureview.com/art_64bit_a.html
Actual Results: everything is on a large dark blu bakground column
Expected Results: something on the left in a narrow dark blu background column
something on the right in a large light blu background column
|
||
Comment 1•25 years ago
|
||
It is the DOCTYPE that triggers strict mode:
<!DOCTYPE HTML PUBLIC "-//SoftQuad//DTD HoTMetaL PRO 4.0::19970714::extensions
to HTML 4.0//EN" "hmpro4.dtd">
I changed the DOCTYPE to HTML 4.0 Transitional and then asked
http://validator.w3.org to validate -- it found lots of errors...
Removing the DOCTYPE makes the document render fine in Mozilla 2000-08-12-08.
Recommending WORKSFORME.
|
Reporter | |
Comment 2•25 years ago
|
||
I'm not sure. The avalanche error after changing to html 4 could be because the
non standard dtd is needed I'll do a check on what errors are there after
dropping the hmpro4.dtd
|
|
Reporter | |
Comment 3•25 years ago
|
||
Some of the errors are because the page is generated in part by a javascript, it
is not wrong because of that.
One interesting fact is that by simply removing doctype or replacing the origina
doctype with the html 4 transitional the page has the proper layout.
The non standard doctype IS the source of the issue but still can't tell if is
triggering a bug or is bogous on its own
|
|
Reporter | |
Comment 4•25 years ago
|
||
going to the owners of the nonstandard doctype dtd stuff is easy to find
improperly handled pages like
http://www.softquad.com/
http://www.hotmetalpro.com/support/
and yes I know, this is becoming a bad bug report becouse is not pointing to a
specific event but with these pages I'm not able to decide if and what is bad
standard compliance or a Mozilla implementation issue.
So feel free to dissect the provided links and post other bugs if appropriate or
if really all is to put on the "is not standard compliant" pile mark this bug as
invalid
|
||
Comment 5•25 years ago
|
||
Actually this is becoming a bad bug report because the issue is already reported
at Bug 48421. Searching for duplicate reports saves your time, and the time of
the Mozilla team.
*** This bug has been marked as a duplicate of 48421 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
|
||
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•