[
https://issues.apache.org/jira/browse/CB-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498462#comment-13498462
]
Andrew Grieve commented on CB-1810:
-----------------------------------
My thinking for putting it in CordovaInterface was that it would make it a
sibling of getActivity().
In the context of plugins, you have:
* This method is called from the WebView thread. To do a non-trivial
amount of work, use:
* cordova.getThreadPool().execute(runnable);
*
* To run on the UI thread, use:
* cordova.getActivity().runOnUiThread(runnable);
I suppose we could change this to webView.getThreadPool().
The thread pool is meant to be an app-wide singleton. I was thinking that
CordovaInterface would probably a singleton, but CordovaWebview isn't since you
can have multiple views, either at the same time or one after another.
> CordovaWebView does not work as a component without providing it a ThreadPool
> -----------------------------------------------------------------------------
>
> Key: CB-1810
> URL: https://issues.apache.org/jira/browse/CB-1810
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 2.2.0
> Reporter: Joe Bowser
> Assignee: Andrew Grieve
> Priority: Blocker
> Fix For: 2.3.0
>
>
> Apparently CordovaWebView no longer works as a stand-alone component. We may
> have to release a 2.2.1 because of this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
