New issue
Advanced search Search tips

Issue 752627 link

Starred by 3 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Changing window height doesn't resize iframe with height: 100% style.

Reported by barmar1...@gmail.com, Aug 4 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36

Steps to reproduce the problem:
Put test1.html and test2.html in the same folder on the server.
1. Open test1.html.
2. Resize the browser window to a smaller size.
3. Increase the browser window height, or click the Maximize button.

What is the expected behavior?
The yellow iframe should expand to fill the browser window.

What went wrong?
The yellow iframe stays the same height, there's a white area below it.

Did this work before? No 

Does this work in other browsers? N/A

Chrome version: 60.0.3112.90  Channel: stable
OS Version: 10
Flash Version: 

This works correctly in OS X. I reproduced it in Chrome versions going back to 52, and in Windows 10 and Windows 8.1.

If you repeat step 3, the iframe expands to fill part of the new area, but still leaves a white gap at the bottom.

Changing just the window width cause the height to update correctly.
 
test1.html
236 bytes View Download
test2.html
143 bytes View Download
Discovered a workaround. Wrap a DIV with style="height: 100%" around the iframe.
Components: Blink>HTML>IFrame
Labels: M-62
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on reported version of chrome#60.0.3112.90 for Win7.

Comment 3 by tkent@chromium.org, Aug 9 2017

Components: -Blink>HTML>IFrame Blink>Layout

Comment 4 by e...@chromium.org, Aug 14 2017

Cc: ikilpatrick@chromium.org
Status: Available (was: Untriaged)
Project Member

Comment 5 by sheriffbot@chromium.org, Aug 15

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
As I said in comment #1, I found a workaround and have been using that in our application.

How should I know if the bug is likely to be fixed or not?
Cc: cbiesinger@google.com
Status: Available (was: Untriaged)
Realistically we're not going to be able to fix this in the near future.
Closing bugs just because they're low priority seems like a strange way to run a software development process (we never did that in any s/w organizations I've been part of), but it's your project, your rules.

How do I go about closing it? The Status field doesn't seem to be editable.
Cc: -cbiesinger@google.com cbiesin...@chromium.org

Sign in to add a comment