Window.open does nothing in windows mobile 10 (IEEdge)

Paul

unread,

Sep 27, 2016, 5:52:31 AM9/27/16

to GWT Users

Window.open("http://www.google.co.uk","_blank","")

....does nothing in windows mobile 10 (IEEdge) when running in GWT 2.7

Any ideas?

If I write a simple html page with the above javascript, then the browser happily opens the google page on a new tab.

Paul

unread,

Sep 27, 2016, 6:27:15 AM9/27/16

to GWT Users

In a simple GWT test project it works. It must be something I'm doing with event capture. My application is complex so I'll have to try and workout what is stopping the window.open just for IEEdge on windows mobile10

IEEdge desktop is fine and so is chrome! Strange....

Vassilis Virvilis

unread,

Sep 27, 2016, 6:32:41 AM9/27/16

to google-we...@googlegroups.com

I mean maybe Edge may also have a connect to desktop Edge debugging mode....

On Tue, Sep 27, 2016 at 1:31 PM, Vassilis Virvilis <vas...@gmail.com> wrote:

looks like a popup blocker issue... Does an alert command before window open() works? If yes then you don't have problem with the event but with open per se.

Mobile Chromium and mobile Safari have a developer mode with console - when connected to desktop computer. It needs some setup but a console may give a hint.

Vassilis

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
Vassilis Virvilis

--

Vassilis Virvilis

unread,

Sep 27, 2016, 6:35:49 AM9/27/16

to google-we...@googlegroups.com

looks like a popup blocker issue... Does an alert command before window open() works? If yes then you don't have problem with the event but with open per se.

Mobile Chromium and mobile Safari have a developer mode with console - when connected to desktop computer. It needs some setup but a console may give a hint.

Vassilis

On Tue, Sep 27, 2016 at 1:27 PM, Paul <paul....@kirona.com> wrote:

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsub...@googlegroups.com.

To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--

Vassilis Virvilis

Paul

unread,

Sep 27, 2016, 1:27:07 PM9/27/16

to GWT Users

Thanks for suggestions. As far as I know you still cannot remote debug mobile IEEdge in visual studio 2015

Anyway I think I have the answer. For some reason if I call window.open in response to a click event or another native event like pointerdown then it works.

If I call window.open in response to a GWT fired event like TapEvent for example (I'm using MGWT which fires tap events when you get a pointerdown followed by a pointerup event) then window.open does not work! You get no error, the call is basically ignored.

Very strange. I'm still investigating.

Cheers

On Tuesday, September 27, 2016 at 11:35:49 AM UTC+1, Vassilis Virvilis wrote:

looks like a popup blocker issue... Does an alert command before window open() works? If yes then you don't have problem with the event but with open per se.

Mobile Chromium and mobile Safari have a developer mode with console - when connected to desktop computer. It needs some setup but a console may give a hint.

Vassilis

On Tue, Sep 27, 2016 at 1:27 PM, Paul <paul....@kirona.com> wrote:

In a simple GWT test project it works. It must be something I'm doing with event capture. My application is complex so I'll have to try and workout what is stopping the window.open just for IEEdge on windows mobile10

IEEdge desktop is fine and so is chrome! Strange....

On Tuesday, September 27, 2016 at 10:52:31 AM UTC+1, Paul wrote:
Window.open("http://www.google.co.uk","_blank","")

....does nothing in windows mobile 10 (IEEdge) when running in GWT 2.7

Any ideas?

If I write a simple html page with the above javascript, then the browser happily opens the google page on a new tab.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsub...@googlegroups.com.

To post to this group, send email to google-we...@googlegroups.com.

Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
Vassilis Virvilis

Paul

unread,

Sep 28, 2016, 6:27:03 AM9/28/16

to GWT Users

Does anyone know if this has been fixed?

http://blog.daniel-kurka.de/2012/05/mobile-webkit-alert-dialog-breaks-touch.html

My problem is with MGWT. It fixes the above bug by using a deferred ScheduledCommand to fire MGWT events e.g. a TapEvent.This is causing me the problem in IEEdge mobile (not desktop) where if you do not call window.open in the context of a native event initiated by the user then the window.open call is ignored. I'm guessing the IEEdge mobile is not as clever as the desktop version and simply blocks all window.open calls if not in the context of a user initiated native event (a form of popup blocking)

I can fix MGWT by simply not deferring these fired events in IEEdge but would like to know if I can remove this fix for all safari permutations (specifically mobile webkit)

Any thoughts would be appreciated.

Reply all

Reply to author

Forward