W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2009

[whatwg] Security risks of persistent background content (Re: Installed Apps)

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 29 Jul 2009 17:15:09 -0500
Message-ID: <dd0fbad0907291515l1d80cd54j82e876da9bfa74a4@mail.gmail.com>
On Wed, Jul 29, 2009 at 5:05 PM, Robert O'Callahan<robert at ocallahan.org> wrote:
> What happened to my idea for browsers to have a special window containing
> tabs for "background apps", which save screen real estate by just showing an
> icon and title (and a URL or domain?) and no actual tab content? You might
> modify the UI so that quitting the normal browser leaves this window open,
> possibly as a separate OS app. Seems to me that this would provide almost
> exactly the desired functionality but without introducing new security
> concerns and without requiring a trust decision.

I think I didn't understand what you were talking about the first time through!

How does inter-tab (inter-process) communication work here, then?
Except for the persistence issue, we already have specced methods for
handling this sort of thing, and it seems like it would be best to
solve any communication/manipulation issues there first, then tack on
something to help persist things.

Also: would these pages be regenerated automatically when the browser
is reopened?

~TJ
Received on Wednesday, 29 July 2009 15:15:09 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:14 UTC