[WebView Support Library] Determine how to handle the fallback case where WebView is not new enough contain the support-library-glue. |
||||
Issue descriptionWe need to be able to support developers using the WebView support library on devices where WebView is not up-to-date. We probably want to use the existing android.webkit.WebViewProvider in such cases.
,
Jul 10 2017
Related to this - we should also cover the case where the device is using an AOSP WebView (if that case is different to using an out-of-date GMS WebView.
,
Jul 11 2017
,
Aug 15 2017
,
Nov 6 2017
When the WebView package on a device is too old to contain the support library glue the app developer should not be calling Support Library WebView APIs - we will provide a utility method for developers to call to check what Android level the support library corresponds to. So if the app developer calls a Support Library WebView method anyway, that method should either be a no-op, or throw an exception.
,
Feb 15 2018
The way we will do this is probably just to make our list of features empty if the WebView APK doesn't support the support library.
,
Apr 2 2018
,
Apr 2 2018
,
Apr 6 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by gsennton@chromium.org
, Jul 10 2017