Bug 58982 – box-shadow glitch on hover with -webkit-transition

• Status: RESOLVED
• Resolution: FIXED
• Component: CSS

[Husar]

If you have an HTML element with multiple box-shadows that should get a change in the box-shadow values after a hover with -webkit-transition there is a noticeable glitch in the shadows rendering.  

Tho replicate:
Create an element (<div>) with the following styles:

div {
	width:220px;
        background-color:#DDD;
	border:1px solid #857A6D;
	border-left:1px solid #C5BEB8;
	border-top:1px solid #C5BEB8;
	padding:30px 30px 60px;
	border-radius:8px;
       -webkit-transition: all .4s ease-in-out;	
       -webkit-box-shadow: inset 4px 4px 4px rgba(245, 245, 245, 0.8), 
		inset 0 3px 15px rgba(0, 0, 0, 0.1); 
       	box-shadow: inset 4px 4px 4px rgba(245, 245, 245, 0.8), 
		inset 0 3px 15px rgba(0, 0, 0, 0.1);
}

div:hover {
	-webkit-box-shadow: inset 4px 4px 4px rgba(245, 245, 245, 0.8), 
		inset 0 3px 15px rgba(0, 0, 0, 0.1),
		4px 4px 6px rgba(166, 153, 140, 0.7), 
		-3px -3px 6px rgba(166, 153, 140, 0.7);
	box-shadow: inset 4px 4px 4px rgba(245, 245, 245, 0.8), 
		inset 0 3px 15px rgba(0, 0, 0, 0.1),
		4px 4px 6px rgba(166, 153, 140, 0.5), 
		-2px -2px 6px rgba(166, 153, 140, 0.5);
}

[Husar]

*** Bug 58980 has been marked as a duplicate of this bug. ***

[Joel A Glovier]

I too have experienced this bug, and there is an example in the h1 on this page I built: http://cure.org/goh

Also posted about it on StackOverflow here: http://stackoverflow.com/questions/3942971/webkit-choking-on-rendering-multiple-text-shadow-box-shadow-values-with-webkit

[Joel A Glovier]

Created attachment 92304 [details]
The h1 on this page has multiple box-shadows and on hover they render awkwardly, one after another

[Joel A Glovier]

Just noticed that the current build of Chrome (Chrome version 10.0.648.205) resolves the bug in how it renders the double shadow transition. Safar, however, as of version 5.0.5 (6533.21.1), still displays the bug.

[Shane Stephens]

Confirm that this is fixed in Chrome 11 and Canary.  I'm marking this as fixed as it looks to have been resolved in WebKit.

[Joel A Glovier]

(In reply to comment #5)
> Confirm that this is fixed in Chrome 11 and Canary.  I'm marking this as fixed as it looks to have been resolved in WebKit.

Did you see that Safari still displays with the bug?

[Shane Stephens]

WebKit nightly renders the transition correctly.  The issue is fixed in WebKit but will obviously take some time to roll out into a production version of Safari.