1780396 - The download speed for "Good 2G" listed in the table on firefox-source-docs.mozilla.org is wrong

Status: RESOLVED FIXED

(DevTools :: Documentation, defect, P3)

Description

[Calin Tanase]

Attachment: Good 2G - download speed.png

Environment:
Operating system: Windows 10
Firefox version: 104.0a1 (2022-07-19) (64-bit)

Steps to reproduce:

1. Go to https://firefox-source-docs.mozilla.org/devtools-user/network_monitor/throttling/index.html
2. Scroll down until the table is reached
3. 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:

1. Screenshot provided

Comment 1

[Julian Descottes [:jdescottes]]

Probably a typo in the docs, in the source we use 450kbps

Comment 2

[Julian Descottes [:jdescottes]]

Attachment: Bug 1780396 - [devtools] fix typo in docs for devtools throttling speeds

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/f6ce6dcc7da8
[devtools] fix typo in docs for devtools throttling speeds r=nchevobbe

Comment 4

[Andreea Pavel [:apavel]]

https://hg.mozilla.org/mozilla-central/rev/f6ce6dcc7da8

Comment 5

[Ardelean Oana, Desktop QA [:oardelean]]

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.

Comment 6

[Julian Descottes [:jdescottes]]

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

[Ardelean Oana, Desktop QA [:oardelean]]

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.