Closed Bug 118147 Opened 23 years ago Closed 21 years ago

Mozilla should have an option to select between quirks and standard layout mode

Categories

(Core :: Layout, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 84636
Future

People

(Reporter: joakim_46, Assigned: attinasi)

Details

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; Win 9x 4.90)
BuildID:    20011229

Mozilla should have an option to select between quirks and normal
layout mode. Somes pages are not well rendered on Mozilla due to
the default use o quirks mode. Most webmasters don't add the necessary
code on the page, to be rendered in standard mode. So Mozilla should be able to 
let the user select.

Reproducible: Always
Steps to Reproduce:
1. Start Mozilla
2. Some pages are not well rendered due to the default use of quirks mode


Actual Results:  Some pages are not well rendered

Expected Results:  All pages should rendered like in IE 6.0 (or even better)
Confirming change
How common are pages that are rendered in quirks mode but rely on things working 
like in standard mode?  Are there particular quirks that are responsible?

This is _not_ the sort of toggle users would typically want.  If this is done, I 
would suggest it be in debug prefs only.
More likely it would be pages we render in standards layout mode, that would
look better in quirks mode.  Can you give a real world example of a page that
looks better in Standards than Quirks?  I could conjure one up I'm sure but I'd
be surprised to see this en masse on the web.

In any case, the better fix IMO would be to fix the appropriate mode's rendering
if possible, though this *would* be an interesting debug pref... A good April
Fool's joke no doubt to force someone's browser to standards mode :)
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows ME → All
Hardware: PC → All
Target Milestone: --- → Future
I guess this requires an icon --> http://bugzilla.mozilla.org/show_bug.cgi?id=155482
Also, note that changing mode requires reloading the page (since there is
mode-specific stuff in the parser).  If the page is not in cache, that means
hitting the server again.

*** This bug has been marked as a duplicate of 84636 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.