On Jul 14, 12:23 pm, Jim Roskind <j...@chromium.org> wrote: > I tend to think incognito mode as a personal (and very private) decision. > As a result, I'd tend to prefer that it be very difficult to leak such > status further than absolutely necessary.
Any web page that wishes can determine if you are (likely) in Incognito Mode: http://jeremiahgrossman.blogspot.com/2009/03/detecting-private-browsing-mode.html It's not something that these modes try and prevent - they are all about not leaving tracks on the client. Cheers Chris > Allowing your proxy provider to > detect this status seems like a violation of the "need to know," but perhaps > that because I see a proxy provider as an ISP in the common case. If I > thought I could "trust" my proxy provider, perhaps I'd be more open about > this status. > ...but perhaps that was not the best example of your need for the API > access?? > > Jim > > > > On Tue, Jul 14, 2009 at 11:35 AM, Peter <peter.j.obr...@gmail.com> wrote: > > > Can someone explain the scope of javascript calls available within PAC > > files that chrome parses? > > > What I'm getting at is, can we use the chrome api javascript calls > > within PAC files? > > > Why would you want/need this? First thought is to determine if the > > browser is in incognito mode or not, but there may be other > > applications. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
