Open
Bug 1922436
Opened 1 year ago
Updated 1 year ago
Newtab if a malformed blocked topsite pref issue
Categories
(Firefox :: New Tab Page, defect, P2)
Firefox
New Tab Page
Tracking
()
NEW
People
(Reporter: thecount, Assigned: maxx)
References
Details
(Whiteboard: [hnt])
Attachments
(1 file)
The pref "browser.topsites.blockedSponsors", if it happens to be malformed, it'll fail when we parse it and cause topsites to now show.
We don't actually know how to reproduce this yet, but we have had 1 instance of maybe it happening.
Manually changing the pref however, can trigger the issue.
I think it's worth fixing just in case, at the very least it strengthens our system a bit, but might actually be fixing an odd and old and tricky bug.
I think the solution is if the parse fails, catch it, and fallback to an empty array.
Updated•1 year ago
|
| Reporter | ||
Comment 1•1 year ago
|
||
To test:
- Set "browser.topsites.blockedSponsors" to an empty string. Don't delete it or clear it. Specifically an empty string. Can also be a space or another string that won't parse into valid json.
- Restart the browser.
- Open/refresh newtab.
Expected: should still see topsites.
Comment 2•1 year ago
|
||
The severity field is not set for this bug.
:thecount, could you have a look please?
For more information, please visit BugBot documentation.
Flags: needinfo?(sdowne)
| Assignee | ||
Updated•1 year ago
|
Assignee: nobody → mcrawford
Severity: -- → S2
Priority: -- → P2
| Assignee | ||
Updated•1 year ago
|
Flags: needinfo?(sdowne)
| Assignee | ||
Comment 3•1 year ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•