summaryrefslogtreecommitdiff
path: root/core/java/android/webkit/WebViewProviderInfo.java
Commit message (Collapse)AuthorAgeFilesLines
* Use new UnsupportedAppUsage annotation.Artur Satayev2019-12-181-1/+1
| | | | | | | | Existing annotations in libcore/ and frameworks/ will deleted after the migration. This also means that any java library that compiles @UnsupportedAppUsage requires a direct dependency on "unsupportedappusage" java_library. Bug: 145132366 Test: m && diff unsupportedappusage_index.csv Change-Id: I5be7335b23a92b8ac80d2fd890198273b66ad644
* All Parcelable CREATOR fields are @NonNull.Jeff Sharkey2019-02-281-1/+1
| | | | | | | | | If they were null, then the Parcelable would fail to work. Bug: 126726802 Test: manual Change-Id: I7929ffa2f20e5de1c8e68e8263cca99496e9d014 Exempt-From-Owner-Approval: Trivial API annotations
* Add @UnsupportedAppUsage annotationsMathew Inwood2018-08-161-0/+2
| | | | | | | | | | | | | | | | For packages: android.webkit This is an automatically generated CL. See go/UnsupportedAppUsage for more details. Exempted-From-Owner-Approval: Mechanical changes to the codebase which have been approved by Android API council and announced on android-eng@ Bug: 110868826 Test: m Change-Id: I41643e1e47391a12b0aed3058b3d9987a8e6ee2f
* Store WebView package signatures as Signatures instead of StringsGustav Sennton2018-01-031-6/+13
| | | | | | | | | We are currently storing WebView package signatures as Strings in WebViewProviderInfo, represent these as Signatures instead. Bug: 62429931 Test: start WebView app + run WebViewTest GTS tests + WVUS tests Change-Id: I910db133cd147b44b4b1c63921308d82db44e5b3
* Add system api to reach WebViewUpdateService Binder interface.Gustav Sennton2016-04-011-1/+5
| | | | | | | | Instead of using reflection in XTS tests we add some system-apis to enable fetching information about webview packages. Bug: 26381867 Change-Id: If983a01b6855e4a4c08ef0b5873304918d499b76
* Simplify WebViewProviderInfo - move its logic into WebViewUpdateService.Gustav Sennton2016-03-311-118/+8
| | | | | | | | | | | | | | | | | | The WebViewProviderInfo should now be ready to be added as an API to be fetched from XTS tests (to avoid using reflection). Move the logic for validation, signature checking and package info fetching out of WebViewProviderInfo so that we can mock the coupling between that logic and the system (e.g. the package manager). Note: with this patch we stop caching valid webview packages in the update service (we would still refetch them anyway when anything important happened). Bug: 27635535 Bug: 27736084 Change-Id: Ia455202d2fd5bc4e03dce0fd917d262bf942d1a3
* Add utility interface for WebView preparation logic.Gustav Sennton2016-03-181-0/+4
| | | | | | | | | | | | To make the WebView preparation mechanism testable we add a utility interface that can be overridden during a test to avoid calling the Android framework and to provide custom WebView packages. With this change we also split some of the code from the WebViewFactory (code unrelated to WebView loading) into a separate utility class. Bug: 27635535 Change-Id: I265ecd42b24ad5383637e125b3654ff339c9df9c
* Add fallback packages to be enabled iff no webview packages are validGustav Sennton2016-02-231-3/+9
| | | | | | | | | | | | | | | | This patch makes it possible to declare a WebView package as a fallback which means that the package will be enabled iff there exist no other valid and enabled (and available-by-default) webview packages. The enabled-state of a fallback package is updated at boot and if a webview package is changed (it it's been up/downgraded or has had its enabled-state changed). This patch also adds 'webviewupdate' shell commands for enabling and disabling this mechanism. Bug: 26375524, 26375860 Change-Id: I151915e5d6d932697dab10aeb593687e6b9c817e
* Move current WebView provider from Settings.Secure to Settings.GlobalGustav Sennton2016-02-111-20/+14
| | | | | | | | | | | | The current WebView provider is not user-specific and should therefore be stored as a Global rather than a Secure setting. Also do some code cleaning including a fix in WebViewProviderInfo to always fetch up-to-date information about whether a webview implementation package is enabled. Bug: 27142972 Change-Id: I4d4b8fca775e97980fb5c34313be6d82472e7d33
* Merge "Fix WebView loading logic to allow changing provider if current disabled"Gustav Sennton2016-01-111-1/+37
|\
| * Fix WebView loading logic to allow changing provider if current disabledGustav Sennton2016-01-061-1/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | Add an XML tag declaring whether a package can be used without explicitly being chosen by the user (it is available-by-default). Change the WebView loading logic to either 1. load a user-chosen and enabled package or 2. load an enabled and available-by-default package or 3. any package that is valid Bug: 26400585 Change-Id: I8de253c1687e3cc7961184c2d770d4e385d6187a
* | More progress on triaging PackageManager callers.Jeff Sharkey2016-01-081-4/+3
|/ | | | | | | | | | | | Catch a bunch of simple cases where the PackageManager flags are obvious. Add the ability to use the MATCH_SYSTEM_ONLY flag on PackageInfo and ApplicationInfo queries. Re-examine recent tasks after a user is unlocked, since some of the activities may now be available and runnable. Bug: 26471205, 26253870 Change-Id: I989d9f8409070e5cae13202b47e2c7de85bf4a5b
* Allow several valid signatures per WebView provider.Gustav Sennton2015-12-171-8/+15
| | | | | | | | | | If one of the signatures match the package signature the package is considered valid. This makes it possible to match signatures in user builds for both signed and unsigned builds. Bug: 26220882 Change-Id: Ie2e7567bf518d4859d68b5fdf5b9833fcdaa7670
* Add functionality for changing WebView provider.Gustav Sennton2015-12-111-0/+140
Make it possible to change WebView provider (through a Developer setting) and kill all apps using the old provider. This includes checking the signatures of the WebView providers to make sure they are valid. Now that we can change WebView provider through a setting it is possible to change provider while some provider is being updated. Because of this we now keep track of which provider should be in use in WebViewUpdateService to make sure we use the correct provider at all times. We now also read WebView package meta data (name, package name, and signature) from a separate xml file. Main bug: crbug.com/546185 Bug: 25338573 Change-Id: I660fd1a40a5388f6569a06a7f0d029e8ff65945a
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-20 23:55:42 +0000