Closed Bug 433883 Opened 16 years ago Closed 16 years ago

A flash object only appears on half the page

Categories

(Core :: Layout, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: josh.tumath+bugzilla, Unassigned)

References

()

Details

Attachments

(2 files)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008051406 Minefield/3.0pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008051406 Minefield/3.0pre

A flash applet by the BBC is made via CSS to appear covering the entire page. The following is ALL of the CSS on the page:

<style type="text/css">
<!--
body{
	height: 100%;
	width: 100%;
	margin: 0px;

-->
</style>

The applet only appears on the top half of the page. The bottom half is just a blank space.

Reproducible: Always



Expected Results:  
The hole page should be covered with the flash object.
Flags: blocking1.9?
Version: unspecified → 1.8 Branch
Can you test this in Firefox 2 and the Firefox 3 nightlies to understand when this broke - unfortunately I cannot test the URL in the US (page says it cannot be viewed outside the UK)
Keywords: qawanted
Confirmed as a regression between Fx2 and Fx3 RC1 build1 (testing on OS X Tiger). Trying to narrow that range now.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: 1.8 Branch → Trunk
I see the same half-screen display with 3.0a1, a4, a5, b2 and b3 (the stuff I had on disk). Do you want to go digging in the pre-alpha1 nightlies ?
This regressed between the 2005-10-07 and 2005-10-08 nightlies (see http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2005/10/)

The checkin window is http://tinyurl.com/5ehaus - taking a stab at CC'ing the relevant developers.
This is a regression from bug 309118. Before that the object tag gets a vertical-align of baseline, after it defaults to top.
Blocks: 309118
Any chance of attaching a testcase that shows the problem to this bug?  The site locks out IP addresses that are not in the UK, apparently, so I can't see what the page looks like...
So the problem is that we're applying the 'vertical-align: top' to the OBJECT, but what we're displaying is the EMBED inside it.  That that combination sticks out of the top of the page is a longstanding bug (bug 118501).
Ah, so the issue is that the <object> is aligned, and so is the the <embed>, and they're aligned _differently_, right?  That is, removing the align attr on the embed, or setting it to "top" will give the correct behavior.

This is basically a bug in the page.  It used to work because we ignored the align="top" on the object altogether earlier in the 1.9 cycle, and used to work in 1.8 because we removed the <object> from the rendering tree completely there.
So I think the correct long-term fix (or at least part of it) is the pair of patches I put in bug 118501; I'm not sure what the right thing to do for 3.0.* is, though.
David/Bz you ok with taking this off the 1.9 blocker list then?
I think I am, yes.
Umm. Shouldn't Firefox be able to fix this anyway? Quite a lot of websites might have this problem.
> Shouldn't Firefox be able to fix this anyway? 

That's what bug 118501 is about.  We could back out the patch that triggered this on trunk, but that would break other sites, so...

> Quite a lot of websites might have this problem.

To be honest... this is the first report of this problem.  It's been around since October 2005 (two and a half years).  The fact is, to trigger it you need to have an embed inside an object, align them both, and align them _differently_.  That last part is really rare.
embed inside IE-specific-object is unfortunately the most common way of embedding plugins, though.
So is this bug a problem that the BBC should be worried about rather than a Gecko rendering issue?
...or one of the most common, anyway.
David, it's the "align them both and align them differently" part that's rare, from what I've seen.

Josh, the BBC could fix it pretty easily by simply using align="top" on both nodes.  It's still a Gecko rendering issue, of course.
Given comment 13, comment 15, and comment 19 I'm taking this off the blocker list.  
Flags: wanted1.9.0.x+
Flags: blocking1.9?
Flags: blocking1.9-
this is now FIXED by the fix for Bug 118501 testing the bbc site example and the attached testcase.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1a1pre) Gecko/2008071103
Status: NEW → RESOLVED
Closed: 16 years ago
Keywords: qawanted
Resolution: --- → FIXED
Flags: wanted1.9.0.x+
Product: Core → Core Graveyard
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: