Hi, I'd like to add couple of bits, perhaps it'll help to explain it from another angle:
> > 2. "When there is any background task running and all Chrome windows are >> > > closed, Chrome will put up a systray icon to indicate that there are some >> > number of background tasks being running. When the user clicks the >> systray >> > icon, Chrome will be launched with the background tab opened." <-- What >> is >> > the background tab? >> >> I forgot to remove background tab from the latest design doc. I will >> remove it and replace with "launch the task manager". >> > > Hmm... the idea of background tasks being representable as real tabs seemed > appealing to me. To the application, why should it matter how the > "background task" is rendered? To the user, it could be a powerful feature > to be able to "expose the window of background tasks" as a normal browser > window where each background task is represented by a normal tab. You could > even have a user option to "minimize a tab to the systray" which would just > cause it to become a background task / tab. > That is true (tasks do not have to be hidden). This is what we thought a "background task tab" could be used for - something like 'new tab' page but instead of previously visited pages it could have view of currently running background tasks (perhaps even live), with some sort of stats (CPU/ram/etc). Clicking on a task in that tab could even open it in a normal tab. Closing the normal tab would make it hidden again. Having ability to see the background task UI could be very valuable for development and diagnostics. Dmitry --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
