76912 - XHTML Transitional document shouldn't be rendered as strict

Status: RESOLVED WORKSFORME

(Core :: XML, defect)

Description

[Chris Petersen]

Build: 2001041908
Platform: All
Expected Result: Noscript content (PCDATA)should be rendered. 
If a document was validated for XHTML Transitional, it should be rendered properly.
What I got: Content is not displayed

Steps to reproduce:

1) To reproduce the issue here, turn off JS in browser and open test case.
2) The pcdata is not displayed even thought the content model for document is
correct (based on the XHTML Trans DTD).
3) Since the content model for NOSCRIPT under strict requires a block , the data
not displayed. This can be confusing to a developer since the document was
written for Transitional in the first place.

Comment 1

[Markus Hübner]

why not having mozilla1.0 as target milestone?!

Comment 2

[Asa Dotzler [:asa]]

Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)

Comment 3

[Nick]

Documents that W3 validates as XHTML 1.0 Transitional get rendered incorrectly 
as XHTML 1.0 Strict and therefore do not display properly.

Comment 4

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Based on the summary, this bug is invalid, since the current behavior is
intentional.  (Standards mode, sometimes called strict mode, has nothing to do
with the strict DTD of long-gone history.)  See
http://mozilla.org/docs/web-developer/quirks/

Comment 5

[Nick]

It's not a bug. It's that the Doctype "XHTML 1.0 Transitional" is "unknown" (at 
least to the browser). In fact, all 3 XHTML DTD's 
[http://www.w3.org/TR/xhtml1/#dtds] that the W3 reccomends are 
considered "unknown" [http://mozilla.org/docs/web-
developer/quirks/doctypes.html]. It's a problem but not a bug.

Comment 6

[Hixie (not reading bugmail)]

Since this bug was filed, we switched to Almost Standards mode for XHTML
Transitional. Therefore this is now WORKSFORME.