what do you mean exactly by "can't be executed"? just nothing happens? does the app deadlock? do you have a test app to demonstrate the problem?

Also you are already in java code in onJsAlert, why would you use the javabridge to go back to js and then callback to java again? that seems like bad design

So before, when the view.loadUrl(javascript:(function(){CustomInterface.completeAction(document.head.innerHTML)})());  
was called then the webview tried to load that uri hence the javascript method from the "CustomInterface"  was called.

Well the reason I m doing it it is because I want to grab some content from the html as you can see from the parameter "document.head.innerHTML".

I finally found the solution. 
I just have to call result.confirm() and then the javascript cant executed as before

  @Override 
    public boolean onJsAlert(WebView view, String url, String message, JsResult result) {
            result.confirm();
            view.loadUrl(javascript:(function(){CustomInterface.completeAction(document.head.innerHTML)})());
 
        return super.onJsAlert(view, url, message, result);
    } 


Just wondering if this change was a bug or a feature ?
 

that sounds like an intentional change in m52 then: https://www.chromestatus.com/features/5683408571203584

why do you need to come back to java then? can't you just directly execute whatever js you need, and just call back to java through CustomInterface?

Well due to some limitation of the backend, when the alert appears I need to parse the html file for a value I need to save. as you can see from my example the parameter I pass to my javascript interface is "document.head.innerHTML". 

I'd suggest not using JS alerts as a way to notify the java code about events, if that's what you're doing (it sounds like it?). Call a javascript interface, or use postMessage on newer OS versions, or something.

Chromium will no longer support the nested event loop required to continue to process JS code while waiting for a response to alert/confirm/prompt, and unfortunately we aren't going to be able to revert this. alert/confirm/prompt are terrible because of their synchronous behaviour - ideally all web content should stop using them entirely.