summaryrefslogtreecommitdiffstats
path: root/chrome/browser/browser_process_sub_thread.cc
diff options
context:
space:
mode:
authorSteve Block <steveblock@google.com>2010-11-30 11:21:26 +0000
committerSteve Block <steveblock@google.com>2010-11-30 12:09:36 +0000
commitd78db59eb6c4cf1d61ebfc8227347b66950561ff (patch)
tree47d0911be63f53f1dfbc56f350ea6834de6f3533 /chrome/browser/browser_process_sub_thread.cc
parentc2e0a14b0b25e83e3bb0e19c3f06d9513949cc88 (diff)
downloadexternal_chromium-d78db59eb6c4cf1d61ebfc8227347b66950561ff.zip
external_chromium-d78db59eb6c4cf1d61ebfc8227347b66950561ff.tar.gz
external_chromium-d78db59eb6c4cf1d61ebfc8227347b66950561ff.tar.bz2
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
Diffstat (limited to 'chrome/browser/browser_process_sub_thread.cc')
0 files changed, 0 insertions, 0 deletions