summaryrefslogtreecommitdiff
path: root/core/java/android/webkit/WebViewDatabase.java
Commit message (Collapse)AuthorAgeFilesLines
* WebView: deprecate accidentally-exposed constructorsNate Fischer2018-09-251-0/+8
| | | | | | | | | | | | | | This deprecates public-exposed constructors. These constructors were exposed by accident. These classes shouldn't be instantiated by applications, but should only be instantiated by WebView. In some cases, the app should get a singleton instance using a #getInstance method. In these cases, we document this explicitly in the deprecation note. Bug: 110807530 Test: make docs, manually verify docs look good. Change-Id: Ibe73b3399c9ced0cf4fbb01e1df13564476df252
* WebView: add @Nullable and @NonNull annotationsNate Fischer2017-09-211-0/+2
| | | | | | | | | | | | | | | | | This adds @Nullable and @NonNull annotations where the docs previously stated this. This change should be safe, since we already disallowed null values for the @NonNull parameters via documentation. I verified that documentation changes for APIs which previously did not mention null-ness in @param or @return Javadocs (if the API already mentioned it in these spots, then DroidDoc prefers the hand-written description). This also fixes various lint errors. Bug: 65465498 Test: make update-api and manually verify docs Change-Id: I4751508d0e72be8ddfc3d6b601db8c307c9df60e
* WebView: wrap Java literals with {@code}Nate Fischer2017-09-051-2/+2
| | | | | | | | | | | | | | | | Docs change only. This wraps some Java literals (true, false, null) with {@code} blocks, as per Android API guidelines. This also addresses other presubmit errors: * fix lines that have become too long * fix broken import order and unused imports Bug: 65213517 Test: make docs (and manually verify things look better) Change-Id: Idc7fe28d40bea7bd1edcad539b75fa9c689b8d46
* Disable WebView autocomplete feature.Selim Gurun2017-04-041-0/+2
| | | | | | | | | | Platform is now providing autofill feature. Disable WebView's simple form data save feature for platform O and above. Test: Removing the functionality and the test Bug: 36869838 Change-Id: If6b9fc12edbe4146fca99d9c6ef8fde36d61f852
* Deprecate WebView#{get,set}HttpAuthUsernamePasswordNate Fischer2016-09-261-4/+52
| | | | | | | | Deprecate these methods and move them to WebViewDatabase. BUG: 31318603 Test: N/A Change-Id: Ie4613e8de9c6120fa1d21263b15ef2467c6ccdef
* Fix WebViewDatabase javadoc.Hui Shu2016-09-061-2/+11
| | | | | BUG=30481165 Change-Id: Ibd14880aa25907234dd93c38b5d0f2c9e808340e
* Remove unused imports in frameworks/base.John Spurlock2015-02-281-1/+0
| | | | Change-Id: I031443de83f93eb57a98863001826671b18f3b17
* [WebView] Allow the WebView to be compiled against the system SDK.Ignacio Solla2014-11-121-25/+8
| | | | | BUG:18152150 Change-Id: Ifd6dcac17663631058d895c61bb6e8018c5aeecc
* Deprectate WebViewDatabase password methods.Ben Murdoch2013-04-111-1/+5
| | | | | Bug: 8593749 Change-Id: I3d87fa43731a275af95f00933a5439d17a16ae80
* Fix broken JavaDocJonathan Dixon2012-11-301-10/+10
| | | | Change-Id: I1e6d595f0fcd1a816ed39aaa801f7d451eb39f85
* Use less static synchronizedJohn Reck2012-09-201-1/+1
| | | | | | Bug: 6482144 Change-Id: I86161e3298101c10a112add406615001561e649e
* Hiding some of the deprecated android.webkit API'sKristian Monsen2012-09-071-1/+3
| | | | Change-Id: I1775a2ff615d1633fe9a20a5af49623222d3d27b
* Improve JavaDoc for HTTP basic authentication methodsSteve Block2012-07-231-3/+10
| | | | | | Bug: 5461416 Change-Id: Ie3bfbf6acde34ea184aa8c8b1d3841e2a2aa8a22
* Improve JavaDoc for saved form dataSteve Block2012-07-231-3/+6
| | | | Change-Id: I962df5678081920c30f8a2b1fe79389f702ef3fb
* Improve JavaDoc for saved username/password pairsSteve Block2012-07-231-6/+11
| | | | Change-Id: Ief079666eb1250f0a57089c778669b638a259194
* Create WebViewDatabaseClassic from WebViewDatabase.Ben Murdoch2012-04-261-564/+32
| | | | | | | | | | | | WebViewDatabase has a getInstance() method, so similarly to WebStorage, WebIconDatabase etc we refactor it into a proxy class, and move the current implementation into WebViewDatabaseClassic. Also clean up some JavaDoc in touched files. Bug: 6234236 Change-Id: I71cbd8f78e60f396e96e8546073ad634797cce15
* Do not enable WAL mode for the WebView database.Jeff Brown2012-03-221-6/+0
| | | | | | | | | | | | | | | | | There is no need to enable WAL for the WebView database because it does not require high throughput. Enabling WAL increases memory usage and can also cause problems if the same database is opened in multiple processes, which can happen if an application has UI code running in multiple processes. Normally, we would use a content provider to ensure that the database is only opened within one process (and then accessed remotely view RPC), but we can't do that for WebView because it is part of the framework. Deleted the call to setLockingEnabled. It does nothing. Bug: 6124556 Change-Id: Ic397c74872fe6b1246da0c859eab0d5147045c86
* Drop support for Android HTTP stackSteve Block2012-02-221-634/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | All future releases will use the Chromium HTTP stack and maintaining two HTTP stacks adds maintenance overhead. The Chromium HTTP stack requires V8, but we now use V8 in all build targets (b/5495373), so we can safely drop the Android HTTP stack. LoadListener, HttpAuthHandlerImpl, Network, SslErrorHandlerImpl, WebViewWorker - Android-stack specific, removed StreamLoader, FrameLoader - Require LoadListener, removed CacheLoader, ContentLoader, DataLoader, FileLoader - Extend StreamLoader, removed BrowserFrame - Removed methods that create LoadListener - BrowserFrame.startLoadingResource() is called from native CallbackProxy, WebView - Removed calls to Network methods CacheManager, CookieManager, CookieSyncManager, WebViewCore, WebResourceResponse - Removed other Android-stack specific code JniUtlil - Removed useChromiumHttpStack() WebViewDatabase - Removed all code to create cookies and cache databases for Android HTTP stack See corresponding WebKit change https://android-git.corp.google.com/g/166327. Bug: 5495616 Change-Id: If491675516f6eb187077af4220214bb6e6a8d045
* WebViewDatabase v11 for ICS.Ben Murdoch2011-11-161-6/+41
| | | | | | | | | | | | | | | | | | | | | | | Bump WebView database version to 11. This has the following effects: - Removes the old webview cookie table on GB devices. Cookies are now managed by the Chromium stack. - Removes the old webview cache database on GB devices. Cache is now managed by the Chromium stack. - Autocomplete form data is now stored/retrieved based on the URL minus the query string/fragment. Upgrade any existing form URLs in the database to match this format, so we can still use them. This will impact GB and HC devices. This has an unfortunate side effect that we may end up with duplicate URLs in the formurl table (say we had two URLS for the same host but with different query strings). Currently we only take the first url from the table - which is fine when they were unique. The simplest way to work around this is just iterate all the rows returned and use all the values we find. Bug: 5560410 Change-Id: I59323dc5e523969e0a1c268b5936d6fa998d625c
* Fix a bug in the database upgrade process, and refactor slightly.Ben Murdoch2011-11-161-49/+57
| | | | | | | | | | | During upgrade from v9 -> v10 the database version was not being updated. Also remove conditionals based on what are effectively hardcoded truth values to simplfiy the logic greatly. Bug: 5560410 Change-Id: I31a01aa35a109a951d4e4c6d5b884bb666668b28
* Enable write ahead logging on databases used by WebView.Leon Scroggins2011-01-101-3/+5
| | | | | Bug:3337213 Change-Id: Ic687bc506faba23c3e52e44f0a5d0146a352206e
* Avoid superfluous calls to CacheManager with the Chromium HTTP stackSteve Block2011-01-071-4/+22
| | | | | | | | | | | | | | When using the Chromium HTTP stack, most of the calls to CacheManager methods are not required, as we're not using its cache. These methods are now marked with asserts to make this clear. Also avoid creating the cache database in WebViewDatabase. This will avoid creating the database databases/webviewCache.db and the directory cache/webviewCache. Bug: 3270236 Change-Id: I68f94dde16830ed817454d5e1af961f41b71d018
* Update the storage locations used by the Chromium HTTP stackSteve Block2010-09-281-0/+3
| | | | | | | | | | | This updates the strorage locations to better match those used by the Android HTTP stack. The corresponding external/webkit change is https://android-git.corp.google.com/g/70643 Bug: 3039536 Change-Id: Ia7ea68d1472e96788a7fbaa6e8f7aa1ee51b3fb0
* am dc1f0858: am 9902196f: Fix npe in getCacheTotalSize.Patrick Scott2010-08-111-0/+3
|\ | | | | | | | | | | | | Merge commit 'dc1f08586eadc3a3dbbdf22b520ba1065b2032f8' * commit 'dc1f08586eadc3a3dbbdf22b520ba1065b2032f8': Fix npe in getCacheTotalSize.
| * Fix npe in getCacheTotalSize.Patrick Scott2010-08-111-0/+3
| | | | | | | | | | Bug: 2882277 Change-Id: I9319a48e0ed75561d3d04691fb288f69d11edc84
* | Move WebViewDatabase initialization into a background thread.Patrick Scott2010-06-161-109/+154
|/ | | | | | | | | | | | | This isn't the perfect solution as any calls into WebViewDatabase will block until initialization completes. It is better than the current model which blocks when creating the WebViewDatabase. In order to get a perfect solution, we would need to do initialization in the background and have a way to interact with the database during initialization that would not block. Bug: 2721802 Change-Id: Ibbaf7f97926128de6534fbf2148452099766c6b7
* Fix for when flash loads cached crossdomain.xml files.Leon Clarke2010-03-231-2/+11
| | | | | Cache the x-permitted-cross-domain-policies header. http://b/issue?id=2519669
* Close Cursors in finally blocks.Leon Scroggins2010-03-221-135/+210
| | | | | | Fix for http://b/issue?id=2533750 Change-Id: I3ebcc6147e4035ce1c4bf6b76a359ce14196e357
* Add a new WebCoreWorker thread to handle the tasksGrace Kloba2010-03-011-2/+38
| | | | | | | | | | | | | | | | | | | | | | | which should not block either UI or WebKit. It handles local file access, cache access and trim cache. Move createCache, saveCache and most of getCache out of WebCore thread so that slow IO and database will not affect loading performance. getCache can be still called from WebCore thread in the uncommon cases like redirect and POST validation. Move cache ticker from WebCore thread to WebViewWorkerThread. Move setCookie from WebCore thread to WebViewWorkerThread. Remove the unreferenced files in the cache directory while trim cache. Confirmed with our SQL expert, Vasu, there is no need to wrap clearCache with end/startTransaction any more. http://b/issue?id=2414792 http://b/issue?id=2475242
* If openOrCreateDatabase() throws an exception, deleteGrace Kloba2009-10-131-3/+21
| | | | | | | the old db and re-do it. If it still fails, something bad happens, like the directory may have the different permission. Let it throw as WebView needs the db. Fix http://b/issue?id=2179339
* Per suggestion in http://b/issue?id=2062340, update the UNIQUE in theGrace Kloba2009-09-141-3/+18
| | | httpauth table.
* Add content-disposition into the cache header as it is needed by Flash.Grace Kloba2009-06-291-5/+14
| | | | As WebKit is using string version of "expires", pass it with the rest of the headers.
* Fix for the new webkit. Now "expires" takes the string instead of int.Grace Kloba2009-06-251-7/+16
| | | | We have to upadte our cache database. Good thing is Gears can avoid the expensive date conversion.
* auto import from //depot/cupcake/@135843The Android Open Source Project2009-03-031-0/+967
|
* auto import from //depot/cupcake/@135843The Android Open Source Project2009-03-031-967/+0
|
* auto import from //branches/cupcake/...@131421The Android Open Source Project2009-02-131-25/+22
|
* Code drop from //branches/cupcake/...@124589The Android Open Source Project2008-12-171-34/+42
|
* Initial ContributionThe Android Open Source Project2008-10-211-0/+962
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-20 15:39:29 +0000