CODEWITHSUNDEEP
javascriptgoogle-chromegoogle-chrome-app
xd1936
xd1936

Reputation: 1180

chrome.app.window.create Incognito Window?

I'm working on a Chrome app, and was wondering how to create a fullscreen Incognito window.

function openWindow(path){
  chrome.system.display.getInfo(function(d){
    chrome.app.window.create(path, {
      'frame': 'none',
      'id': 'browser',
      'bounds':{
         'left':0,
         'top':0,
         'width':d[0].bounds.width,
         'height':d[0].bounds.height
       }
    },function(w){
      w.fullscreen();
    });
  });
}

This creates a regular window. Adding

'incognito': true,

didn't work.

Upvotes: 0

Views: 589

Answers (2)

Xan
Xan

Reputation: 77523

A "browser" inside the <webview> tag is stateful, but the state is not persistent unless you specify a partition attribute.

If you don't specify a partition, the state (cookies, localStorage, etc.) is lost when the element is destroyed, e.g. on an app window restart. It does, however, survive as long as the <webview> element lives.

Furthermore, at any point you can wipe any part of the state as you would do with Chrome, via <webview>.clearData() function. In a public kiosk mode, it's probably a good idea to do this if the app was inactive for a period or the user explicitly indicates he finished browsing.

Upvotes: 0

Marc Rochkind
Marc Rochkind

Reputation: 3740

To echo one of Xan's comments above, Chrome App windows are not browser windows. As they have no cookies or history of any kind, they are inherently incognito. Caching is for performance, so the HTML processor probably does caching, but I would think that caching isn't much of a privacy issue.

Upvotes: 1

Related Questions