Open
Bug 1421357
Opened 7 years ago
Updated 2 years ago
Throttle simulation does not throttle websockets
Categories
(DevTools :: Netmonitor, enhancement, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: domoritz, Unassigned)
References
(Blocks 2 open bugs)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.59 Safari/537.36 Steps to reproduce: Simulate a bad network with https://blog.nightly.mozilla.org/2016/11/07/simulate-slow-connections-with-the-network-throttling-tool/. Then load an application that loads a lot of data over a websocket and see whether the speed is affected. Actual results: The websocket connection appears to not be throttled. Note that Chrome has a similar limitation: https://bugs.chromium.org/p/chromium/issues/detail?id=423246. Expected results: I'd expect the connection to be limited for websockets as well.
Updated•7 years ago
|
Component: Untriaged → Networking: WebSockets
Product: Firefox → Core
Updated•7 years ago
|
Component: Networking: WebSockets → Developer Tools: Responsive Design Mode
Product: Core → Firefox
Thanks for filing! You are correct that WebSockets is not throttled yet. At the moment, we can only throttle things that are observable to our network monitor, and at the moment, WebSockets are not shown there. I'll mark this as depending on basic WebSocket support in DevTools.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Depends on: network-websocket-inspector
Ever confirmed: true
Priority: -- → P3
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•5 years ago
|
Blocks: rdm-device
Comment 4•4 years ago
|
||
Moving this over to Honza, now that it's clear this isn't an RDM issue.
No longer blocks: rdm-device
Component: Responsive Design Mode → Netmonitor
Flags: needinfo?(bwerth) → needinfo?(odvarko)
Updated•4 years ago
|
No longer depends on: network-websocket-inspector
Flags: needinfo?(odvarko)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•