You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2015/07/16 15:00:05 UTC

[jira] [Commented] (WICKET-5953) AjaxFallbackLink triggers both the JS/AJAX request and the fallback link request on touchscreen in IE11

    [ https://issues.apache.org/jira/browse/WICKET-5953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629680#comment-14629680 ] 

Martin Grigorov commented on WICKET-5953:
-----------------------------------------

Thanks for the report!

To me this is a bug in IE 11.
At https://github.com/apache/wicket/blob/7bcf9236b0fe8a86f53603c22390a75dda4fad7b/wicket-core/src/main/java/org/apache/wicket/ajax/markup/html/AjaxFallbackLink.java#L97 we (schedule a) suppress the JS event default behavior.
Apparently IE ignores it.

I have bad experience with IE bug tracker. I have filled bugs before but they never answered.

I'd recommend you to not use AjaxFallbackLink. Current days all devices support JS and if a user decides to disable JS then almost every site will break.

> AjaxFallbackLink triggers both the JS/AJAX request and the fallback link request on touchscreen in IE11
> -------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-5953
>                 URL: https://issues.apache.org/jira/browse/WICKET-5953
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 7.0.0-M6
>         Environment: Windows 8, Internet Explorer 11, touchscreen (Surface Pro 3)
>            Reporter: Tero Tarkkala
>            Priority: Minor
>         Attachments: myproject.zip
>
>
> Attached quickstart demonstrates the behaviour. Refreshing the container is there just to limit the amount of network calls on the log. Without the container refreshing the whole page is reloaded.
> Same environment but using a mouse to click the link doesn't exhibit the symptoms, so the bug is probably related to how IE exposes touch events to JS. Tested also on Chrome on the same platform, which works normally (only the ajax call to IBehaviorListener is triggered).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)