Position fixed element position and scroll position interacting with rendering of borders within position relative region
Reported by
adam.fly...@gmail.com,
Jan 5 2017
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 Steps to reproduce the problem: 1. Open the issue.html test case. 2. Ensure the browser width is 1440px retina. (This is the full monitor width of a 15" MacBook Pro with the standard 2x retina setting. The monitor resolution is 2880px wide.) 3. Scroll the page. 4. Observe that after scrolling down ~100px, the red border on .grid>div:nth-child(2)::after disappears. What is the expected behavior? The border should not disappear. What went wrong? I suspect that the position fixed element which is positioned outside of the viewport (top:-100px) is disrupting the rendering of the position relative .grid when it would have entered the viewport had it been positioned absolutely or relatively. I use the vague “disrupting” because calc, flex, and ::after may all be at play here as well. This was the minimal test case I could create but the problem exists quite often when there is rounding involved with calc widths in a grid. Did this work before? Yes Does this work in other browsers? Yes Chrome version: 55.0.2883.95 Channel: stable OS Version: OS X 10.10.5 Flash Version: Shockwave Flash 24.0 r0
,
Jan 6 2017
Able to reproduce this issue on Mac 10.12.2 Macbook pro retina with chrome version 55.0.2883.95 and current canary version #57.0.2972.0 Issue is broken in M38. Note: ----- Issue is not reproduced in Windows 10 and Ubuntu 14.04 with latest stable version 55.0.2883.87 Bisect Info: =========== Good build : 38.0.2117.2, Revision Range -288155 Bad build : 38.0.2118.0, Revision Range -288467 After executing the bisect(old) script , i got the following CL's between good and bad build versions =========================================== https://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=%2Ftrunk&range=179751%3A179732&mode=html The suspecting Change Log is : ----------- https://chromium.googlesource.com/chromium/blink/+/fc45e5423d41cd922c6e61edba0051431e0e533d From the above CL suspecting the below change --------------------------- Review URL: https://codereview.chromium.org/449723003 abarth@- Could you please look into this issue, if it's related to your change? if not could you please help us to reassign this issue to the right owner.
,
Feb 13 2017
abarth - please claim as owner if you are working on this.
,
Apr 3 2017
The regression point is so long ago, this is not really a regression. Dropping priority.
,
Apr 3 2017
,
Apr 4 2017
This is probably present on all platforms now that they all support HighDPI.
,
Apr 6 2018
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
,
Apr 6 2018
Issue no longer reproduces on Canary 67.0.3378.0 |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ajha@chromium.org
, Jan 6 2017