The download speed for "Good 2G" listed in the table on firefox-source-docs.mozilla.org is wrong
Categories
(DevTools :: Documentation, defect, P3)
Tracking
(firefox104 fixed)
Tracking | Status | |
---|---|---|
firefox104 | --- | fixed |
People
(Reporter: ctanase, Assigned: jdescottes)
References
()
Details
Attachments
(2 files)
Environment:
Operating system: Windows 10
Firefox version: 104.0a1 (2022-07-19) (64-bit)
Steps to reproduce:
- Go to https://firefox-source-docs.mozilla.org/devtools-user/network_monitor/throttling/index.html
- Scroll down until the table is reached
- Check the download speed listed in the table for the selection "Good 2G"
Expected Behavior:
The download speed listed in the table for the selection "Good 2G" is 500 kbps
Actual Behavior:
The download speed listed in the table for the selection "Good 2G" is 50 kbps
Notes:
- Screenshot provided
Updated•11 months ago
|
Updated•11 months ago
|
Assignee | ||
Comment 1•11 months ago
|
||
Probably a typo in the docs, in the source we use 450kbps
Assignee | ||
Comment 2•11 months ago
|
||
Updated•11 months ago
|
Assignee | ||
Updated•11 months ago
|
Assignee | ||
Updated•11 months ago
|
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f6ce6dcc7da8 [devtools] fix typo in docs for devtools throttling speeds r=nchevobbe
Comment 4•11 months ago
|
||
bugherder |
Updated•10 months ago
|
Comment 5•10 months ago
|
||
Hello,
I could not reproduce this bug on Windows 10 64-bits using the link from the Description. Would you be so kind as to verify the fix on the latest beta/nightly channels?
Thank you.
Assignee | ||
Comment 6•10 months ago
|
||
For info this is just a documentation fix, so you can't check it per channel.
https://firefox-source-docs.mozilla.org/devtools-user/network_monitor/throttling/index.html now shows 450 Kbps
for Good 2G
which is the value we use in the code. (In the source we also updated a comment, but that also can't really be tested).
Comment 7•10 months ago
|
||
Hy Julian, thanks for clarifying, appreciate it!
Since the documentation now displays the proper value on both affected and fixed builds, i think it's safe to say there's nothing actionable here for QA anymore.
Description
•