You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Andrew Grieve (JIRA)" <ji...@apache.org> on 2014/07/16 20:08:05 UTC
[jira] [Resolved] (CB-7153) CordovaWebView() crashes if constructed
with a Context that does not implement CordovaInterface
[ https://issues.apache.org/jira/browse/CB-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Grieve resolved CB-7153.
-------------------------------
Resolution: Fixed
Fixed with:
https://github.com/apache/cordova-android/commit/705991e5b037743e632934b3c6ee98976e18d3f8
Which moves to two-phase initialization, and also injects the view clients, CordovaPreferences, and whitelist.
Fixed in 3.6.0-dev
> CordovaWebView() crashes if constructed with a Context that does not implement CordovaInterface
> -----------------------------------------------------------------------------------------------
>
> Key: CB-7153
> URL: https://issues.apache.org/jira/browse/CB-7153
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Android
> Reporter: Andrew Grieve
> Assignee: Andrew Grieve
> Priority: Minor
>
> It is a bit restrictive to enforce that the Context used to construct CordovaWebView must also be the thing that implements CordovaInterface. However, it's important to maintain a Constructor that takes a Context as its only parameter so that the View can be inflated within XML layouts.
> To solve this, and to make it possible to initialize the class with other dependencies that it has, we should move to using two-phase initialization.
--
This message was sent by Atlassian JIRA
(v6.2#6252)