Odd behavior with Carousel when Win Chrome browser tab is inactive

[skibulk]

I'm using the built in JS carousel a rotating header on my site. The problem occurs while using tabs in the latest version of Chrome.

First open a page with a carousel on it. Then open a new tab (same window). After a few slides would have gone by, switch back to the carousel. The current slide/next slide transition should be broken for one iteration. For example, the current slide image isn't shown until the next slide takes its place. Also the transition times seem to be off. After the one broken iteration, the carousel works as normal.

Maybe this is something that Chrome is doing to save CPU?

[cvrebert]

What OS are you using?

[skibulk]

Win 7 x64

[cvrebert]

Just for the record, I can't seem to repro on Mac Chrome.

[cvrebert]

@XhmikosR Could you try to repro this?

[XhmikosR]

I can't seem to reproduce either on the /components page.

[cvrebert]

@juthilo @hnrch02 Mind giving this a try on Windows?

[juthilo]

I should be able to check this out later today, sure

[dhampik]

Can reproduce it on http://getbootstrap.com/javascript/#carousel
Ubuntu 14.10 x64 Google Chrome 39.0.2171.95 (64-bit)

[cvrebert]

@juthilo Any luck?

[juthilo]

Sorry for the delay. I can reproduce on Windows 8.1 using Chrome 39.2171.95.

[cvrebert]

@juthilo Could you file a Chromium bug?

Only workaround I can think of would be to make use of the Page Visibility API to stop the carousel when the tab isn't visible and hope that that would avoid/minimize the problem.

[cvrebert]

Made a POC for using the visibility API. @juthilo Does the bug repro on http://jsbin.com/yigazi/3 ? (Fingers-crossed that it doesn't..)

[juthilo]

@cvrebert 👍 Can't reproduce using your JS Bin. I did a direct comparison of the live docs and your Bin to be sure.

I'll file the Chromium bug later today.

[cvrebert]

Cool! Thanks 😄

[juthilo]

Et voilà, the Chromium issue: https://code.google.com/p/chromium/issues/detail?id=449180

[cvrebert]

Closing as a bug in the browser itself that we can't directly address.
#15566 would have offered an indirect workaround, but has been punted to Bootstrap v4.