Home and newtab weather widget fetch might need a retry feature
Categories
(Firefox :: New Tab Page, enhancement)
Tracking
()
People
(Reporter: thecount, Assigned: thecount)
References
(Blocks 1 open bug)
Details
(Whiteboard: [hnt])
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
If the weather fetch fails, we don't try again until the next system tick/update.
We can add some retry logic that runs before waiting for the next system tick/update.
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
[Tracking Requested - why for this release]: We intend to launch a weather experiment in 127. It should be a low risk, small set of changes.
If the weather data fetch fails a retry is very likely to work, and would reduce the number of errors the user sees. After retrying 3 times if we still don't have a successful response, then we should display the error.
Updated•1 year ago
|
Comment 2•1 year ago
|
||
The bug is marked as tracked for firefox127 (beta). However, the bug still isn't assigned.
:amy, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 3•1 year ago
|
||
I think we're ok if this doesn't make it in, but it may be easy and we may get time this week. If so we might consider taking it.
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Comment 4•1 year ago
|
||
Comment 7•1 year ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Assignee | ||
Comment 8•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D214314
Updated•1 year ago
|
Comment 9•1 year ago
|
||
beta Uplift Approval Request
- User impact if declined: Should stop some errors for users during an experiment
- Code covered by automated testing: yes
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: Hard to test errors for this, but more so what's important is some regression tests on a new profile still displays the weather widget on newtab
- Risk associated with taking this patch: Low
- Explanation of risk level: Just a few lines, adding a loop, in a preffed off feature
- String changes made/needed: None
- Is Android affected?: no
Updated•1 year ago
|
Updated•1 year ago
|
Comment 10•1 year ago
|
||
uplift |
Updated•1 year ago
|
Comment 11•1 year ago
|
||
I have verified this issue on the latest Firefox RC 128.0 (Build ID: 20240701154223) and the latest Nightly 129.0a1 (Build ID: 20240703213305) on Windows 10x64, macOS 14.4.1 and Linux Mint 20.1 x64.
In order to verify this I have used the following scenarios.
- On new profiles, I have disabled the internet connection and the "Weather data is not available right now" error is correctly displayed. After enabling the internet connection and a check is performed the weather is correctly displayed.
- Using a VPN, I have changed the location multiple times to verify that the weather is correctly displayed.
- I have disabled/enabled multiple times the Weather feature from the settings menu from the New Tab page, and the weather was correctly displayed each time.
Description
•