Closed Bug 309745 Opened 19 years ago Closed 16 years ago

Strict compliance mode rendering trigger

Categories

(Firefox :: General, defect)

1.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: wolruf, Unassigned)

References

()

Details

(Whiteboard: [closeme 2009-03-14])

Firefox 1.0.7 on WinXP.

URL http://www.cisco.com/public/sw-center/sw-ios.shtml
renders in strict compliance mode

whereas this one renders in quirks mode:
http://www.cisco.com/public/sw-center/sw-lan.shtml

however, source shows the exact same DOCTYPE for both:

<!-- here start --><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
[...]

When saved on local filesystem, both pages render in strict compliance mode, so
I'm thinking perhaps a timing issue causes Firefox to hit a bug and sometimes
render in quirks mode.
They're both showing quirks mode for me while viewing online, and both showing
standards mode while viewing a saved copy. That doesn't seem quite right to me.
Running Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050922
Firefox/1.6a1
http://www.cisco.com/public/sw-center/sw-lan.shtml
Line 133 <!<!-- ***HINAVCONTENT*** -->

Causes the page to be rendered in quirks mode. Removing the extra <! causes the
page to be loaded in standards compliance mode.
Now that's strange, why would rendering depend on something else than the
DOCTYPE declaration ? I'll attach a reduced testcase, thanks for the investigation.
Actually, I couldn't reproduce what you see in comment 2, can you attach reduced
testcase ?
I can't reproduce this because the second link appears to have moved. Is this still a problem in the latest version of Firefox?
Whiteboard: [closeme 2009-03-14]
(Guessing at what the problem is from comment 2.)

data:text/html,<!<!DOCTYPE html><html>Testcase</html>
renders in Quirks mode.  DOMI shows there is comment node in <head>
with the text "<!DOCTYPE html".

HTML5 says in 9.2.4.17 "Markup declaration open state"
http://www.whatwg.org/specs/web-apps/current-work/#markup-declaration-open-state
that this is a parse error and we should enter "bogus comment" state:
http://www.whatwg.org/specs/web-apps/current-work/#bogus-comment-state
which says "Consume every character up to and including the first U+003E GREATER-THAN SIGN character (>) ..."

So, I believe the parsing is correct per HTML5.

-> INVALID
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.