New issue
Advanced search Search tips

Issue 871742 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

cssGrid doesn't respect layers when scrollable element is hidden behind it.

Reported by roddhar...@gmail.com, Aug 7

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.84 Safari/537.36

Example URL:
  https://codepen.io/anon/pen/xJavgp

Steps to reproduce the problem:
1. Adjust the size of the rendered CodePen pane.
2. As the table (hidden behind the Help pane) turns scrollable, the table is suddenly displayed on top of the help pane.
3. 

What is the expected behavior?
The table should remain hidden behind the help pane. (Run the same code in Edge or FireFox and you will see the expected behavior).

What went wrong?
As mentioned.  It would appear that when content that is appropriately hidden behind another element becomes scrollable, the rendering engine suddenly decides that the hidden element should now be displayed and no longer hides it behind the element it was initially behind.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 68.0.3440.84  Channel: stable
OS Version: 10.0
Flash Version:
 
Labels: Needs-Triage-M68
Cc: susan.boorgula@chromium.org
Components: Blink>CSS
Labels: -Type-Bug -Pri-2 RegressedIn-61 Triaged-ET Target-68 Target-69 Target-70 M-70 FoundIn-70 FoundIn-69 FoundIn-68 hasbisect OS-Linux OS-Mac Pri-1 Type-Bug-Regression
Owner: martiw@chromium.org
Status: Assigned (was: Unconfirmed)
roddharris@ Thanks for the issue.

Able to reproduce this issue on Windows 10, Mac OS 10.13.3 and Ubuntu 14.04 on the latest Stable 68.0.3440.84 and latest Canary 70.0.3516.0 as per the original comment.

Bisect Information:
===================
Good Build: 61.0.3122.0
Bad Build : 61.0.3123.0

By running the per-revision bisect script, all bad builds were invoked. Hence below is the manual changelog URL from omahaproxy.

https://chromium.googlesource.com/chromium/src/+log/61.0.3122.0..61.0.3123.0?pretty=fuller&n=10000

From the above Changelog, suspecting the below change:
Reviewed-on: https://codereview.chromium.org/2904173002

martiw@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner.

Thanks
Components: -Blink
Labels: -Needs-Triage-M68
Components: -Blink>CSS Blink>Compositing
Owner: ----
Status: Untriaged (was: Assigned)
That seems like a bad attribution.

Maybe it's bisect-able on another platform. I'll check.
Labels: -Pri-1 -Type-Bug-Regression Pri-2 Type-Bug
Owner: schenney@chromium.org
Status: Assigned (was: Untriaged)
This is not a regression if it happened way back in M-61.

Sign in to add a comment