Good point about leaving something running behind. We are still working on a opt-in mechanism which can provide a better optional education (install wizard-like with "learn more..." link for example).
Also, we will have a systray icon with a menu that allows killing those items (and killing likely means eradication, so it doesn't start unless 'installed' next time). Background tasks are also going to be visible in the Chrome's Task Manager. We also discussed a possibility, when user closes the browser and there is running background task, to do an animation a-la "genie effect" of the browser window into the systray icon to illustrate that the browser did not close completely. User can click the icon to observe whats' running and perhaps choose "kill all" option. Dmitry On Thu, Nov 6, 2008 at 11:28 PM, Simon B. <[EMAIL PROTECTED]> wrote: > > > > ... > > > When the background task is allowed to start, it will continue to run > > > even when the browser is exited. Next time when the system is started > > > and the user logs in, the background task will run automatically > > > without any re-authorization since the permission has already been > > > granted last time. > > > > Is this spelled out anywhere? E.g. it's not exactly natural for something > > tied to your browser to keep running after you close your browser. I fear > > this may be quite un-expected for users. How does a user know that their > > notification will keep running after they close the browser? > > In my mock-up [1] the first notification asks the user: > " (icon) www.calendardemo.net > will be able to notify you. > will be always on > Allow / Cancel" > > This notification should show that it originates from the tray icon > (*). That way, as long as the tray icon stays it should be quite clear > what "always-on" means? > For this purpose it is important that the tray icon always stays in > the tray area while background tasks are running, i.e. not appear only > when Chrome is closed like it has been suggested. > > (The word "always-on" could be maybe be explained with tooltips or by > clicking the word in the notification. Also "able to notify you" could > benefit from some more explanation.) > > (*) ideas how to show that: maybe by animating the tray icon when > notifications appear and when they close, or make the notification > bubble into a cartoon speech bubble originating from the tray icon > > > How do they stop that if they want? Does "end task" correspond to > "revoke my permission > > to run this notification and don't launch it again" or does it mean "just > > stop it now, but it may re-start at any time"? > > There are rumoured settings, either user-wide or per background task, > about whether to allow tasks to run before and after the normally > visible browser. > The easiest would be to simply let the user decide if they can spare > (want to pay for) CPU and bandwidth also when the browser is closed. > If done well, that could limit the amount of misunderstandings (and > complaints) about Chrome "not closing properly". > > [1] http://sites.google.com/site/chromiumdev/notifications > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
