packages_apps_Browser/src/com/android/browser/AutofillHandler.java, branch replicant-6.0 packages/apps/browser De-classicify Android Browser part 2 2013-08-26T03:07:02+00:00 Jonathan Dixon joth@google.com 2013-08-26T02:35:27+00:00 f9e1705d4012706664a2bdf63a50b8a784b833dd Bug: 10427705 Allows Browser to compile even when WebViewClassic is no longer in frameworks/base. The deleted functionality was already disabled at runtime when using non-classic webview. Change-Id: I21b58ec52ac059c699b49a2dd80008d9a9e6791a 
Bug: 10427705

Allows Browser to compile even when WebViewClassic is no longer in
frameworks/base. The deleted functionality was already disabled at
runtime when using non-classic webview.

Change-Id: I21b58ec52ac059c699b49a2dd80008d9a9e6791a
Don't wait on ContactsProvider 2012-05-16T17:05:38+00:00 Ben Murdoch benm@google.com 2012-05-14T15:39:50+00:00 234eadcf7d0dbf2d24f92c24f40343d518f6fe3a Right now during the initial WebSettings sync to native we wait for the autofill profile to be loaded from disk so that it can be synced. If there's no profile set, then we try to infer a profile from the user's Me contact profile. Querying the Me contact can be slow and in some extreme cases can cause the settings sync on the UI thread to block long enough to show an ANR. Instead signal the threads (via the CountdownLatch) waiting on the initial import before we do the Me profile lookup. Note that we still may block the UI thread if the lookup of an already saved profile takes an exceptionally long time. This is so that when a user has saved a profile, we'll never resort to showing them the "setup autofill" message. (But all ANR reports to date have shown that we were querying the Me contact at the time of ANR). Bug: 6371781 Change-Id: Ibb0d5e285ec3587d9f9bad3e69b79890850c2f6d 
Right now during the initial WebSettings sync to native we wait
for the autofill profile to be loaded from disk so that it can
be synced. If there's no profile set, then we try to infer a
profile from the user's Me contact profile. Querying the Me
contact can be slow and in some extreme cases can cause the
settings sync on the UI thread to block long enough to show
an ANR.

Instead signal the threads (via the CountdownLatch) waiting on
the initial import before we do the Me profile lookup. Note that
we still may block the UI thread if the lookup of an already saved
profile takes an exceptionally long time. This is so that when a
user has saved a profile, we'll never resort to showing them the
"setup autofill" message. (But all ANR reports to date have shown
that we were querying the Me contact at the time of ANR).

Bug: 6371781
Change-Id: Ibb0d5e285ec3587d9f9bad3e69b79890850c2f6d
Fixup browser to use WebView proxy 2012-03-02T11:18:30+00:00 Jonathan Dixon joth@google.com 2012-02-24T00:13:06+00:00 4d2fcaba7fb8eb1723943ac9a10e76d509330bd1 Has to escape out to WebViewClassic whenever it needs a hidden API. Interdepends on https://android-git.corp.google.com/g/165608 Change-Id: Ic61dd7f57f75381864075605d5901f2688648cbd 
Has to escape out to WebViewClassic whenever it needs a hidden API.

Interdepends on https://android-git.corp.google.com/g/165608

Change-Id: Ic61dd7f57f75381864075605d5901f2688648cbd
Fix NPE when pre-populating Autofill data. 2012-02-23T11:18:00+00:00 Ben Murdoch benm@google.com 2012-02-23T11:18:00+00:00 7458d4cbde2e5e49503d6e87924930d381b7ad89 If the user has no me profile, bail out to avoid a NPE. Bug: 5869116 Change-Id: I80701d4563f394879917b6242ace7b2bae584fb2 
If the user has no me profile, bail out to avoid a NPE.

Bug: 5869116
Change-Id: I80701d4563f394879917b6242ace7b2bae584fb2
Prepopulate the users autofill text. 2011-10-28T11:57:01+00:00 Ben Murdoch benm@google.com 2011-10-27T17:04:58+00:00 3d6c719b6c85d879c1c3fdc6ac902c3c9fa0a5b3 When the browser starts, if autofill is on and no profile is already set up, try to read the user's "me" contact and prepopulate their profile with what we can get. Bug: 5427308 Change-Id: I23e0369f64b2b69763d1934f7ed6b2ece9cca282 
When the browser starts, if autofill is on and no profile
is already set up, try to read the user's "me" contact and
prepopulate their profile with what we can get.

Bug: 5427308
Change-Id: I23e0369f64b2b69763d1934f7ed6b2ece9cca282
Cache the application context instead of Activity. 2011-08-01T15:17:37+00:00 Ben Murdoch benm@google.com 2011-08-01T12:58:47+00:00 914c5591baeb86bf30a5bc28930071442a822d60 When storing a reference to a Context, ensure that it's the Application context rather than Activity Context. Bug: 5084293 Change-Id: Ib0be5f8ceb91846bb985d0813a8f22cabd44eaf8 
When storing a reference to a Context, ensure that it's the
Application context rather than Activity Context.

Bug: 5084293

Change-Id: Ib0be5f8ceb91846bb985d0813a8f22cabd44eaf8
Fix AutoFill 2011-05-06T17:33:16+00:00 John Reck jreck@google.com 2011-05-06T17:33:16+00:00 72d77529cc146e2eb8e36247d448e416b56c865d Ensure that we sync the new profile data to WebSettings so that it will get sent to native land. Change-Id: I825557d9c73e218f0056f6bfd1d3b726ca9f6eef 
Ensure that we sync the new profile data to WebSettings so that
it will get sent to native land.

Change-Id: I825557d9c73e218f0056f6bfd1d3b726ca9f6eef
Fix race condition 2011-04-26T20:50:11+00:00 John Reck jreck@google.com 2011-04-26T20:48:09+00:00 7b06c907aa31c38069ec2718bd4a388f1f801e6f Change-Id: I567e9d987dbd85551d51b34612b542e9694b83e1 
Change-Id: I567e9d987dbd85551d51b34612b542e9694b83e1
Browser settings refactor 2011-04-26T20:03:32+00:00 John Reck jreck@google.com 2011-04-25T16:01:54+00:00 35e9dd6283a2d65687104eb0b3a459c02dcb150b Change-Id: I6fc1b21f7ea692fbe37a17bf900e9b7408a9c077 
Change-Id: I6fc1b21f7ea692fbe37a17bf900e9b7408a9c077