Bug 10499

Summary: <object> shown despite having display: none
Product: WebKit Reporter: Eric Seidel (no email) <eric>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: ap, jonathanjohnsson, mitz
Priority: P4 Keywords: HasReduction
Version: 420+   
Hardware: Mac   
OS: OS X 10.4   
URL: http://www.cellphones.ca/cell-phones/phone/271/
Attachments:
Description Flags
testcase for <object> issue none

Description Eric Seidel (no email) 2006-08-21 13:38:25 PDT
Safari loads iframes wrong on this page

Firefox seems to load them correctly.

Safari reloads the same page inside all of the iframes.  Maybe it's a server issue, not sure.
Comment 1 crastinator 2006-08-21 17:23:00 PDT
I can confirm this oddity as well using build r15952 and firefox 1.5.06
Comment 2 Matt Lilek 2006-08-22 23:08:38 PDT
Created attachment 10175 [details]
testcase for <object> issue
Comment 3 Matt Lilek 2006-08-22 23:09:04 PDT
This is not an issue with iframes at all, but with the <object> tag.

The <object> tags on that page are set to display:none; but lack a type attribute.  <object> tags lacking a type attribute and set to display:none; are displayed, but once the type attribute is added, it is not displayed.

I've uploaded a testcase displaying this behavior.  The issue is present in both Safari 2.0.4 and r15975; works correctly in Firefox 1.5.0.6.
Comment 4 jonathanjohnsson 2006-08-24 10:41:10 PDT
Changing summary and keyword to reflect Matt's findings.

I don't know what component this belongs to, so changing to "New Bugs".
Comment 5 Sebastien Boisvert 2007-02-19 16:28:17 PST
My tests on the latest nightlies show that the type attribute doesn't make any difference.
Comment 6 Rob Buis 2007-08-25 12:42:14 PDT
Seems fixed in ToT.
Cheers,

Rob.
Comment 7 David Kilzer (:ddkilzer) 2007-08-26 06:52:32 PDT
Closing per Comment #6.  I also verified this is fixed using the test case in Attachment #10175 [details].

Comment 8 mitz 2007-08-26 07:24:49 PDT
(In reply to comment #6)
> Seems fixed in ToT.

I'm still seeing this with plugins, but I'll file a separate bug on that.