W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2010

Re: Notifications

From: Drew Wilson <atwilson@google.com>
Date: Wed, 3 Feb 2010 11:09:53 -0800
Message-ID: <f965ae411002031109x33b5e5ddj50dc4286b454e816@mail.gmail.com>
To: Olli@pettay.fi
Cc: Jeremy Orlow <jorlow@chromium.org>, John Gregg <johnnyg@google.com>, public-webapps <public-webapps@w3.org>
That's true in general about any UI the worker may display (HTTP Auth,
Certificate errors, etc) - the UA generally picks a parent document on
behalf of the worker and displays the UI on the associated screen.

If the client cares about which screen specifically it's displaying on
(because it has parent windows spread across multiple screens?), it can try
to route things back through a specific window itself - providing this API
from worker context does nothing to prevent that and it's a huge convenience
for the overwhelming majority of uses.

-atw

On Wed, Feb 3, 2010 at 10:58 AM, Olli Pettay <Olli.Pettay@helsinki.fi>wrote:

> On 2/3/10 8:55 PM, Jeremy Orlow wrote:
>
>> Agreed.  Having a shared worker that doesn't need to worry about races
>> with shutting down windows seems like a big win.
>>
>> Olli, do you foresee any problems with allowing access from workers?
>>
>
>
> In a multiscreen environment worker can't define which screen to use.
> That seems to be a pretty major problem, IMO.
>
>
> -Olli
>
>
>
Received on Wednesday, 3 February 2010 19:10:22 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:36 GMT