Two things I wanted to start working on in GeckoView: 1. Private browsing support 2. Disabling history in a browser
Private browsing support would mean a GeckoView.Browser widget would act like a Private Browsing tab in Firefox. What does Private Browsing not save? * Visited pages: No pages will be added to the list of sites in the history database. * Form entries: Nothing you enter into text boxes on web pages will be saved for form autocomplete. * Passwords: No new passwords will be saved. * Cookies: Cookies store information about websites you visit such as site preferences, login status, and data used by plugins. * Cached Web Content and Offline Web Content and User Data: No temporary Internet files (cached files) or files that websites save for offline use will be saved. Disabling history is a subset of this feature, but is still useful on it's own. If you have a GeckoView used to display local HTML content, there is likely no need to waste time and storage saving the history. Proposed API changes: public final int BROWSER_DEFAULT = 0; public final int BROWSER_PRIVATE = 1; public final int BROWSER_NOHISTORY = 2; GeckoView.addBrowser(String url, int flags) We can keep the existing addBrowser(String) API and just have it call addBrowser(String, int) with BROWSER_DEFAULT for the flag. Is there value in that? Currently, GeckoView does not give developers a way to control how history is saved. We can look into creating a ChromeDelegate API for passing control to the GeckoView application. Thoughts? Finkle
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
