Update IPP uses of BANDWIDTH.MAX_IN_GB to be based on usageInfo
Categories
(Firefox :: IP Protection, task, P2)
Tracking
()
People
(Reporter: fchasen, Assigned: niklas, NeedInfo)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fx-vpn])
Attachments
(2 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
Anywhere we are using the constant MAX_IN_GB should be replaced by the max returned from Guardian. Currently we are using lazy.IPPProxyManager.usageInfo.max in the panel, but that won't be available until the proxy has started for the first time so we may need to use max returned with the entitlement before it.
Updated•3 months ago
|
Let's also update this hardcoded value in https://searchfox.org/firefox-main/rev/b824aa1f1416b2e3675f7561cb58f5568f4f156a/browser/components/ipprotection/IPProtectionAlertManager.sys.mjs#67.
| Assignee | ||
Updated•3 months ago
|
| Assignee | ||
Comment 2•3 months ago
|
||
| Reporter | ||
Updated•3 months ago
|
Comment 5•3 months ago
|
||
Backed out for causing bc failures @ browser_ipprotection_alert_manager.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/40cb6d51aa0b5aaf66c75e3c57bee460c627e3e9
Comment 7•2 months ago
|
||
| bugherder | ||
Comment 8•2 months ago
|
||
Is there something QA needs to verify here? Thanks!
| Reporter | ||
Comment 9•2 months ago
|
||
I don’t think so, this was just replacing the defaults for bandwidth sizes so shouldn’t be user facing.
Comment 10•2 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D284487
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Comment 11•2 months ago
|
||
| uplift | ||
Description
•