Closed
Bug 85905
Opened 23 years ago
Closed 23 years ago
Page Info should show quirks vs standard mode
Categories
(SeaMonkey :: Page Info, enhancement)
SeaMonkey
Page Info
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.9
People
(Reporter: jo.hermans, Assigned: db48x)
References
Details
Currently you can only see Title, URL and last modified. Useful additions would be :
- content-length
- content-type (it's imppossible to see if it's html or xml for instance)
- expires
- character-coding (like in the view menu)
- all headers (if still present, maybe show them an a separate tab)
- a button to view-source
- an indicator if it was parsed in struct or quirks-mode
Assignee | ||
Comment 2•23 years ago
|
||
yea, it's a dup, though it does mention one interesting thing, quirks vs
standard mode. Interesting, reporter, can we make this bug just about that one
little bit?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 3•23 years ago
|
||
Sure, add it to the list in 52730.
I need the standard/quirks indication, to see if a page is ok for
Mozilla/Netscape 6 or for the older version of the browser. Until now, it was
difficult to determine.
You might want to use other words to present this to the user. Maybe "Standard
Mode" and "Compatible Mode" or something.
Comment 4•23 years ago
|
||
I suggest one more useful addition: a "Server:" field (the server's product
token field as returned by the server in conformance with HTTP specification).
Comment 5•23 years ago
|
||
Reproduced on build 2001091303 on Windows ME.
Should this bug be assigned to component "User Interface Design" to remove it from
the prescreen list (http://www.mozilla.org/quality/browser/prescreening.html)?
Assignee | ||
Comment 6•23 years ago
|
||
Dunno why I didn't triage it. Thanks for reminding me.
Assignee: asa → db48x
Blocks: 82059
Severity: normal → enhancement
Component: Browser-General → XP Apps: GUI Features
OS: Windows NT → All
Hardware: PC → All
Summary: Page Info should show more information → Page Info should show quirks vs standard mode
Assignee | ||
Comment 7•23 years ago
|
||
well, now that bug 105640 is fixed, this shouldn't be too difficult.
Status: NEW → ASSIGNED
Assignee | ||
Comment 9•23 years ago
|
||
Feel free to comment on the text it shows:
generalQuirksMode=This document was rendered in compatibility mode.
generalStrictMode=This document was rendered in standards compliance mode.
Comment 10•23 years ago
|
||
In a help file, you'll want to explain what these two modes mean.
Assignee | ||
Comment 11•23 years ago
|
||
I'll be back from vacation soon.
Target Milestone: --- → mozilla0.9.8
Assignee | ||
Comment 13•23 years ago
|
||
yay! finnally checked in. Thank you bz :)
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 14•23 years ago
|
||
Bug 31932 addresses documentation for quirks mode.
Component: XP Apps: GUI Features → Page Info
QA Contact: doronr → pmac
Comment 15•23 years ago
|
||
*** Bug 122385 has been marked as a duplicate of this bug. ***
Comment 16•23 years ago
|
||
Is it possible yet to determite whether the page validates to its doctype?
Comment 17•23 years ago
|
||
No, Mozilla doesn't do validation. The easiest way to add the capability to send
pages to a remote validator is to use a bookmarklet:
http://www.hut.fi/u/hsivonen/test/validate
Comment 18•23 years ago
|
||
Verified (commerical build: 2002-02-14-10-trunk)
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•