I think the cycles required for keeping sendJavascript around are probably worthwhile given that otherwise developers might have to resort to loadURL(javascript://) for their special cases.
Ultimately, I am much less involved in the Android particulars, so I'll just leave you with an opinion, and not a firm +/- @purplecabbage risingj.com On Mon, May 26, 2014 at 12:07 PM, Ian Clelland <iclell...@chromium.org>wrote: > On Mon, May 26, 2014 at 2:58 PM, Joe Bowser <bows...@gmail.com> wrote: > > > On Mon, May 26, 2014 at 11:53 AM, Jesse <purplecabb...@gmail.com> wrote: > > > Is the webview method evaluateJavascript [1] still available, callable > > from > > > the context of a plugin? Or is this somehow hidden? > > > > It only exists on KitKat, earlier implementations require > > loadURL(javascript://). > > > > > > > > Personally I think is okay to remove the cordova implemented > > > sendJavascript() as long as there is still a way to accomplish the rare > > but > > > sometimes required bare metal pass through. > > > > > > Do/will other pluggable webviews support a consistent interface for > > calling > > > javascript in their loaded pages? ie. Does crosswalk support > > > evaluateJavascript? > > > > > Very good question! I don't know. > > > > Crosswalk's XWalkView supports evaluateJavascript, and I believe that it is > actually being used by InAppBrowser. > > I don't know about any other webviews. >
