av9ash/GitBugs huggingface dataset:
Bug: Flexible Spaces are taking more space in the toolbar than they used to
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2023-03-21 20:56:56+00:00
Resolved: 2023-08-28 11:55:01+00:00

STR to demonstrate this:
1. On latest Nightly, add the search bar next to the url bar, with flexible spaces surrounding them in both sides (so it will be [flexible-space][urlbar][searchbar][flexible-space])
2. Sprinkle some toolbarbuttons after the second flexible space
3. Now do the same to a pre-bug-1820534 Nightly, see that the flexible spaces take less space.

In my 24" monitor + 150% DPI, this actually causes a usability issue as the urlbar isn't wide enough to provide important url data, and dragging the splitter to widen it doesn't work, but that's a pre-existing issue.
Bug: Only update recently-closed-tabs and synced-tabs timestamps when each is actually visible
Status: RESOLVED
Priority: P2
Resolution: DUPLICATE
Created: 2023-03-21 22:22:03+00:00
Resolved: 2023-10-05 23:06:06+00:00

We call an `updateTime` function from a setInterval tick to update the displayed timestamp from e.g. "just now" to "5mins ago", or "yesterday" or whatever. That timer callback currently happens regardless of whether the firefox view tab is active, or if the list is visible or not (i.e. if the parent `<details>` element is open/closed). We should start and stop the timer when visibility changes. There are some changes in the patch on  Bug 1809661 that could be built on.
We also update the timestamps whenever the list is updated and the items re-rendered. We should stop and re-start the timer then as well, so we don't update an element which has only just been rendered. 

I ran into this in bug 1794435, but didn't want to blow up the scope of the patch to fix that ticket.
Bug: Private window's cookies leaked through Web Developer Tools in non-Private window
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-03-22 03:23:08+00:00
Resolved: 2024-06-25 02:21:51+00:00

I discovered this issue while loading a website in a private window without Web Developer Tools open, and a non-private window with the same website already loaded and Web Developer Tools open. It allows the non-private window to see the cookies that belong to the private window, and it can be used for cookie hijacking through Firefox (for example, an attacker can be recording/screencasting a non-private window with Web Developer Tools open while the victim is using a private window to login to a website with sensitive/financial information).

