We've made good progress on the StrictDTD handling system. After discussions with hamerly, I'm convinced that it would be useful to get beta2 feedback on this code. The code is controlled by an environment setting (non-mac) which I propose enabling by default. If during beta testing (prior to beta2 release) we determine that it's problematic, we'll return the default setting to OFF.
Requestion nsbeta2 checkin.
Status: NEW → ASSIGNED
Putting on [nsbeta2+][5/16] radar.
*** Bug 34688 has been marked as a duplicate of this bug. ***
Putting on [NEED INFO] radar. PDT requests ekrockinput at tomorrow 4pm mtg on this issue.
Whiteboard: [nsbeta2+][5/16] → [NEED INFO]
What happened? This was on tap to land when the tree opened for new feature work, and now it's [need info]? Grrr. If this code doesn't land, we CANNOT claim to support XHTML, since it can be rendered as BOTH html and xml. StrictDTD is the only way to do that, in addition to providing support for strict-mode HTML4. I don't know whether Ekrock is aware of these issues.
Recommend nsbeta2+. Essential for being able to state strict compliance with HTML 4.0 spec as well as for enabling interoperability of XML and HTML for content/web app platform through XML Namespaces and XHTML. Also low risk as strict DTD is only invoked when DTD at top of HTML file requests it.
Whiteboard: [NEED INFO]
Ekrock is my hero. :)
The PDT has agreed to give this beta2+ status until 6/15.
Adding [6/15] indication.
Whiteboard: nsbeta2+ → [nsbeta2+][6/15]
*** Bug 40893 has been marked as a duplicate of this bug. ***
This was landed on Friday; strict and transitional 4.0 DTD's are now active. To disable them, you can set MOZ_DISABLE_STRICT in your environment.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.