It's better to be non-animated. Remember,ichrome is using too much CPU already. Second; the user is doing something, he doesn't want to be distracted with information unrelated to his current task. If the user finds himself waiting on his current tab, his eyes will probably see a tab being slightly "burnt" and will wonder what is happening. :)
M-A On Wed, Oct 7, 2009 at 1:13 PM, Darin Fisher <[email protected]> wrote: > http://tinderbox.mozilla.org/1afi003r.gif > > On Wed, Oct 7, 2009 at 10:10 AM, Glen Murphy <[email protected]> wrote: >> >> Something like yes! Maybe not a dialog, as I use things that peg my >> CPU (games) somewhat frequently. >> >> One idea we toyed with was marking such tabs as 'on fire' (icon or >> color), so at least there was a visual indication. I think this would >> be a good starting point before anything more obtrusive like a dialog >> or bar. >> >> >> On Wed, Oct 7, 2009 at 9:59 AM, Paweł Hajdan Jr. >> <[email protected]> wrote: >> > Just a while before one of my tabs (GMail) started using a lot of CPU >> > time >> > (67% while I was compiling in the background). The browser and the >> > system >> > were responsive at all times, but processing power was wasted. >> > We have a warning dialog for hanged renderers offering to kill them. >> > What do >> > you think about a warning dialog for renderers consistently using a lot >> > of >> > CPU? >> > > >> > >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
