At the moment, it doesn't do anything, just print something in the logs,
then calls the super implementation:
@Override
public boolean onCreateWindowRequested(XWalkView view,
XWalkUIClient.InitiateBy initiator, ValueCallback<XWalkView> callback)
{
Log.d(TAG, "onCreateWindowRequested called");
return super.onCreateWindowRequested(view, initiator, callback);
}
I only see the log entry when window.open() is called with 1 argument. I
don't see it when the JS code uses 3 arguments. I'm not saying the number
of arguments is the cause, but that's the only difference I can see so far
between the 2 web sites.
Michael.
On Wed, Jul 27, 2016 at 2:34 AM, Zhang, Xiaofeng <[email protected]>
wrote:
> Could you share your implementation of onCreateWindowRequested?
>
>
>
> Best Regards J
>
> Xiaofeng Zhang
>
>
>
> *From:* Crosswalk-help [mailto:
> [email protected]] *On Behalf Of *Michael
> Goffioul
> *Sent:* Wednesday, July 27, 2016 12:15 AM
> *To:* [email protected]
> *Subject:* [Crosswalk-help] XWalkUIClient.onCreateWindowRequested() not
> called for 3-argument version of window.open()
>
>
>
> Hi,
>
>
>
> I'm using crosswalk-18. In my app, I've overridden
> XWalkUIClient.onCreateWindowRequested(). Both
> settings SUPPORT_MULTIPLE_WINDOWS and JAVASCRIPT_CAN_OPEN_WINDOW are set to
> true. The problem is that onCreateWindowRequested is not always called.
>
>
>
> It is called in
> http://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_win_open
>
>
>
> It is not called in http://www.psiauto.com/is/root/tools_testWinindex.cfm
>
>
>
> The main difference I can see between these 2 sites is that the former is
> using 1 argument for window.open, while the latter uses 3 arguments.
>
>
>
> Is this a know problem? Is there a workaround? Is it fixed in newer
> versions of crosswalk?
>
>
>
> Thanks,
>
> Michael.
>
>
>
_______________________________________________
Crosswalk-help mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
