page render(layout) is incorrect when some elements is fixed.
Reported by
qingzhao...@gmail.com,
Oct 22
|
|||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3587.0 Safari/537.36
Example URL:
Steps to reproduce the problem:
1. open attach file html, page display incorrectly. Diff from Firefox and safari.
html code:
<!DOCTYPE html>
<html>
<head>
</head>
<body>
<style>
</style>
<div style="overflow: hidden; margin: 0 200px; border-radius: 8px;">
<div style="width: 100%; padding-bottom: 500px; position: relative;">
<div style="overflow: hidden; z-index: 5; position: absolute; top: 0; left: 0; width: 100%; height: 100%;">
<div style="position: fixed; top: 0px; left: 0px;
margin:0; padding:0; height: 100%; width: 100%; z-index: 9999;background-color: blue;">
</div>
</div>
</div>
</div>
</body>
</html>
What is the expected behavior?
What went wrong?
Page layout error.
Does it occur on multiple sites: Yes
Is it a problem with a plugin? N/A
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 72.0.3587.0 Channel: canary
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
,
Oct 22
Bisected to https://chromium.googlesource.com/chromium/src/+log/ed59882d..a0494357?pretty=fuller Suspecting r471158 Fix the bug that absolute positioned element moves unexpectedly Before Chrome 60: the entire page is blue just like Firefox. Chrome 60-61: totally broken (a blue T-like shape is displayed) Chrome 61-Canary: a blue rectangle is displayed (bisected to r484751).
,
Oct 23
qingzhao2008@ Thanks for filling the issue... Able to reproduce the issue on reported chrome version 72.0.3587.0 also on latest chrome 72.0.3588.0 using Mac 10.13.6, Ubuntu 14.04 and Windows 7 & 10. Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged. As per comment #2 CC'ing Dev for further inputs. Note: On m-60 observed as attached screenshot and M-70 seen blue rectangle and on firefox entire page is blue. Thanks..!
,
Oct 25
This is a case where SPv1 compositing does not allow the fixed-position descendant to escape border-radius clipping. It appears to be fixed by BGPT (--enable-blink-features=BlinkGenPropertyTrees) This feature should launch in Chrome 72. Assigning to myself to verify and close bug when that happens.
,
Oct 31
chrishtr@chromium.org, why not fix in chrome 70 or 71?
,
Nov 15
Can confirm that I had render bugs (header cells of table not rendering/all white) where one of the ancestors element of the table had position:fixed. (I found a workaround for our app in production by changing its position to relative and adding more CSS.) This was not the case a month ago - version 70ish broke it a couple weeks ago. |
|||
►
Sign in to add a comment |
|||
Comment 1 by swarnasree.mukkala@chromium.org
, Oct 22