Opened 15 years ago

Closed 9 years ago

#2408 closed defect (wontfix)

Escape key in browser kills cometd connection

Reported by: [email protected] Owned by:
Priority: high Milestone: future
Component: DojoX Cometd Version: 0.4.1
Keywords: cometd comet Cc:
Blocked By: Blocking:

Description (last modified by alex)

On pressing the escape key in Firefox 2 (may be apparent in other browsers also) the comet connection to the server is lost, and it does not reconnect. The connection type used was the long polling HTTP POST.

Using javascript evt.preventDefault() when escape is pressed does not prevent this action... user must explicitly recall cometd.init() to reinitialize the connection

Change History (10)

comment:1 Changed 15 years ago by guest

If you capture the escape keydown event, and return false, this fixes the problem. This event should probably be captured in the cometd code.

comment:2 Changed 15 years ago by alex


comment:3 Changed 15 years ago by alex

Milestone: 0.91.1

comment:4 Changed 15 years ago by alex

Status: newassigned

comment:5 Changed 14 years ago by dylan

Milestone: 1.11.2

mass move of editor issues to 1.2.

comment:6 Changed 14 years ago by alex

Component: EventsDojoX Cometd
Description: modified (diff)

comment:7 Changed 14 years ago by dylan

Milestone: 1.2future
Owner: changed from alex to anonymous
Status: assignednew

comment:8 Changed 14 years ago by Joscha Feth

For the lazy ones:

dojo.connect(document, "onkeypress", function(e) {
    var key = e.keyCode || e.charCode;
    if (key == dojo.keys.ESCAPE) {
        return false;

comment:9 Changed 11 years ago by Chris Mitchell

Owner: anonymous deleted

comment:10 Changed 9 years ago by bill

Resolution: wontfix
Status: newclosed

The CometD library has been removed from DojoX. The CometD project now maintains its own Dojo library in AMD format as part of their project. This will be available via cpm, or may be downloaded from GitHub?. See:

Note: See TracTickets for help on using tickets.