Bug 9966 - Unclosed "object" tag prevents content following it from being displayed
Summary: Unclosed "object" tag prevents content following it from being displayed
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL: http://www.nieuwerevu.nl/media/nieuws...
Keywords: HasReduction
: 12708 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-07-17 01:41 PDT by Alexander Kellett
Modified: 2012-12-27 11:37 PST (History)
3 users (show)

See Also:


Attachments
Reduction (206 bytes, text/html)
2006-08-13 02:18 PDT, Mark Rowe (bdash)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kellett 2006-07-17 01:41:15 PDT
Content is missing in both a nightly and in 10.4.7. Content is rendered as expected in firefox.
Comment 1 Mark Rowe (bdash) 2006-08-13 02:18:51 PDT
Created attachment 10012 [details]
Reduction

The original page contains two unclosed "object" tags.  The second one has no parameters, so I assume it is intended to be the closing tag of the first and has simply had the / omitted.

This reduced test case demonstrates how we handle an unclosed "object" tag differently than Firefox, leading to content not being displayed.
Comment 2 Alexey Proskuryakov 2007-02-09 09:44:32 PST
*** Bug 12708 has been marked as a duplicate of this bug. ***
Comment 3 Robert Hogan 2011-07-17 03:48:31 PDT
Today WebKit does display the content in the reduction with a vertical border line after it, Firefox and Opera display a border line before and after the line of content.
Comment 4 Robert Hogan 2012-12-27 11:37:12 PST
OK, although we display the reduction slightly differently from other browsers (and they differ among themselves too) - the original bug has been resolved, WebKit does now display content after an unclosed object tag. I don't think there's any right or wrong way to display an unclosed object tag itself so I'm going to close this bug. Please re-open if there's something to do here.