abodenha@ this is a stable blocker for M57. who can look at this issue from the UI side?

I'm not able to repro on 57.0.2987.75 samus.  Can we confirm if this is still happening?

sandeepkumars@ can you please respond to comment #2 above? If this doesn't repro please remove the RBS label.

abodenha@ does this look stable blocking?

Issue is still seen in latest M59: 59.0.3033.0/9347.0.0 dev-channel Paine

Note: Please have the browser NTP in the background before launching the APP launcher

Deleted: Actual launcher.png 23.4 KB

	Actual launcher.png 23.4 KB View Download

+abodenha for review. Doesn't look like RBS to me. Please advise.

warx@ can you look into this?  If we're really losing the dropshadow on the launcher that's really bad.  I'm unable to confirm here tho.

sandeepkumars@ can you confirm if this is seen on all devices or a particular set of devices? If it is the latter, what devices is that?

I can see it on veyron_minnie tot also.

If it is a chrome side issue, then we can bisect in 57.0.2970.0 ~ 57.0.2975.0. I am doing it right now.

The emulator build does show that 57.0.2970.0 is good, and 57.0.2975.0 is bad.

By taking a quick look at the changelists, maybe this CL is related https://codereview.chromium.org/2588103004

+estade for guidance and question: is it the new MD behavior? If so, this bug should be a WontFix.

you can see it on tot? I can't. It should have been fixed by https://crrev.com/3f8c2b4194ebb61b23c8eec97a24a4074f38f136

I should be more specific. I could see #5 effect on tot, but not reporter's actual_launcher.png's effect.

In this issue, there are three figures. I think you mean the third png is the one that we want to ship to users, right? Then tot is all right.

Then I believe this is a WontFix since #12 CL is landed in 57.0.2977.0.

Please test it after 57.0.2977.0.

Thanks Evan.

assign back for #13 comment