Have you considered how incognito interacts with extensions that have NPAPI
components? It might not be feasible to create a second, isolated instance
of those extensions because the NPAPI component has direct access to system
calls.
I wonder if read-only access to localStorage will be confusing to authors.
I can imagine extensions doing wonky things if they assume they can write
to localStorage. Maybe we should have a separate API for reading
information from the non-incognito localStorage?
Adam
On Wed, Jan 13, 2010 at 2:28 PM, <mpcompl...@chromium.org> wrote:
> I've shared Extensions
> Incognito<http://docs.google.com/Doc?docid=0AbzUSl_g6CjAZGdzZHJnanJfM2RiY3N3dmZz&hl=en&invite=CJ3Si8MG>
> Message from mpcompl...@chromium.org:
>
> Hi all,
>
> I'm working on adding support for running extensions in incognito mode (bug:
> http://code.google.com/p/chromium/issues/detail?id=20175 ). Here is a
> proposal for how it might work. Any and all feedback is welcome.
>
> Click to open:
>
> - Extensions
> Incognito<http://docs.google.com/Doc?docid=0AbzUSl_g6CjAZGdzZHJnanJfM2RiY3N3dmZz&hl=en&invite=CJ3Si8MG>
>
>
> Google Docs makes it easy to create, store and share online documents,
> spreadsheets and presentations.
> [image: Google Docs logo] <http://docs.google.com>
>
> --
> Chromium Developers mailing list: chromium-dev@googlegroups.com
> View archives, change email options, or unsubscribe:
> http://groups.google.com/group/chromium-dev
>
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
