I absolutely second this idea. There is a lot of CPU time used by tabs which are running in the background, and your proposal seems to hit target in an attempt to solve that.
About the sounds: I see your point, but an autodetection system wouldn't work for all cases. Sometimes a site plays sound, which you really don't care about when you're not looking at that tab. Further even; I often go completely tut-tut when I open three pages on three tabs, which all play some sound effects in the background. One pitfall I can spot in this; according to the Chrome task manager Flash is one seperate process - which appeared to bshared by all tabs - so I'm not sure if changing the nice-ness of a tab would make any difference. Even though I agree that it probably should make a difference. W. On Nov 3, 9:47 am, Caveman <[email protected]> wrote: > Could be like Safari; Let's say you click "open in new tab" (a youtube > video link). The flash is going to run ONLY when you click the tab (to > see it). > > Your approach goes ahead. I think it's a good idea to decrease/limit > cpu use for Flash/javascript for not viewable windows. --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
