Closed Bug 121531 Opened 23 years ago Closed 22 years ago

[quirks] dissentmagazine.org - bad title tag interferes with layout

Categories

(Core :: Layout, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 42945

People

(Reporter: contact2009, Assigned: doronr)

References

()

Details

The front page of the URI, http://www.dissentmagazine.org/, does not display in
Mozilla 0.9.7, Build ID: 2002012304, Windows 98. In IE 6, it shows up okay.
*** Bug 126781 has been marked as a duplicate of this bug. ***
It appears the main content frame of this page is not rendering because it has a
<title="archive/index"> tag in <head>. This isn't valid in any spec AFAIK, but
should this really be causing Mozilla to panic?

Content: 
http://www.dissentmagazine.org/archive/index.shtml
Summary: page does not show in Mozilla → dissentmagazine.org - renders as blank page
Thanks. That's right, this doesn't look like tech evangelism.

A reduced testcase is, any page that has an opening title tag but not a closing
title tag renders blank. This is the case even if there is a closing head tag.
If the title tag is munged, we should still render everything after after a
closing head tag.

--> Browser/Layout. If turns out to still be tech evangelism, you will have my
apology.
Component: US General → Layout
Product: Tech Evangelism → Browser
Summary: dissentmagazine.org - renders as blank page → [quirks] dissentmagazine.org - renders as blank page
Version: unspecified → other
Summary: [quirks] dissentmagazine.org - renders as blank page → [quirks] dissentmagazine.org - bad title tag interferes with layout
Page now works. Title tag is fixed.

Doron, should Mozilla treat <title="Hello, this is a web page"> as a valid tag,
or should we move this back to tech evangelism, and resolve it as fixed?
If this is not tech evangelism, this bug may be a dupe of bug 42945.
This bug is a dupe.

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