New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 846231 link

Starred by 1 user
Status: Duplicate
Merged: issue 831380
Owner: ----
Closed: May 2018
Cc:
█ kochi@chromium.org
Components:
EstimatedDays: ----
NextAction: 2018-06-07
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Iframe content disappears in a fixed container in iframe.

Reported by yyt...@gmail.com, May 24 2018 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36

Example URL:
https://codepen.io/yyt182/pen/deJGar

Steps to reproduce the problem:
1. Chrome of 66 version.
2. DOM structure: iframe -> overlay container -> iframe.
3. Overlay container has style of `position: fixed`.
4. Scroll down more than one screen and trigger the overlay to show.
5. The iframe content in overlay was rendered but not shown.
6. When scroll up, the content shows.

What is the expected behavior?

What went wrong?
The iframe content in fixed overlay(which rendered in an iframe) was rendered but not shown.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes 65

Does this work in other browsers? Yes

Chrome version: 66.0.3359.181  Channel: stable
OS Version: OS X 10.13.4
Flash Version:

Comment 1 by kochi@chromium.org, May 24 2018 

What do you mean by "rendered but not shown"?
Could you attach screenshots of, preferably, both expected and wrong ones?

Thanks,

Comment 2 by kochi@chromium.org, May 24 2018

Cc: kochi@chromium.org
Labels: Needs-Feedback
NextAction: 2018-06-07

Comment 3 by woxxom@gmail.com, May 24 2018 

Fixed in 68.0.3409.0 by e931d2aecb4d72946962e57e7e1586668071b504
"[RLS] Do not apply scroll when clipping fixed-position visual rects"

In good builds the iframe contents is correctly shown within 2 seconds.
In bad builds the iframe is fully or partially empty because its contents is scrolled out of view.

Comment 4 by kochi@chromium.org, May 24 2018

Mergedinto: 831380
Status: Duplicate (was: Unconfirmed)
woxxom@ thanks for the info.
Let me merge to  bug 831380  then.  It seems it's already merged to M67,
and merging to M66 may not happen considering M67 will be released soon.

Comment 5 by monor...@bugs.chromium.org, Jun 7 2018 

The NextAction date has arrived: 2018-06-07
►

Sign in to add a comment