New issue
Advanced search Search tips

Issue 739348 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug-Regression



Sign in to add a comment

box-shadow inset does not work for all offsets

Reported by bry...@gmail.com, Jul 5 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:54.0) Gecko/20100101 Firefox/54.0

Steps to reproduce the problem:
1. Visit the Pen: https://codepen.io/bryeva/pen/qjKMRV in Chrome 59 or 60(Dev)
2. Hover over the text
3. Move the cursor outside of the rectangle
4. Repeat

What is the expected behavior?
The animation should be fluid / smooth.

What went wrong?
The animation flickers at random intervals when viewing with Chrome 59 or 60(Dev) on Mac/PC.

Did this work before? Yes 58

Does this work in other browsers? Yes

Chrome version: Version 59.0.3071.115 (Official Build) (64-bit)  Channel: n/a
OS Version: OS X 10.12.3
Flash Version: Shockwave Flash 26.0 r0

There is a similar bug - number 713674 - https://bugs.chromium.org/p/chromium/issues/detail?id=713674#

This dealt with mismatched list lengths in shadow interpolation for box-shadow transitions. I suspect this may be similar as when the 'inset' box-shadow attribute is added, it behaves in a similar flickering way.

Box-shadow transitions without the 'inset' attribute work fine.
 
box-shadow-chrome-bug.zip
2.1 KB Download

Comment 1 by bry...@gmail.com, Jul 5 2017

UserAgent for the browser that is experiencing the issue: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36
Components: -Blink>Animation Blink>Paint
Labels: -OS-Mac Needs-Bisect OS-All
Status: Untriaged (was: Unconfirmed)
Summary: box-shadow inset does not work for all offsets (was: Chrome Box-shadow transition issue with inset)
Recreated the bug using JS instead of animations:
https://codepen.io/anon/pen/owMLJB?editors=0110
This is most likely a painting issue.
Labels: PaintTeamTriaged-20170707 BugSource-User
Owner: schenney@chromium.org
Status: Assigned (was: Untriaged)
I'll bisect.
Cc: kkaluri@chromium.org
Labels: -Needs-Bisect hasbisect-per-revision M-61
Able to reproduce this issue on Windows 10, Ubuntu 14.04 and Mac 10.12.5 with chrome Stable #59.0.3071.115, Beta #60.0.3112.50, Dev #61.0.3141.7 , Canary #61.0.3152.0

Bisect Info:
===========
Good build : 59.0.3069.0,  Revision Range - 463921
Bad build  : 59.0.3071.0,  Revision Range - 464641

After executing the per-revision bisect script , i got the following CL's between good and bad build versions
===========================================
https://chromium.googlesource.com/chromium/src/+log/24ce4cde5a1d9f21ff63d0560f904dbd2dc46d81..58a80400fbbbddc28a9fb82ca69605e7f520a589

The above CL is redirected to Skia third party roll: https://skia.googlesource.com/skia.git/+log/ac796f880f0a..4ccd862d2940

schenney@- Could you please look into above CL's and assign it to the appropriate dev person for further triage.

Thank You...
Components: -Blink>Paint Internals>Skia
Owner: ----
Status: Untriaged (was: Assigned)
No doubt related to all the changes to local shader matrix.

Comment 6 by hcm@google.com, Jul 11 2017

Owner: mtklein@chromium.org
Status: Assigned (was: Untriaged)
Code author is no longer on our team, over to Mike for ideas on what may be going wrong here.

Sign in to add a comment