packages_apps_Browser.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Implement client-side incognito mode	Ricardo Cerqueira	2015-11-07	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Since WebView deprecated privateBrowsing in API 17 (and killed it for good in API 19), we were left without incognito in the Browser app. Follow the docs' recommendations and implement it with "manual" control of privacy-related engine options * Internally track incognito state for tabs * Disable all forms of storage and cache on private webviews * Disable all cookie activity while an incognito tab is active * Stop trying to use the deprecated "privateBrowsing" argument when creating webViews, always set to false Change-Id: I23f2e34ee125635bba8981f0711ba4986a9beaab
*	Accept third party cookies if cookie setting is enabled by user	Tao Bai	2014-09-12	1	-0/+4
\| \| \| \| \|	BUG:17474704 Change-Id: I8f9f17887cf65c1c5465b576dcf094784266b15b
*	Update Browser to use TEXT_AUTOSIZING	Jonathan Dixon	2013-10-24	1	-2/+4
\| \| \| \| \| \| \|	Also enable Web Debugging conditionally based on the platform OS level (to document the best-practice, as much as anything else) Change-Id: Ib89c6e6250370c520ad0c571e6e5a166369f1f40
*	Make web contents debugging always enabled (as in Chrome)	Mikhail Naganov	2013-09-23	1	-0/+3
\| \| \| \| \| \|	Bug: 8691809 Change-Id: Icef9d796a99f3dbca2a4568d2f71e70bc6e91dd7
*	Remove slow, yet no-op call	John Reck	2011-08-17	1	-1/+0
\| \| \| \| \| \| \| \|	Bug: 5178457 It is slow because it forces initialization of the TilesManager, yet the value set is ignored by TilesManager anyway. So remove it. Change-Id: I0fc8a98340742fedfd27495da8fcd7a7c2a32fc0
*	b/5080166 support multi-touch on external touchscreen.	Huahui Wu	2011-07-26	1	-2/+4
\| \| \| \|	Change-Id: I4a9b747a1c3c4f98268dc735e800c9c509d5d392
*	Preloading support in browser	Michael Kolb	2011-06-30	1	-0/+69
	Apps like the QSB can request the browser to preload a web page. - preloaded pages are not added to the browser history if they'r not seen by the user - when a request is received, a new tab is created for the preloaded page, but not added to the tab list - upon receiving the view intent for the preloaded page the tab is added to the tab list, and shown - if several pages are preloaded consecutively in the same tab, the back stack is cleared before it is displayed - preloaded pages use the main browser cookie jar, so pages that have never been viewed by the user can drop cookies Change-Id: I9ed21f2c9560fda0ed042b460b73bb33988a2e8a