The problem is that my example adds a custom WebChromeClient which will not work with WVE (unless you use two different WebViews).
damn! sorry, i forgot that. however, in my own defense and at the risk of punishment, i would add that there is no direct conflict between webviewextras and the custom webchromeclient IF you don't use webviewextras' webchromeclient. i ran the example with webviewextras and the custom webchromclient and executed javascript via webviewextras without an issue.
it is true that, if i use the custom webchromeclient AND webviewextras webchromeclient (and declare the webviewextras' webchromeclient AFTER the custom webchromeclient, ShoeFileChooser would fail (as expected). but if i use the customchromeclient and webviewextras (without webviewextras webchromeclient),
there is no problem.
what the op uses a webchromeclient for is another question. but since he only reveals snippets of his code, it's difficult to say. webchromeclient doesn't allow all that much beyond onfilechooser and console.logging, and he has streesed in several posts that what he needs is webviewextras and javascript. he can have his cake and eat it.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
and, if he has to have logging capability from the custom webchromeclient, he can add these 6 lines of inline code to the example's inline java:
@Override
public boolean onConsoleMessage (ConsoleMessage consoleMessage) {
String logMessage = "CONSOLE LOG: " + consoleMessage.message() + " in (" + consoleMessage.sourceId() + " at Line: " + consoleMessage.lineNumber() + ")";
processBA.raiseEventFromUI(this, "console", new Object[] {logMessage} );
return true;
}
if he creates a sub called "console" in main, he can see console messages. if he uses webchromeclient for other purposes, they could probably easily be added.