Closed
Bug 1113046
Opened 10 years ago
Closed 5 years ago
Opening the debugger causes websockets to be closed
Categories
(DevTools :: Debugger, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: wangxianfeng, Unassigned)
Details
(Whiteboard: needs-review)
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0 Build ID: 20141217030202 Steps to reproduce: 1.User iframe load a index.html (localserver). 2.index.html use websocket to access webserver (localserver). 3.click Developer->Debugger. Actual results: websocket closed. Expected results: websocket work normally.
Updated•10 years ago
|
Component: Networking: WebSockets → Developer Tools
Product: Core → Firefox
I am able to reproduce this. e10s makes no difference here. I edited the sample to use a local HTTP address and ws://echo.websocket.org. Slightly more lengthy STR: 1. Load example's websocket.html file 2. Open the toolbox to the Console tab 3. Observe that there are logs of the websocket messages, but no "close" 4. Open the Debugger tab 5. Go back to the Console, and "close" is now logged It does not reproduce if the toolbox is already open and you reload the page. You need to start with the toolbox closed, reload, then open toolbox, and switch to the debugger to cause the problem.
Status: UNCONFIRMED → NEW
Component: Developer Tools → Developer Tools: Debugger
Ever confirmed: true
Reporter | ||
Comment 2•10 years ago
|
||
firefox OS + webide can reproduce this issue.
Updated•10 years ago
|
Summary: websocket closed by developer tool → Opening the debugger causes websockets to be closed
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•5 years ago
|
Whiteboard: needs-review
Comment 5•5 years ago
|
||
I can't reproduce the problem anymore.
Closing.
Honza
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(odvarko)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•