Fix exception in Browser Settings

Bug 11302175

Need to implement isValidFragment when targeting >= KK

Change-Id: I19cc285aa237ffd9001558a9ee6adaf152acd1df
Fix exception in Browser Settings

Bug 11302175

Need to implement isValidFragment when targeting >= KK

Change-Id: I19cc285aa237ffd9001558a9ee6adaf152acd1df
Add back browser history page.

Not sure why it was removed, but it seems to work just fine.

Change-Id: I6d76928182a53ca57d080394823d35d66e0ba987
disable incognito mode for now due of missing support

in webchromium.....currently it throws for KiKat API and higher
illegal exception and is not nativly supported

Change-Id: I74982bd457ebf70939247a7685abad89973c92d6
Merge tag 'android-4.4.2_r1' into HEAD

Android 4.4.2 Release 1
Set slimroms.net as default home page for browser

PS 2 : Fix derp

Change-Id: Ie3423aeaec59822b95e822ecd6c9f3dd411f4a97
Add Website Settings as valid fragment

Fixes FC in Settings > Advanced > Website settings

Change-Id: I365bf1d7f95674171f7214fe16eeecd344ec260a
Remove Incognito mode from quick controls since it no longer exists in the browser

Change-Id: I7581c486b47d2bc60b884fb686f04dc3ef514c27
Browser: Fix browser force close

Issue: Cursor was accessed by handler thread
       when it was closed. During Orientation change,
       BrowserBookmarksPage#onDestroyView is called
       which clears all the loaders [and cursors].
       Simultaneously ThreadedCursorAdapter#loadRowObject
       is getting called which then calls
       BrowserBookmarksAdapter#getRowObject
       where closed cursor is accessed and force close happens.

Fix: Synchronized cursors wrt main thread and handler thread.
     Checked mCursorAdapter for invalid conditions

CRs-Fixed: 576176
Change-Id: I9f16c2f1a55f35e8256bbf56afce3538850f9d42
Revert "Remove Incognito mode from quick controls since it no longer exists in the browser"

This reverts commit a2c4940fd5cf02bc97721bda8739df356baf0c83.

Change-Id: Ie66e3116477fc1a490c31cb6e810343909c9b217
Revert "disable incognito mode for now due of missing support"

This reverts commit ba23cb02b0f49c3f5650bfde2796066f0e7adf8f.

Change-Id: I25d91b14d1d97dcded26904454dda1d04aae497d
Implement client-side incognito mode

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
Show a startup page in incognito mode

Change-Id: Ib1d4be6890c81b73a46f026b6fcbb2f1e8de567d
blue to grey browser's progress bar

Change-Id: I7cabb70f84cd4f6c65a1c8b197831dad822498fa
Fix the problem that the favicons on the history page are shown ramdomly when the page is scrolled.

Steps to reproduce:
1. Visit some URLs to fill the history page.
2. Go to the history page.
3. Scroll up and down repeatedly.

What happened:
The favicons on the left side of the history page are shown ramdomly.

Change-Id: I243ec67899b13c5482e1503f7eab23dd9a5aa1f5
Signed-off-by: Sungmann Cho <sungmann.cho@navercorp.com>
fix browser blue textfield

Change-Id: I6f7fb8b0ff61d4d9d78a8580450f7d299c41d449
BrowserSettings: update desktop UA string to match Chrome 30

Now that we're using a Chromium-based WebView which closely matches
Chrome 30, we should report as a newer Chrome version when masquerading
as a desktop browser.

Change-Id: I301a8cfac9a83e66a6749872943e80ff5c4740a1
Replace removed NARROW_COLUMNS layout mode with TEXT_AUTOSIZING

For reasons which I completely fail to understand, Google elected not to
implement the very useful NARROW_COLUMNS layout mode (double-tap to
reflow text) in Chromium WebView, and instead chose to implement
TEXT_AUTOSIZING (buggy heuristic-based font inflation).  But complaining
isn't going to get it back, and font inflation is better than nothing on
small screens, so replace NARROW_COLUMNS with TEXT_AUTOSIZING to restore
some support for resizing text to be legible on screen.

Change-Id: Ieeb03d38e8a7386e8e8f811c570aa17bfabf4337
Reimplement titlebar autohiding to be compatible with chromium webview.

Patch Set 4: Fix code formatting

Change-Id: I4de873f7c089d4f7dede944d05f48d03000f3d99
Browser: Fix Progress bar when quick Controls Enabled

The quick controls progress bar was broken by my browser autohide patch.
This patch fixes it to properly show again.

Change-Id: I1062c4eac26bbc87ca6ec9de775e0b1b58d0542b