Some comments:
1. "Returns the port for the host page to communicate with the background
task. Null is returned if the task is not started." <-- How do you find out
when the task is started?
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?
3. "In task manager, all active background tasks are also listed and have a
button for the tasks to be ended and removed." <-- Task manager only
provides options to kill a plugin process or a process hosting a collection
of tabs. As is, I'm not sure that it would be a good background task
manager.
4. What happens if a background task calls
window.{alert,prompt,confirm,showModalDialog}?
5. "The background task should detect this and show a notification message
to tell the user to launch a sign-in page." <-- What is the mechanism to
show a notification message?
6. "When there is any fatal error happening during loading or executing the
background task, or the task just crashes or hangs, a notification message
will be shown from the sys-tray icon and the user could clicks on the
message to go to the help page of the host site to find out more
information." <-- This doesn't sound like the right behavior in the case of
crashes or hangs. In the case of a hang, Chrome should probably just kill
the background task if it remains unresponsive for some amount of time. In
that case or if the tab experiences a crash, Chrome should do something like
"Sad tab" to inform the user of the error, giving the user the ability to
restart the background task perhaps?
7. "Incognito support: If a web page is running under incognito mode, it
cannot start any background task. This is because we respect the user's
privacy in this mode and will not permit any "hidden" things to be
performed." <-- Incognito mode tries not to break the web. Maybe it is OK
to allow background tasks from incognito windows provided the incognito
window is still alive. Once the last incognito window closes, then we could
kill all associated background tasks. This way if background tasks are
required by some website, they could still be used when incognito.
8. It feels like background task is just a hidden tab feature. It might be
good if there were UI to force background tasks to be opened as normal
visible tabs. In other words, it seems like background tasks do not need to
be hidden to function. It is just preferred UI to have them hidden by
default.
I have many questions about implementation. I don't see much discussion
about implementation in the design doc, yet it seems from the volume of
changes that you are probably well into the implementation. Can you comment
on your implementation approach?
-Darin
On Tue, Oct 28, 2008 at 4:55 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>wrote:
>
> Hi all,
>
> Here is a draft of a design doc for Background Browser Task:
>
> http://docs.google.com/View?docid=dd6rm2wb_3fmz8pnnp
>
> Your feedback is appreciated.
>
> Thanks,
>
> Jian
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
