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 2014/06/20 21:09:26 UTC

[jira] [Comment Edited] (WICKET-5624) Do not throw when WebSocket is not supported

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

Martin Grigorov edited comment on WICKET-5624 at 6/20/14 7:09 PM:
------------------------------------------------------------------

The suggestion is applied!
The event name is "/websocket/notsupported" (or Wicket.Event.Topic.WebSocket.NotSupported)
Thanks!


was (Author: mgrigorov):
The suggestion is applied!
Thanks!

> Do not throw when WebSocket is not supported
> --------------------------------------------
>
>                 Key: WICKET-5624
>                 URL: https://issues.apache.org/jira/browse/WICKET-5624
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-native-websocket
>    Affects Versions: 6.15.0
>            Reporter: Andrei Badea
>            Assignee: Martin Grigorov
>             Fix For: 7.0.0-M3, 6.17.0
>
>
> When the browser does not support WebSocket, /wicket-websocket-jquery.js throws an "is not supported" string from the initialize() method, which runs in the DOM ready event. This break any other initialization of the page that takes place after the WebSocket initialization, leading to less than graceful degradation of functionality.



--
This message was sent by Atlassian JIRA
(v6.2#6252)