Closed Bug 31932 Opened 23 years ago Closed 8 years ago

NavQuirks mode doc - review & update?

Categories

(Documentation Graveyard :: Web Developer, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
Future

People

(Reporter: sacolcor, Assigned: dbaron)

References

()

Details

(Whiteboard: relnote-user)

This bug is being split off from #1044 as the result of issues raised there.  
The resolution of this bug has three stages:

1)  Document NavQuirks. In particular, list any HTML/CSS standards violations 
that result from it.  Then document the behavior of IE5 on each of those 
issues, and also list how the W3C spec says it should be done.  Make this 
document publicly available in some way.

2)  For each issue from #1, decide how Mozilla should behave as follows:  If 
IE5 matches the W3C spec, we should too, even in NavQuirks mode.  If IE5 
matches Nav4, we should leave the quirk in.  Otherwise, decide on a case-by-
case basis based on what will keep the most pages on the web working.  

3)  File new bugs for any issues found in #2 requiring a change in Mozilla's 
behavior.  Make sure that the bug description includes updating the document 
prepared in #1.
Status: UNCONFIRMED → NEW
Ever confirmed: true
A good start to finding the places where we are using NavQuirks mode is:
   http://lxr.mozilla.org/seamonkey/search?string=mParseMode

Hardware: PC → All
Summary: NavQuirks mode needs to be documented and examined. → NavQuirks mode needs to be documented and examined
Most of the quirks are handled in CNavDTD, I think. Reassigned to rickg for an 

assessment of the problem.

Assignee: pierre → rickg
I agree with the documentation idea. Marking remind.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → REMIND
Even if the exact details of the Quirks mode are currently undocumented, the
existance of the Quirks mode (and how to force Standard mode) should be
documented conspicuously ASAP on www.mozilla.org to ease the work of Web
designers who are testing their markup and styles with Mozilla.
Verified REMIND
Status: RESOLVED → VERIFIED
Blocks: 34662
Marking "relnote". We need to mention this in the release notes even if we have
not yet documented the complete list of quirks.
Keywords: relnote
Split the preliminary documentation of the existance of the quirks mode as bug

36045.

Depends on: 36045
Would a template help? I wrote up a template and a sample form:
http://www.escape.com/~fantasai/MozQuirks/index.html

BTW, shouldn't this be moved to Documentation?
Component: Style System → Web Developer
Product: Browser → Documentation
Version: other → unspecified
Reopening and moving to Future...
Status: VERIFIED → REOPENED
Resolution: REMIND → ---
Target Milestone: --- → Future
QA Contact: chrisd → rudman
We need to relnote the existence of Quirks, certainly...

Gerv
Whiteboard: relnote-user
The existence of Quirks is covered by bug 36045.

BTW, why is this one relnote-user and 36045 relnote-devel?
I just wrote a draft list at
http://www.people.fas.harvard.edu/~dbaron/mozilla/quirklist
based on the URLs above.

Taking this bug.
Assignee: rickg → dbaron
Status: REOPENED → NEW
Status: NEW → ASSIGNED
Blocks: 86578
With the checkin of bug 55264,
http://www.people.fas.harvard.edu/~dbaron/mozilla/doctypes is now accurate
documentation.
Blocks: 57237
Summary: NavQuirks mode needs to be documented and examined → NavQuirks mode doc - review & update?
No longer blocks: 57237
QA Contact: rudman → ian
Closing this very old bug. Please open a new bug in the "Developer Documentation" product (to get on MDN's radar), if there is still an issue that is worth a bug.

Information discussed above lives here on MDN now:
https://developer.mozilla.org/en/docs/Mozilla_Quirks_Mode_Behavior
https://developer.mozilla.org/en-US/docs/Quirks_Mode_and_Standards_Mode
Status: ASSIGNED → RESOLVED
Closed: 23 years ago8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.