standards incomplient page can trigger standards compliance mode; M$ can manipulate this
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mozilla Firefox |
Won't Fix
|
Medium
|
|||
firefox (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
firefox-3.0 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: mozilla-firefox
If there is a valid DTD at the beginning of the (x)htm(l) file, firefox assumes it's a valid file, even when gecko reports invalid code. As a result, the invalid website is parsed in standards compliance mode instead of quirks mode. If IE starts requiring DTDs (for invalid, MSIE compatible code), quirks mode won't work at all because it will never be triggered. To reproduce:
0. have a standards incompliant html authoring program installed (e.g. Dreamweaver)
1. Make a fairly complex web page/site (offline of course)
2. Confirm the presence of and/or add a valid doctype declaration per the instructions somewhere at www.w3c.org
3. View the page in Firefox. Check the page properties. It will be in "standards compliance mode." Since your page is littered with invalid code, it should have switched to quirks mode at some point during rendering.
I KNOW what a DTD means. It means "I am using valid code of format foo." But if the code is not valid, surely it makes sense to switch to quirks mode? Suppose Microsoft changed MSIE to require a DTD? The web designers would figure this out and spread it by way of blog, and all of a sudden, the Internet (tm) doesn't work on firefox.
Changed in firefox: | |
status: | Unknown → New |
Changed in firefox: | |
status: | New → Won't Fix |
Changed in firefox: | |
importance: | Unknown → Medium |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008050509 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008050509 Firefox/3.0b5
If there is a valid DTD at the beginning of the (x)htm(l) file, firefox assumes it's a valid file, even when gecko reports invalid code. As a result, the invalid website is parsed in standards compliance mode instead of quirks mode. If IE starts requiring DTDs (for invalid, MSIE compatible code), quirks mode won't work at all because it will never be triggered. To reproduce:
I KNOW what a DTD is. It means "I am using valid code of format foo." But if the code is not valid (and the DTD is), surely it makes sense to switch to quirks mode? Suppose Microsoft changed MSIE to require a DTD? The web designers would figure this out and spread it by way of blog, and all of a sudden, the Internet (tm) doesn't work on firefox.
Reproducible: Always
Steps to Reproduce:
0. have a standards incompliant html authoring program installed (e.g. Dreamweaver)
1. Make a fairly complex web page/site (offline of course)
2. Confirm the presence of and/or add a valid doctype declaration per the instructions somewhere at www.w3c.org
3. View the page in Firefox. Check the page properties (right click -> view page info).
Actual Results:
It will be in "standards compliance mode."
Expected Results:
Since your page is littered with invalid code, it should have switched to quirks mode at some point during rendering.
This is forwarded by reporter from #236960 in the Ubuntu Launchpad @ /bugs.launchpad .net/ubuntu/ +source/ firefox/ +bug/236960
https:/
I wasn't entirely certain what to set severity to, so I left it at Normal. You might even call this an enhancement, if you look at it the right way...