| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
No change to logic, only documentation change. This adds some
clarifications to getCookie()/setCookie():
* getCookie() returns multiple cookies, setCookie() accepts only one
* This briefly describes getCookie()'s output format because it's fairly
simple
* This summarizes setCookie()'s input format and provides an example,
but directs the reader to the RFC spec for a full description
* Minor formatting changes, including editing a javadoc link which
doesn't currently render correctly in kotlin docs (for
ValueCallback#onReceiveValue)
Fixes: 175471135
Test: m offline-sdk-docs -j4
Change-Id: Id9052fa03584caae5ffc92ed1f6c4d2641d900ce
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Having a hidden abstract method for a class that can be extended
means that public implementors cannot implement these hidden methods
posing a risk that custom implementations will not have required
abstract methods resulting in an exception.
Bug: 151134792
Test: make update-api
Change-Id: I758d12465fabc671be19bedeeceb16885de23c87
Merged-In: I758d12465fabc671be19bedeeceb16885de23c87
Exempt-From-Owner-Approval: large scale suppression of existing issues,
no-op in terms of behavior
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Deprecate unsafe:
- WebSettings#setAllowUniversalAccessFromFileURLs
- WebSettings#setAllowFileAccessFromFileURLs
- CookieManager#setAcceptFileSchemeCookies
And direct the users to use WebViewAssetLoader instead.
Bug: 148841999
Test: m offline-sdk-docs -j20
Change-Id: I607d1343cb2aa5baead49ceff6dbac4a4474009c
|
| |
|
|
|
|
|
|
|
|
|
| |
No change to logic, only docs. This announces 'Secure' cookies are
deprecated for insecure URL schemes (only "https://" is considered
secure). This doesn't mention target SDK, because apps should follow
this guidance for all WebView versions, target SDKs, and OS levels.
Bug: 149589092
Test: m offline-sdk-docs -j4
Change-Id: I07c2b5341588d354f7f8219ce71a3d2ca04bc982
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RFC2109 has been obsolete for a long time, and the docs aren't very
clear what exactly the RFC has to do with CookieManager; the RFC is
about HTTP and it's not immediately clear how this would apply to a Java
API.
Update the reference to the current cookie spec (and hyperlink it), and
clarify the text to explain that the HTTP header formats from the RFC
are the formats used to get/set set cookies.
Fixes: 143086151
Test: make ds-docs
Change-Id: I5e5838d3435b74516847b63e485fdd93810284aa
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ART uses the class object's embedded monitor to protect class
initialization - the same monitor used by "synchronized" applied to
static methods. This can cause deadlock in extremely rare cases of
preemption during WebView code loading.
Remove synchronized from all static methods in WebView, to avoid this
deadlock. In most cases the synchronized is simply unnecessary in the
Chromium-based WebView implementation; in CookieSyncManager we instead
use a separately allocated Lock object to preserve thread safety.
Bug: 27417671
Change-Id: I13049f23fc984b77a3f4c203a5c698858c64abfe
|
| |
|
|
|
|
|
| |
Add missing @Deprecated annotations for methods with @deprecated tag
in javadoc.
Change-Id: I35b78ccb97832d86b914c21a300444ba29e33844
|
| |
|
|
|
|
|
|
| |
The CookieManager documentation became incorrect after deprecating
CookieSyncManager. Remove the note about CookieSyncManager.
code.google.com/p/android/issues/detail?id=82052
Change-Id: I13bc52716cd71e47b67148186a69f7269e418864
|
| |
|
|
|
| |
BUG:18152150
Change-Id: Ifd6dcac17663631058d895c61bb6e8018c5aeecc
|
| |
|
|
| |
Change-Id: Idb3976edfae37293ed75cb5b869b4b42d8042bbe
|
| |
|
|
|
|
|
| |
As per API council feedback.
Bug: 17253647
Change-Id: Ide3d4b216f01a96e54111f885813ca8a7c3865ba
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Documents the defualt settings of acceptCookies and acceptFileSchemeCookies.
The current defaults:
<L >=L
acceptCookies | y | y |
acceptThirdPartyCookies | y | n |
acceptFileCookies | n | n |
Bug: 11575158
Change-Id: Ia6cb71bf80608cb2ea8049192f33616e57c15801
|
| |
|
|
|
|
|
| |
Remove synchronized from setAcceptThirdPartyCookies
Bug: 16403458
Change-Id: I6073da2c03fd0952bc447f7cfe0d959148af6877
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The CookieSyncManager is largely useless as the WebView
automatically syncs cookies every 30s (whether you like it
or not). The one method which needs to be saved is sync,
there is no other way to force a sync without this.
We move sync to the CookieManager and rename it to flush
for greater consistency.
Bug: 11060034
Change-Id: I8a14998020eea54f196fc6ed845b09ed69cfd447
|
| |
|
|
|
| |
Bug: 11678084
Change-Id: Ieb74fb6caae3d5a18dbfe748be47ebebad003cf7
|
| |
|
|
|
| |
Bug: 14379829
Change-Id: I6b0e0644153a805eccb48d30b0ad3e91babd8093
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
A change that made the setCookie() docs say setCookie rejected
session cookies was introduced here
https://googleplex-android-review.git.corp.google.com
/#/c/166946/3/core/java/android/webkit/CookieManager.java
and looks like it was just a mistaken rephrasing of the original docs.
This change removes that comment from the current docs.
Bug: 14379829
Change-Id: I36ae708f55faf424424ea18f75c89872e7c71312
|
| |
|
|
|
| |
Bug: 5461416
Change-Id: I0ae09943007cf3866daad97a76f5008e61c471ed
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the JavaDoc style for the following classes ...
- CacheManager.java
- CookieManager.java
- GeolocationPermissions.java
- WebResourceResponse.java
- WebSettings.java
- WebStorage.java
- WebView.java
In particular, this applies the guidelines at
https://wiki.corp.google.com/twiki/bin/view/Main/APIDocumentation
This should help to ensure that future JavaDoc comments use correct style,
rather than using incorrect style for consistency.
Note that this change does not attempt to improve the content of the JavaDoc
comments. This will be done in later changes.
Bug: 5461416
Change-Id: I79e9b15a8cf3597195d58e154a7eb1bcc462944c
|
| |
|
|
|
|
|
|
| |
This allows CookieManager subclasses to correctly override all behvaior
in the base class.
Bug: 6379925
Change-Id: Ife02db24bc192bc1eabf09e0d64668716786d237
|
| |
|
|
|
|
|
| |
This is a quick workaround to get tests running again, will follow up with full fix tomorrow.
Bug: 6379925
Change-Id: I96d6e27bfb8f8cd41ec08845ab0fb1e584dbc9da
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GeolocationPermissionsClassic
CookieManagerClassic
WebIconDatabaseClassic
WebStorageClassic
Also creats a WebViewFactory top level class - this remains hidden
for now, as it's currently only used implicitly by the other
public WebView classes to create the provider instances.
Bug: 5626244
Change-Id: Id0ca1c16d8058f31a86414bbc0e8a55db4b907ba
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- remove final from classes which we will need to provide subclasses
in future: CookieManager, GeolocationPermissions, WebIconDatabase
and WebStorage. None of these have published constructors,
so applications cannot subclass them anyway.
- Also convert some protected members of JsResult to private, as its of
no use to legal subclasses, and applications cannot subclass it.
Change-Id: Iaca9d2db31e25853b6c55feae41d9e7774087479
|
| |
|
|
|
|
|
| |
See b/5495616.
Bug: 6228353
Change-Id: I16cfd7b37973919d5bf14d2d80954caede264961
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
| |
Also fix naming of CookieManager.pendingCookieOperations.
Clean-up only, no functional change.
Bug: 5461416
Change-Id: Ia129c4535b8ef6a5a314e588c34ee6db2fe5b386
|
| |
|
|
|
|
|
|
|
|
|
| |
Add missing check for native HTTP stack inside
CookieManager.getCookie(WebAddress) and
CookieManager.setCookie(WebAddress) - private APIs that now
will throw an exception as the legacy cookie table no longer
exists with WebViewDatabase version 11.
Bug: 5690908
Change-Id: I51ae848d03b04d6021d314dda4a199675e38ab02
|
| |
|
|
|
| |
Change-Id: I10d96b254dcf3cb04f8d5cdf4bc527c84c362c1c
https://android-git.corp.google.com/g/#change,99052
|
| |
|
|
|
|
|
|
|
|
|
| |
incognito
Adding private mode parameter for some cookie operations.
Depends on this change in webkit:
https://android-git.corp.google.com/g/#change,99051
Change-Id: I304de625632c3d659bf0d7a6b6a6e2bec985ecb6
|
| |\
| |
| |
| | |
scheme URLs"
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Needs https://android-git.corp.google.com/g/83647 in external/webkit,
which disallows such cookies by default and provides configuration
methods native side.
Also updates TestShellActivity to allow such cookies, as they are
required for the page cycler.
Bug: 2944150
Change-Id: Idcc7e2812fab33e6a2a8766a2176bc3278e617da
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
operations." into honeycomb
* commit '01b7a98c31f3d4587fb6739c8c6b35530177c20c':
Need a public way to wait for cookie operations.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Hidden for now as we are past the public api deadline.
Bug: 3421214
Change-Id: I8a65ae479d0b8b020af2600d7d29d5d358414add
|
| | |/
| |
| |
| |
| |
| | |
Setting http:// at the start if there is no :// in the url
Change-Id: Idfae4f724808267fe9c8ab3864cfc4305ddac0e7
|
| | |
| |
| |
| |
| |
| |
| | |
Using WebAddress to parse the url, this way we will match the
java stack.
Change-Id: I30979df5ef347d9770985ebbb8139ec119764460
|
| |/
|
|
|
|
| |
Adding http:// at the start of the url if there is no :// already
Change-Id: If292f60af3289a9849ff060ffacc0d97e3120132
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is a generally useful method, not specific to CookieManager.
I want to use it to modify the behaviour of CacheManager when we're
using the Chrome HTTP stack.
Corresponding C++ changes in I78a92cb2
BUG=3270236
Change-Id: I56b0ddcaa93ef340f4ffc3578486c3c96316f2ec
|
| |
|
|
|
|
|
| |
Webkit loadurl() will wait on the webcore thread until oustanding
cookie operations complete.
Change-Id: I067408fdb9acd2e2d1f1f21eef910d0b26304332
|
| |
|
|
|
|
|
| |
I previously tried to make this a new public API, but I realised
it should actually hang off the existing code in CookieSyncManager.
Change-Id: Ic44334008266bad5ba1245cf674350a4c10712ce
|
| |
|
|
|
|
|
|
|
| |
The browser app will use this to sync cookies to flash when it is
sent to the background. Corresponding C++ code is in Ia9b56f3c.
Bug: 3231371
Change-Id: I04e96affcce335191ee2075d0e160f0d8313bf76
|
| |
|
|
|
| |
Bug: 3167208
Change-Id: I8adebf9f9e92967a3250e61ccfbb45e02bbee3f9
|
| |
|
|
|
|
|
|
|
|
| |
hasCookies(), removeExpiredCookie(), removeSessionCookie() and setCookie()
Requires a change to external/webkit ...
https://android-git.corp.google.com/g/76897
Bug: 3116410
Change-Id: I46603be60e2a6b0e8bac9ca506b56d78643a3658
|
| |
|
|
|
|
|
|
| |
Requires a change to external/webkit ...
https://android-git.corp.google.com/g/76603
Bug: 3116410
Change-Id: Id0cd5871fd13f952d4f2aa963576a4e610459a18
|
| |
|
|
|
|
|
|
|
|
| |
HTTP stack
Also requires a change to external/webkit ...
https://android-git.corp.google.com/g/76066
Bug: 3116410
Change-Id: If8562468708e7d68c5be53db3860647687ebf3bd
|
| |
|
|
|
|
|
|
|
| |
This will be required when hooking up CookieManager to the Chromium
stack, as we need to decide in Java whether or not to call into native
code.
Bug: 3116410
Change-Id: Ibe2f7687655a93993b19f4fb9b4fed137b3b9466
|
| |
|
|
|
|
|
|
| |
Requires a change to external/webkit ...
https://android-git.corp.google.com/g/75473
Bug: 3086308
Change-Id: I01274b3b1384a6947d5a56a51b0b93b1898ddebc
|
| |
|
|
| |
Change-Id: Iceaf3d648289344e53c37273f7324a79676fbef7
|