Wrong size on IFRAME if position is fixed or absolute and you define values for top and bottom or left and right

RESOLVED INVALID

Status

()

RESOLVED INVALID
11 years ago
11 years ago

People

(Reporter: daniel.andefors, Unassigned)

Tracking

({testcase})

Trunk
x86
Windows XP
testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008031605 Minefield/3.0b5pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5pre) Gecko/2008031605 Minefield/3.0b5pre

An IFRAME with fixed or absolute position where you've defined values for top and bottom or left and right or all of these will not be sized correctly. 

Reproducible: Always

Steps to Reproduce:
1. Create an HTML page with an IFRAME.
2. Using CSS, set position to fixed or absolute on the IFRAME.
3. Using CSS, set top and bottom, left and right or all on the IFRAME.
Actual Results:  
The height or width of an IFRAME with fixed or absolute position is not derived from top and bottom or left and right respectively. What happens is that if you define values for top and bottom the value for bottom is ignored and it seems that the IFRAME gets some default height. Similarly, if you define values for left and right the value for right is ignored.

Expected Results:  
The height of an IFRAME with fixed or absolute position should be derived from top and bottom. The width should be derived from left and right.
(Reporter)

Comment 1

11 years ago
Created attachment 309898 [details]
HTML testcase

Updated

11 years ago
Attachment #309898 - Attachment mime type: text/plain → text/html

Updated

11 years ago
Keywords: testcase
Version: unspecified → Trunk

Comment 2

11 years ago
Unlike a div the iframe is a replaced element.  So you have to set the width explicitly.  Firefox 2 was incorrect with handling this according to CSS 2.1.  

See Bug 412679.  
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.