Steps to reproduce (I am using Firefox 111.0.1 in Windows 10 Pro 21H2)
1. Open a non-private window and a private window.
2. In the non-private window, open the Web Developers Tools and go to the Storage tab.
3. In the non-private window, open a website that stores cookies (e.g. https://www.whatarecookies.com/cookietest.asp)
4. In the non-private window Web Developer Tools, at the left column, open the cookies that are stored for that website.
5. In the private window, open the same website as before.
6. The non-private window Web Developer Console will have updated its cookies to the ones that belong to the private window.

I have attached a video showing this vulnerability.
Bug: Intermittent uriloader/exthandler/tests/mochitest/browser_download_always_ask_preferred_app.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2023-03-22 05:52:13+00:00
Resolved: 2023-08-02 12:02:14+00:00

**Filed by:** ctuns [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=409743545&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/f6tkYXsyTYmy0XvJ42QhAQ/runs/0/artifacts/public/logs/live_backing.log

---
```
[task 2023-03-22T05:15:39.309Z] 05:15:39     INFO - TEST-PASS | uriloader/exthandler/tests/mochitest/browser_download_always_ask_preferred_app.js | Should be opening the file. - 
[task 2023-03-22T05:15:39.309Z] 05:15:39     INFO - Buffered messages finished
[task 2023-03-22T05:15:39.310Z] 05:15:39     INFO - TEST-UNEXPECTED-FAIL | uriloader/exthandler/tests/mochitest/browser_download_always_ask_preferred_app.js | Should not have selected a hidden item. - 
[task 2023-03-22T05:15:39.310Z] 05:15:39     INFO - Stack trace:
[task 2023-03-22T05:15:39.311Z] 05:15:39     INFO - chrome://mochikit/content/browser-test.js:test_ok:1484
[task 2023-03-22T05:15:39.311Z] 05:15:39     INFO - chrome://mochitests/content/browser/uriloader/exthandler/tests/mochitest/browser_download_always_ask_preferred_app.js:null:18
[task 2023-03-22T05:15:39.311Z] 05:15:39     INFO - chrome://mochikit/content/browser-test.js:handleTask:1039
[task 2023-03-22T05:15:39.312Z] 05:15:39     INFO - chrome://mochikit/content/browser-test.js:_runTaskBasedTest:1111
[task 2023-03-22T05:15:39.312Z] 05:15:39     INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1253
[task 2023-03-22T05:15:39.312Z] 05:15:39     INFO - chrome://mochikit/content/browser-test.js:nextTest/<:1028
[task 2023-03-22T05:15:39.313Z] 05:15:39     INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/<:1053
[task 2023-03-22T05:15:39.313Z] 05:15:39     INFO - GECKO(11367) | JavaScript error: resource://gre/modules/HelperAppDlg.jsm, line 623: TypeError: can't access property "postShowCallback", this.dialog is null
[task 2023-03-22T05:15:39.314Z] 05:15:39     INFO - Leaving test bound 
[task 2023-03-22T05:15:39.314Z] 05:15:39     INFO - Console message: [JavaScript Error: "TypeError: can't access property "postShowCallback", this.dialog is null" {file: "resource://gre/modules/HelperAppDlg.jsm" line: 623}]
[task 2023-03-22T05:15:39.315Z] 05:15:39     INFO - initDialog/<@resource://gre/modules/HelperAppDlg.jsm:623:7
[task 2023-03-22T05:15:39.315Z] 05:15:39     INFO - setTimeout handler*initDialog@resource://gre/modules/HelperAppDlg.jsm:622:18
[task 2023-03-22T05:15:39.316Z] 05:15:39     INFO - onload@chrome://mozapps/content/downloads/unknownContentType.xhtml:1:8
[task 2023-03-22T05:15:39.316Z] 05:15:39     INFO - 
[task 2023-03-22T05:15:39.403Z] 05:15:39     INFO - GECKO(11367) | MEMORY STAT | vsize 20983603MB | residentFast 1348MB
[task 2023-03-22T05:15:39.405Z] 05:15:39     INFO - TEST-OK | uriloader/exthandler/tests/mochitest/browser_download_always_ask_preferred_app.js | took 1022ms
```
Bug: Normal windows are opened instead of Private windows if ‘Never Remember History’ is set.
Status: NEW
Priority: P3
Created: 2023-03-22 10:06:36+00:00
Resolved: 2023-06-01 10:18:21+00:00

**Found in**
* 112.0b5 (20230321175953)

**Affected versions**
* 112.0b5 (20230321175953)
* 113.0a1 (20230321213816)

**Tested platforms**
* Affected platforms: Win10, Win7, Ubuntu 20.04, Mac 10.13.
* Unaffected platforms: -

**Steps to reproduce**
1. Have FF installed on machine.
2. Go to about:preferences#privacy and set ‘Never Remember History’ under History settings.
3. Do a restart.
4. After restart, go to Hamburger menu and select to open a new private window.

**Expected result**
* Firefox Private window should be opened without issues.

**Actual result**
* Firefox Private window is opened as a normal window.

**Additional notes**
* Not a regression as the issue reproduces back to 60.0a1 (20180306220120), changing severity to S3.
* Same issue reproduces if 'Use custom setting for History' and 'Always use private browsing mode' are set also.
Bug: Pinned Tabs - Session Security Issue
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-03-22 13:16:04+00:00
Resolved: 2023-05-22 16:00:39+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/111.0

Steps to reproduce:

1) Have a pinned tab for example https://google.com. Open a new tab where log in any site.
2) Close the FireFox browser (all tabs)
3) Open FireFox again and open the previous page again too

UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/111.0


Actual results:

4) The server session keep alive.

I tested with a simple php file where I create a session and print out session_id.

If I don't have any pinned tabs:
session_id change after reopen FireFox

If I have any pinned tabs:
session_id doesn't change after reopen FireFox ($_SESSION array is still alive)



Expected results:

After I close Firefox all session must be closed whether I have a pinned tab or not!

In a public place, if someone on a foreign machine sets a pinned tab and then other person using the machine cause security issues. Because all people think if they are closed browser is equal logout.
Bug: New Shortcuts are not added to the Top Sites section if previously dismissing all the non-sponsored tiles
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-03-22 16:08:34+00:00
Resolved: 2023-03-27 15:10:41+00:00

**[Affected versions]:**
- Firefox Nightly 113.0a1 - Build ID: 20230322094136

**[Affected Platforms]:**
- Windows 10 x64
- macOS 12.4
- Linux Ubuntu 20.04 x64

**[Prerequisites]:**
- Have a VPN client connected to a US server (for people located outside the US).

**[Steps to reproduce]:**
1. Open the browser from the prerequisites.
2. Open a new tab.
3. Dismiss all the non-sponsored tiles.
4. Hover any of the empty tiles, EXCEPT the one next to the sponsored one.
5. Click the “Edit this site” button.
6. Add a site title and a valid URL on the “New Shortcut” window.
7. Click the “Add” button and observe what happens next.

**[Expected result]:**
- A new shortcut is created with the details entered in step 6.

**[Actual result]:**
- Nothing happens, the tile remains empty.

**[Regression window]:**
- This result represents the best changelog range we managed to bisect using Mozregression.
- Last good revision: 908a298d2fdd967fda1fdcd09a017952c46c4e7a
- First bad revision: 77bb7e3dc44cc54cf535e81ab2269c2a094afc0e
- Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=908a298d2fdd967fda1fdcd09a017952c46c4e7a&tochange=77bb7e3dc44cc54cf535e81ab2269c2a094afc0e
- From the pushlog above, it seems that Bug 1822604 is the one that caused this regression.

