New issue
Advanced search Search tips

Issue 705214 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 700383
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

when "position: fixed" element inside grid container, is hidden, no redraw of other elements

Reported by howard.e...@gmail.com, Mar 25 2017

Issue description

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

Steps to reproduce the problem:
1. Set up a CSS-Grid layout in a container, and also include an element that is position fixed (like a slideshow overlay). 
2. Then Hide the fixed element with javascript (like someone is closing the slideshow to return to the normal layout.

Codepend example:
http://codepen.io/howardelton/full/ZejWdg/

1. click the button to display the overlay.
2. click the overlay to make it disappear (where the error occurs)

What is the expected behavior?
When element is hidden, the layout behind it should remain unaltered, and become fully visible. This is the behaviour in FF 52.

What went wrong?
When the element is hidden, the space where is was turns white and the elements underneath are not redrawn. 

Did this work before? No 

Chrome version: 57.0.2987.110  Channel: stable
OS Version: 10.0
Flash Version: 

If the "position: fixed" element is moved to outside of the Grid container, then it functions as expected. Since this is not required in FF, I think it is a bug.
 
Should be under Blink>Layout>Grid
fishing data
Labels: Needs-Triage-M57
Cc: pbomm...@chromium.org gov...@chromium.org
Components: -Platform>DevTools Blink>Layout>Grid
Labels: -Type-Bug -Needs-Triage-M57 M-59 OS-Linux OS-Mac Type-Bug-Regression
Owner: r...@igalia.com
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Win 10, Mac 10.12.3 and Ubuntu 14.04 using 57.0.2987.110.This is fixed in latest beta 58.0.3029.33  and canary 59.0.3054.0.

Reverse Bisect info:
===================
Good: 59.0.3043.0
Bad : 59.0.3042.0
You are probably looking for a change made after 457060 (known good), but no later than 457061 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/5c7a83e9da26f8621d4b17196c22c75fb1dca45f..eb7634d5a91a495af9495164ffb2e5f1f91f7e09
Review-Url: https://codereview.chromium.org/2748983003
rego@: Could you please take a look into this if its related to your change, and merge into M57 as its already merged into M58(3029).
Not adding Stable-blocker as this looks not working properly even in 56.0.2924.87.

Comment 6 by r...@igalia.com, Mar 28 2017

Mergedinto: 700383
Status: Duplicate (was: Assigned)
Yes it seems the very same issue than  bug #700383 .

@durga.behera the merge into M57 was requested and rejected as you can see in:
https://bugs.chromium.org/p/chromium/issues/detail?id=700383#c36

Sign in to add a comment