Opened 14 years ago
Closed 8 years ago
#2408 closed defect (wontfix)
Escape key in browser kills cometd connection
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | high | Milestone: | future |
Component: | DojoX Cometd | Version: | 0.4.1 |
Keywords: | cometd comet | Cc: | |
Blocked By: | Blocking: |
Description (last modified by )
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 14 years ago by
comment:2 Changed 14 years ago by
Milestone: | 0.4.2 → 0.9 |
---|
comment:3 Changed 13 years ago by
Milestone: | 0.9 → 1.1 |
---|
comment:4 Changed 13 years ago by
Status: | new → assigned |
---|
comment:6 Changed 13 years ago by
Component: | Events → DojoX Cometd |
---|---|
Description: | modified (diff) |
comment:7 Changed 13 years ago by
Milestone: | 1.2 → future |
---|---|
Owner: | changed from alex to anonymous |
Status: | assigned → new |
comment:8 Changed 13 years ago by
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 10 years ago by
Owner: | anonymous deleted |
---|
comment:10 Changed 8 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
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: http://cometd.org/
If you capture the escape keydown event, and return false, this fixes the problem. This event should probably be captured in the cometd code.