**[Notes]:**
- The issue is not reproducible using the empty tile next to the Sponsored one.
- After doing the STR above, I noticed that dismissing the Sponsored tiles as well will make the new shortcut be displayed. Also, the 2nd Sponsored tile cannot be dismissed individually, but it gets dismissed at the same time as the first Sponsored tile is dismissed.
- [Here](https://drive.google.com/file/d/10D4jKYp6SRqIwkbB8yvpl7ZHhtgt7SMl/view?usp=sharing) is a screen recording of the issue.
Bug: Intermittent browser/components/urlbar/tests/browser/browser_UrlbarInput_searchTerms_telemetry.js | single tracking bug
Status: NEW
Priority: P5
Created: 2023-03-22 16:54:35+00:00
Resolved: 2024-09-30 06:38:26+00:00

**Filed by:** imoraru [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=409792974&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Atn3T_m4S2m-B6ESS5e6dw/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Atn3T_m4S2m-B6ESS5e6dw/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---
```
[task 2023-03-22T16:08:59.909Z] 16:08:59     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_UrlbarInput_searchTerms_telemetry.js | "undefined" == "undefined" - 
[task 2023-03-22T16:08:59.909Z] 16:08:59     INFO - Leaving test bound popup_not_in_urlbar
[task 2023-03-22T16:08:59.909Z] 16:08:59     INFO - Buffered messages finished
[task 2023-03-22T16:08:59.910Z] 16:08:59     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_UrlbarInput_searchTerms_telemetry.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - 
[task 2023-03-22T16:08:59.910Z] 16:08:59     INFO - GECKO(1794) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2023-03-22T16:08:59.910Z] 16:08:59     INFO - GECKO(1794) | MEMORY STAT | vsize 16017MB | residentFast 301MB | heapAllocated 133MB
[task 2023-03-22T16:08:59.911Z] 16:08:59     INFO - TEST-OK | browser/components/urlbar/tests/browser/browser_UrlbarInput_searchTerms_telemetry.js | took 57888ms
[task 2023-03-22T16:08:59.911Z] 16:08:59     INFO - checking window state
[task 2023-03-22T16:08:59.911Z] 16:08:59     INFO - GECKO(1794) | Completed ShutdownLeaks collections in process 1794
[task 2023-03-22T16:08:59.911Z] 16:08:59     INFO - TEST-START | Shutdown
[task 2023-03-22T16:08:59.912Z] 16:08:59     INFO - Browser Chrome Test Summary
[task 2023-03-22T16:08:59.912Z] 16:08:59     INFO - Passed:  94
[task 2023-03-22T16:08:59.912Z] 16:08:59     INFO - Failed:  1
[task 2023-03-22T16:08:59.912Z] 16:08:59     INFO - Todo:    0
[task 2023-03-22T16:08:59.913Z] 16:08:59     INFO - Mode:    e10s
[task 2023-03-22T16:08:59.913Z] 16:08:59     INFO - *** End BrowserChrome Test Results ***
```
Bug: Top_picks contextual telementry is not logged
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2023-03-22 19:52:44+00:00
Resolved: 2023-03-28 17:48:03+00:00

**Found in**
* 112.0b2

**Affected versions**
* 113.0a1
* 112.0b2
* 111.0
* 110.0

**Tested platforms**
* Affected platforms: Windows 10, Mac 13, Ubuntu 22.04


**Preconditions**
- VPN connected to US
- `browser.urlbar.resultMenu` set to `true`
- `browser.urlbar.quicksuggest.blockingEnabled` set to `true`
- `browser.urlbar.merino.endpointURL` to `https://merinopy.services.mozilla.com/api/v1/suggest` 
- `browser.urlbar.merino.providers` to `adm,top_picks`
- `browser.urlbar.bestMatch.enabled` to `true`
- `browser.search.region` to `US`
- `browser.urlbar.quicksuggest.dataCollection.enabled` to `true`
- `browser.urlbar.bestMatch.blockingEnabled` to `true`
- `browser.ping-centre.log` to `true`

**Steps to reproduce**
1. Open precondition profile.
2. Open browser console
3. Type `dell` into address bar
4. From the Top_picks suggestion line, click more options and choose Learn More.
4'. From the Top_picks suggestion line, click more options and choose Dismiss.

**Expected result**
* In browser console contextual ping is logged for both 4 and 4' steps.

**Actual result**
* No contextual ping is logged

**Regression range**
* N/A
Uncertain if this is a regression, since AIUI there was some work done in this area and there were multiple versions of this. Additionally mozregression returns inconsistent results and yet another problem also being the fact that the Top_picks is an region based feature.

**Additional notes**
* The above ping behavior doesn't seem to be related to [Awesome Bar Result Menu](https://bugzilla.mozilla.org/show_bug.cgi?id=1789661) since either disabling the feature or trying on a build that doesn't have it still doesn't generate the expected glean ping-center telemetry.
* As an example, this is the non-sponsored contextual suggest ping:

TELEMETRY PING (contextual-services): {"experiments":{},"locale":"en-US","version":"112.0","release_channel":"be321ta","match_type":"firefox-suggest","advertiser":"wikipedia","block_id":0,"improve_suggest_experience_checked":true,"position":10,"source":"remote-settings","is_clicked":false,"context_id":"{b908afd8-e8eb-4274-968d-cd00f084ceeb}"}

TELEMETRY PING (contextual-services): {"experiments":{},"locale":"en-US","version":"112.0","release_channel":"be321ta","match_type":"firefox-suggest","advertiser":"wikipedia","block_id":0,"improve_suggest_experience_checked":true,"position":10,"source":"remote-settings","iab_category":"5 - Education","context_id":"{b908afd8-e8eb-4274-968d-cd00f084ceeb}"}
Bug: Feature Callout in PDF viewer does not point to the correct elements in full screen mode
Status: RESOLVED
Priority: P2
Resolution: INCOMPLETE
Created: 2023-03-22 20:55:29+00:00
Resolved: 2023-10-09 12:21:32+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/111.0

Steps to reproduce:

Change the "browser.pdfjs.feature-tour" pref to '{"screen":"FEATURE_CALLOUT_1_A","complete":false}', opened a PDF in Firefox 111, went to full screen mode (this also occurs if you start in full screen mode)


Actual results:

The feature callout does point to the correct icons in the PDF viewer


Expected results:

It should point to the correct icons in the PDF viewer toolbar in full screen mode.
Bug: The three-dot "..." menu and pocket button should change their look when hovered, on new-tab tiles & suggested-stories
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2023-03-22 21:17:42+00:00
Resolved: 2024-05-16 11:51:23+00:00

STR:
1. Open a new tab.
2. Hover a "Recommended by Pocket" suggested-story tile to make the pocket button and three-dot-menu show up.
3. Hover the three-dot-menu button or pocket button.

EXPECTED RESULTS:
The hovered button should change its look slightly to indicate that it's hovered, to help you know that (a) it's something you can click, and (b) it's the thing that will be activated if you click right now.

ACTUAL RESULTS:
The hovered button doesn't change its look at all, making it a little harder to tell if you're properly hovering its hit-box (e.g. if you want to click it).
Bug: Session Restore should restore even if the page in the tab opened with _blank target is still loading
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-03-22 23:33:48+00:00
Resolved: 2023-04-20 15:13:40+00:00

This is a follow-up of bug 610357.
As reported in the bug, it would be better that Session Restore restores a tab opened with _blank target even if it is still loading.
And also, in the bug, when opening a new tab with _blank target, even if it is loading, the URL will be shown to the tab title and the urlbar. Thus, as users become more aware of the currently open URL, it should be more expected that tabs will be the target of session restores.

And also, we need to consider the case of aborting reported at 1762998.
Bug: Intermittent browser/components/customizableui/test/browser_940307_panel_click_closure_handling.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2023-03-23 00:09:29+00:00
Resolved: 2023-04-18 17:04:10+00:00

**Filed by:** smolnar [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=409849832&repo=mozilla-central
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/EX9X_0UlTu2HcSqTLlHxTQ/runs/0/artifacts/public/logs/live_backing.log

---
```
INFO - TEST-START | browser/components/customizableui/test/browser_940307_panel_click_closure_handling.js
[task 2023-03-22T23:27:14.931Z] 23:27:14     INFO - TEST-INFO | started process screenshot
[task 2023-03-22T23:27:14.986Z] 23:27:14     INFO - TEST-INFO | screenshot: exit 0
[task 2023-03-22T23:27:14.986Z] 23:27:14     INFO - Buffered messages logged at 23:26:54
[task 2023-03-22T23:27:14.986Z] 23:27:14     INFO - Entering test bound plain_button
[task 2023-03-22T23:27:14.986Z] 23:27:14     INFO - Waiting for overflow button to show
[task 2023-03-22T23:27:14.986Z] 23:27:14     INFO - Checking if element has non-0 size
[task 2023-03-22T23:27:14.986Z] 23:27:14     INFO - Buffered messages finished
[task 2023-03-22T23:27:14.986Z] 23:27:14     INFO - TEST-UNEXPECTED-FAIL | browser/components/customizableui/test/browser_940307_panel_click_closure_handling.js | Uncaught exception in test bound plain_button - Panel did not hide within 20 seconds.
[task 2023-03-22T23:27:14.986Z] 23:27:14     INFO - Leaving test bound plain_button
[task 2023-03-22T23:27:14.986Z] 23:27:14     INFO - Entering test bound searchbar_in_panel
[task 2023-03-22T23:27:14.986Z] 23:27:14     INFO - Waiting for overflow button to show
[task 2023-03-22T23:27:14.986Z] 23:27:14     INFO - Checking if element has non-0 size
[task 2023-03-22T23:27:14.994Z] 23:27:14     INFO - TEST-PASS | browser/components/customizableui/test/browser_940307_panel_click_closure_handling.js | Panel should still be open 
```
Bug: [Intermittent] [Nightly] The “Sponsored” tag is no longer displayed for the Sponsored Top Sites when opening a New Firefox Window after the browser was previously restarted
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-03-23 10:24:01+00:00
Resolved: 2023-05-29 15:12:51+00:00

**[Affected versions]:**
- Firefox Nightly 113.0a1 - Build ID: 20230322211554

**[Affected Platforms]:**
- Windows 10 x64
- macOS 12.4
- Linux Ubuntu 20.04 x64

**[Prerequisites]:**
- Have a VPN client connected to a US server (for users located outside the US).

**[Steps to reproduce]:**
1. Open the browser from the prerequisites.
2. Open a new tab and make sure you have Sponsored Top Sites.
3. Restart the browser using the shortcuts (Ctrl+Shift+J then Ctrl+Alt+R).
4. Dismiss the Default browser message.
5. Press the Ctrl+N shortcut to open a New Firefox Window.
6. Observe the Sponsored Top Sites.

**[Expected result]:**
- The Top Sites display the “Sponsored” tag right under the tiles.

**[Actual result]:**
- The “Sponsored” tag is not displayed.

**[Regression window]:**
- I was able to reproduce the issue even back on the 94.0a1 Nighty build, so I assume the issue was introduced at the same time with the feature and it’s not a regression.

**[Notes]:**
- I am able to reproduce the issue only on the Nightly channel, on Beta and Release channels I did not reproduce it at all.
- I wasn’t able to reproduce the issue if closing and reopening the browser instead of restarting it through shortcuts.
- The issue is cleared if the tab is refreshed and doesn’t reproduce anymore when opening new tabs.
- [Here](https://drive.google.com/file/d/15MKIe3J3F-KGBNA_ePn5GivzalQbEfuU/view?usp=sharing) is a screen recording of the issue.
Bug: The Sponsored tile via Pocket is not displayed when opening a New Window
Status: NEW
Priority: P3
Created: 2023-03-23 14:11:26+00:00
Resolved: 2023-06-06 22:01:13+00:00

**[Affected versions]:**
- Firefox Nightly 113.0a1 - Build ID: 20230322211554

**[Affected Platforms]:**
- Windows 10 x64
- macOS 12.4
- Linux Ubuntu 20.04 x64

**[Prerequisites]:**
- Have a VPN client connected to a US server (for users located outside the US).
- Have the `nimbus.debug` pref set to `true`.

**[Steps to reproduce]:**
1. Open the browser from the prerequisites.
2. Copy and paste the following link in a new tab: 
`about:studies?optin_slug=showing-3rd-sponsored-tile-on-the-newtab-page&optin_branch=treatment&optin_collection=nimbus-preview`
3. Open a new tab and make sure you have 3 Sponsored Top Sites.
3. Press the Ctrl+N shortcut to open a New Firefox Window.
4. Observe the Sponsored Top Sites.

**[Expected result]:**
- All 3 Sponsored Top Sites are displayed.

**[Actual result]:**
- Only the 2 Sponsored Top Sites via adM are displayed, the Pocket one is not displayed.

**[Notes]:**
- I was not able to reproduce the issue on Beta 112.0b5.
- The issue is cleared if the tab is refreshed and doesn’t reproduce anymore when opening new Firefox windows.
- [Here](https://drive.google.com/file/d/1AUunGR63okDmuPRLJgW8Znpcpb0N91oh/view?usp=sharing) is a screen recording of the issue.