History log of /external/chromium/android/autofill/android_url_request_context_getter.cc
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
9c7e521a0bd94b62fffc1b1374dd743e20cd01bd 02-Jun-2011 Kristian Monsen <kristianm@google.com> Merge Chromium at r11.0.672.0: Compile fix in android_url_request_context_getter.*

Typedef removed in this CL:
http://src.chromium.org/viewvc/chrome/trunk/src/net/url_request/url_request_context.h?r1=70592&r2=71522&pathrev=74924

Change-Id: I3ed7374ea725269edd68eae7094e74df37ce7be3
/external/chromium/android/autofill/android_url_request_context_getter.cc
40eae52c5e5dbf475a0cf368c9ccbb7f8a0653f4 17-Dec-2010 Ben Murdoch <benm@google.com> Fix crash in AutoFill

We recently changed WebKit to use one URLRequestContext per WebView.
However AutoFill did not get migrated to the new system and so
we have observed crashes due to a dangling pointer. We have one
AutoFill object per WebView and hence one Profile object per webview.
we access the URLRequestContext through the Profile so inject the
correct context in when the AutoFill object is created.

Needs a change in external/webkit, see
Iace23ae8c0240f0134894c12d2f7281161aa6150

Bug: 3291654

Change-Id: I004ab7ac9c6a72be1b62aa8e44322b97a371c136
/external/chromium/android/autofill/android_url_request_context_getter.cc
d78db59eb6c4cf1d61ebfc8227347b66950561ff 30-Nov-2010 Steve Block <steveblock@google.com> Provide a URLRequestContext directly to AutoFill, rather than a factory function

In b/3044989, AutoFill was modified to take a factory function for the
URLRequestContext (which was then created when needed), rather than
taking the context directly. This was to avoid a race condition where
the context is created before the required storage paths have been
synced to the WebCore thread through the BrowserFrame.

Since https://android-git.corp.google.com/g/76579 and
https://android-git.corp.google.com/g/80056, we read the required
paths directly from JniUtils, so the race condition no longer exists. We
can therefore provide the context directly to AutoFill.

Note that while the context may be created before the Settings have been
synced to the WebCore thread, the necessary properties will be updated
as part of this sync before the context is used.

This change will also simplify things when we use one context per
WebView.

Also requires a change in external/webkit ...
https://android-git.corp.google.com/g/82145

Bug: 3044989
Change-Id: Ie5bf6722783f80e8204f7bedf2cd3334ebb6109f
/external/chromium/android/autofill/android_url_request_context_getter.cc
595099a8c1be642bb6603f1b82669d721fe5d5df 18-Nov-2010 Ben Murdoch <benm@google.com> Merge Chromium at r65505: GetIOMessageLoopProxy now const

http://src.chromium.org/viewvc/chrome?view=rev&revision=63574

Change-Id: I7e81d58e8d3476c135d45610de6a615bf1eee667
/external/chromium/android/autofill/android_url_request_context_getter.cc
75738068e7480a137be1147c03794605c8963ecc 22-Oct-2010 Steve Block <steveblock@google.com> Hide details of private browsing for URLRequestContext from Chromium AutoFill code

Change-Id: I0b9ff8414e3554f65a4d318eff6a47aeff28285b
/external/chromium/android/autofill/android_url_request_context_getter.cc
e58d2d4516094b9cf2637d1312f0c25f75c20599 20-Oct-2010 Steve Block <steveblock@google.com> Fix Chromium HTTP request context getters to use raw pointers

Requires a change to external/webkit ...
https://android-git.corp.google.com/g/75221

Change-Id: I33e86e97acd34d44206418c4cf87c4ffecac0557
/external/chromium/android/autofill/android_url_request_context_getter.cc
2fcbbc66b3616062542ccd46f55d5f4114828042 30-Sep-2010 Steve Block <steveblock@google.com> Update AndroidURLRequestContextGetter to take a pointer to the getter function

This allows users of AndroidURLRequestContextGetter to instantiate a
URLRequestContext lazilly.

When used in AutoFill++, this means that when the URLRequestContext is
first initialized, the WebCore thread is set-up and the necessary
settings are available.

The corresponding WebKit change is
https://android-git.corp.google.com/g/71269

Bug: 3044989
Change-Id: I8627d6ea1cdf84ce415319718b54b485ea2cca77
/external/chromium/android/autofill/android_url_request_context_getter.cc
7d214dfa174224b459660971e5b5cce2e06be02a 06-Aug-2010 Ben Murdoch <benm@google.com> Intial set of changes to enable autofill on Android.

This is the initial checkin of AutoFill code into external/chromium.
There's still lots to do, but this basically gets autofill working
end to end, using a precanned profile injected from WebCore. By
default, autofill is not enabled at the moment. For testing you can
turn it on by setting the ENABLE_AUTOFILL environment variable to
"true" and rebuilding.

There is a corresponding change in external/webkit.

Change-Id: I74ef1ccc3fd0625f1bb8e2f85b43a60d23c59ffc
/external/chromium/android/autofill/android_url_request_context_getter.cc