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

Issue 722140 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Border-radius and overflow: hidden with position fixed. Clip is broken

Reported by hololelo...@gmail.com, May 14 2017

Issue description

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

Steps to reproduce the problem:
1. Open this link http://lelouch.ru/bugs/overflow/
2. Open dev tools and emulate some mobile device, like Galaxy S5 or iPhone, or else. Nevermind.
3. You will see some red corners inside rounded div

What is the expected behavior?
Red corners should not be there

What went wrong?
Overflow hidden is not working with this construction (check link http://lelouch.ru/bugs/overflow/)

Did this work before? No 

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

You can reproduce this bug only if you have construction like this http://lelouch.ru/bugs/overflow/

Div with fixed position inside div with fixed position.
You should set oveflow: scroll/auto to main parent div with fixed position (class="wrap")
You should have parent div with position relative (class="relativeParent")
You should have some scrollable content to reproduce this bug

If you have style Overflow: hidden on parent div (class="relativeParent", i have commented this, you should uncomment to see the result) the bug will gone.

If div class="relativeParent" will not have relative or absolute position, the bug will gone.

Also this bug is exist on chrome mobile (latest stable) on android 7
 
bug_confirmed.png
58.8 KB View Download
Labels: Needs-Triage-M58
Labels: -Type-Bug -Pri-2 hasbisect-per-revision M-60 OS-Linux Pri-1 Type-Bug-Regression
Owner: trchen@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Windows-7, Mac-10.12.4 and Linux Ubuntu-14.04 using chrome stable version 58.0.3029.110 and canary 60.0.3100.0.This is regression issue, broken in M52.

Using the per-revision bisect providing the bisect results,
Good build:52.0.2713.0-(Revision:388380).
Bad build:52.0.2714.0- (Revision:388647).
CHANGE-LOG URL:
https://chromium.googlesource.com/chromium/src/+log/1e9c8f7aa1a0e05450bdc35b94fdbf37c2f1cf18..66024c61d8dedbf67abe5ada9c521d0f6f909895

Review URL: https://codereview.chromium.org/1898393002	
trchen@ Could you please look into this issue, help us to assign this issue to the right owner if not respect to your change.

Thanks.

Labels: OS-Mac

Comment 4 by trchen@chromium.org, May 15 2017

Cc: schenney@chromium.org chrishtr@chromium.org
Components: -Platform>DevTools Blink>Compositing Blink>Paint
Labels: -OS-Linux -OS-Windows -Pri-1 -Arch-x86_64 -OS-Mac -M-60 -hasbisect-per-revision -Needs-Triage-M58 OS-All Pri-2
Status: Untriaged (was: Assigned)
This is not a new regression. The bisected change only revealed a convoluted case of an existing bug. Here is a minimal repro: http://jsbin.com/cometuhuku/

The general issue is that squashed layers don't apply ancestor rounded clip, because their PaintLayerPainter uses themselves as the painting root and rely on CLM to apply ancestor clip for them (which CLM doesn't handle rounded clip correctly). Interestingly I worked on a related issue recently, but decided to abandon the fix because it was too complex: https://codereview.chromium.org/2835783002/

Cc: trchen@chromium.org
Labels: -OS-All -Type-Bug-Regression BugSource-User PaintTeamTriaged-20170515 OS-Android OS-Chrome OS-Fuchsia OS-Linux OS-Mac OS-Windows Type-Bug
Owner: ----
Status: Available (was: Untriaged)
Can someone explain the relationship to https://bugs.chromium.org/p/chromium/issues/detail?id=712783?
The relationship is that both involve special cases of squashed layers.
Labels: -OS-Fuchsia
Project Member

Comment 9 by sheriffbot@chromium.org, Jun 29 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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
Status: WontFix (was: Untriaged)
This has been fixed, at least in the latest Canary.

Sign in to add a comment