We had a lot of regressions in 49. Is there an easy way to test this in dev?

I'd have to put Dev on my Pixel, which is a bit of a pain.

This very much looks like a compositing bug, given that no repaints happen (paint rect flashing demonstrates this), and cc continues to show the debug borders for these quads.

(And I think the bugs you're talking about were Blink paint invalidation bugs.)

Could this be the same as  issue 600805  (which occurs w/out a Cast session
active)?

Not sure.

Here's the recording I promised (Googlers only); I had to re-record it. You can see that invalidations work fine while the page is focused. While another tab is in the foreground, however, some things disappear. When I make another tab draw frames (by scrolling, by watching video, etc.), those elements flicker in and out in the background tab that is being cast.

https://drive.google.com/a/google.com/file/d/0BwPS_JpKyELWTk1XNFRWdXR5YXc/view

@btolsch is this something you could take a look at? Seems like it might be related to Media Router.

The repro steps detail using the legacy Cast extension, not media router.

Has this happened again recently (since Chrome 51 or even 50 went stable)?

Is it possible to cast into a meeting using media router? I've only done it with the extension.

We are working on enabling cloud services (including Hangouts meetings) starting with media router as of Chrome 51 (specific domains whitelisted) and plan on a full launch in Chrome 52.

51 is currently stable; does that mean this is already available?

On 52.0.2743.57 beta, I can't reproduce the original issue, but only because the tab casting video freezes entirely when I switch to another tab (and doesn't even resume if I switch back!).

Aside: I don't even seem to be able to access the legacy cast extension anymore now that I'm on 52 beta, which makes this a pretty hefty regression in functionality for me.

The video freezing on tab switch kind of sounds like crbug.com/622736, but that was for full screen content and only seen on m53 before, not m52.  Please comment there if you can repro reliably on m52 and the scenario matches what you are seeing.

Note that you can disable media router (at least until the experiment is removed from Chrome, probably around m55 or so) by turning off the media router flag: chrome://flags#ennable-media-router

You will need to re-enable or re-install the legacy Cast extension after that.

Thanks for the tip that MR can still be turned off. I can't reproduce my tab-freezing thing today, but it was reliable on the day that it happened. :/ Sorry that isn't particularly helpful.

I couldn't repro this with 57.0.2987.75 on the Pixel. 

Closing as not reproducible. jbroman@ please re-open if you see this again. Thanks!