av9ash/GitBugs huggingface dataset:
Bug: The error message from the Weather widget is not displayed on the New Tab when the internet connection is blocked or when the Merino service is not available
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-05-23 13:03:03+00:00
Resolved: 2024-05-28 11:27:49+00:00

**[Affected versions]:**
- Firefox build version: Firefox Beta 127.0b5, Build ID: 20240522100816

**[Affected Platforms]:**
- Windows 10 x64
- macOS 14.5
- Ubuntu 22.04.4

**[Prerequisites]:**
- Have an en-US Firefox build installed and opened.
- Have a VPN solution connected to the US.
- Have your internet connection disconnected in order to block weather data.
- Have the "browser.newtabpage.activity-stream.system.showWeather" pref set to true.


**[Steps to reproduce]:**
1. Open a New Tab page.
2. Observe the elements displayed on the upper-left corner of the New Tab.

**[Expected result]:**
- The “Weather data is not available right now” error message is successfully displayed on the New Tab page.

**[Actual result]:**
- The “Weather data is not available right now” error message is not displayed on the New Tab page.

**[Notes]:**
- This issue is reproducible also by modifying the “browser.urlbar.merino.endpointURL” pref to an invalid value in order to simulate that the Merino service is down.
- Attaching a screen recording of the issue [here](https://drive.google.com/file/d/1r_EozGx8cguySldXxdb1p8P8r3jznshk/view?usp=sharing)

**[Regression Window]:**
- Using Mozregression tools we have found a Pushlog  [link](https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=f6f78b7bc091646b8c4d007b08141c3f0a75430f&tochange=2ddf8cad7d283dc27a53f18caa3e002f641908df). 
- From this Pushlog link it seems that Bug1896182(https://bugzilla.mozilla.org/show_bug.cgi?id=1896182) may have introduced this behavior.
Bug: Icon / buttons in sidebar launcher are wonky / duplicated with sidebar.revamp=true
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-05-23 13:45:40+00:00
Resolved: 2024-07-01 14:08:42+00:00

Fairly sure this broke in the last 24-48h.

There are also errors in the browser console:

```
Uncaught TypeError: can't access property "assignedNodes", this.slotEl is null
    checkForLabelText chrome://global/content/elements/moz-button.mjs:89
    handleEvent chrome://global/content/vendor/lit.all.mjs:2031
2 moz-button.mjs:89:5
    checkForLabelText chrome://global/content/elements/moz-button.mjs:89
    handleEvent chrome://global/content/vendor/lit.all.mjs:2031
```

(this may be a reusable components change that broke this...)
Bug: New Tab - Two "add shortcuts" tile appear at start
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-05-23 16:12:07+00:00
Resolved: 2024-06-03 16:42:50+00:00

When opening Firefox 126.0 (64-bit) in Windows, I see new tab with two "add shortcut" tiles. 
One is the real "add shortcut" tile, and the second one is a Wikipedia tile when I click on it.

After opening a new tab again, or opening a new window, this issue is not there anymore. Only when Firefox starts.

Expected behavior:
- User opens Firefox
- Only see one tile " add shortcut"
Bug: amazon.fr/amazon.de aren't understood by analysis-explainer code; fills in "retailer" which isn't localized
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2024-05-23 17:15:54+00:00
Resolved: 2024-06-19 14:56:57+00:00

This code:

https://searchfox.org/mozilla-central/rev/a44891c52387ca4bd7c35b50f0d335f3980ef36a/browser/components/shopping/content/analysis-explainer.mjs#87-104
```js
// It turns out we must always return a non-empty string: if not, the fluent
// resolver will complain that the variable value is missing. We use the
// placeholder "retailer", which should never be visible to users.
getRetailerDisplayName() {
  let defaultName = "retailer";
  if (!this.productUrl) {
    return defaultName;
  }
  let url = new URL(this.productUrl);
  let hostname = url.hostname;
  let displayNames = {
    "www.amazon.com": "Amazon",
    "www.bestbuy.com": "Best Buy",
    "www.walmart.com": "Walmart",
  };
  return displayNames[hostname] ?? defaultName;
}

```

inserts the retailer name in this string: https://searchfox.org/mozilla-central/rev/a44891c52387ca4bd7c35b50f0d335f3980ef36a/browser/locales/en-US/browser/shopping.ftl#154-158 .

At a minimum, this needs to add `amazon.fr` and `de` to the `displayNames`, though ideally we need to figure out a fallback solution that does use translation. That would need some templating changes to use a different string (without a substitute `$retailer` variable) if we cannot recognize the retailer name.
Bug: Places Window ("All Downloads") initially shows up white even when using the dark theme, causing a flashing appearance
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-05-23 19:07:12+00:00
Resolved: 2024-06-10 19:13:46+00:00

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

Steps to reproduce:

1. Open Firefox
2. Open All Downloads

This only happens the first time it is opened after opening Firefox


Actual results:

Loading window was white


Expected results:

Loading window should be dark in dark mode
Bug: Intermittent browser/components/translations/tests/browser/browser_translations_select_telemetry_translation_failure_ui.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: FIXED
Created: 2024-05-23 19:31:22+00:00
Resolved: 2024-06-10 20:29:46+00:00

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

---
```
TEST-PASS | browser/components/translations/tests/browser/browser_translations_select_telemetry_translation_failure_ui.js | Expected select-translations-panel-to selection to match 'en' - 
[task 2024-05-23T18:41:27.984Z] 18:41:27     INFO - Buffered messages finished
[task 2024-05-23T18:41:27.985Z] 18:41:27     INFO - TEST-UNEXPECTED-FAIL | browser/components/translations/tests/browser/browser_translations_select_telemetry_translation_failure_ui.js | Uncaught exception in test bound test_select_translations_panel_telemetry_translation_failure_ui - undefined - timed out after 200 tries.
[task 2024-05-23T18:41:27.985Z] 18:41:27     INFO - Leaving test bound test_select_translations_panel_telemetry_translation_failure_ui
[task 2024-05-23T18:41:27.986Z] 18:41:27     INFO - GECKO(3433) | MEMORY STAT | vsize 3700MB | residentFast 515MB | heapAllocated 304MB
[task 2024-05-23T18:41:27.986Z] 18:41:27     INFO - TEST-OK | browser/components/translations/tests/browser/browser_translations_select_telemetry_translation_failure_ui.js | took 24764ms
[task 2024-05-23T18:41:27.987Z] 18:41:27     INFO - Not taking screenshot here: see the one that was previously logged
[task 2024-05-23T18:41:27.988Z] 18:41:27     INFO - TEST-UNEXPECTED-FAIL | browser/components/translations/tests/browser/browser_translations_select_telemetry_translation_failure_ui.js | Found an unexpected tab at the end of test run: https://example.com/browser/toolkit/components/translations/tests/browser/translations-tester-select.html - 
[task 2024-05-23T18:41:27.988Z] 18:41:27     INFO - GECKO(3433) | [Child 9665, Main Thread] WARNING: NS_ENSURE_TRUE(mDoneSetup) failed: file /builds/worker/checkouts/gecko/editor/composer/nsEditingSession.cpp:1163
[task 2024-05-23T18:41:27.989Z] 18:41:27     INFO - GECKO(3433) | [Child 3693: Main Thread]: I/DocShellAndDOMWindowLeak ++DOCSHELL 7f4610d5c400 == 1 [pid = 3693] [id = 83]
[task 2024-05-23T18:41:27.989Z] 18:41:27     INFO - GECKO(3433) | [Child 3693: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 165 (7f460fb2b200) [pid = 3693] [serial = 250] [outer = 0]
[task 2024-05-23T18:41:27.990Z] 18:41:27     INFO - GECKO(3433) | [Child 3693: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 166 (7f4610d5c800) [pid = 3693] [serial = 251] [outer = 7f460fb2b200]
[task 2024-05-23T18:41:28.020Z] 18:41:28     INFO - checking window state
[task 2024-05-23T18:41:28.120Z] 18:41:28     INFO - TEST-START | browser/components/translations/tests/browser/browser_translations_select_telemetry_unsupported_language_ui.js
```
Bug: [Returning Users] Refresh Firefox Infobar shouldn't display on first startup after a user refreshes their profile
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-05-23 20:35:07+00:00
Resolved: 2024-11-22 11:56:42+00:00

Refresh Firefox infobar shows up on about:welcome for users reinstalling Firefox. Considering we are showing user option to reset profile settings in installer, we should avoid duplicate action by showing Refresh Firefox infobar again during first run.

STR
1. On latest windows, delete Firefox app from 'Add or Remove Program'
2. Install Firefox keeping 'Restore default profile settings..' checkbox checked

Actual Result
Firefox opens with  Refresh infobar showing on about:welcome

Expected result:
Refresh infobar should not show on about:welcome

Additional Notes:
1. Click of Refresh Firefox resets pref and  unenrolls user if enrolled in 'aboutwelcome' or other firstrun Nimbus experiments

https://searchfox.org/mozilla-central/rev/010ccb86d48fa23b2874d1a7cbe6957ec78538c3/browser/components/BrowserGlue.sys.mjs#1884
https://searchfox.org/mozilla-central/source/browser/components/BrowserGlue.sys.mjs#1583
Bug: Persist sidebar attributes when window closed with sidebar open and reopened
Status: NEW
Priority: P3
Created: 2024-05-23 21:11:18+00:00
Resolved: 2024-07-21 17:35:30+00:00

As part of the sidebar revamp, the following bugs sought to move persistence of the sidebar from XULStore to SessionStore (Bug 1892033, Bug 1885894). This persists for every scenario except when a window with only "new tab" and an open sidebar is closed.

An attempt was made to rectify this in this Diff: https://phabricator.services.mozilla.com/D207787?id=866201. The blocks of code from this Diff relevant to the new tab fix specifically are as follows:

1. SessionStore.js:
```
initializeWindow(aWindow, aInitialState = null)) {
...
        } else if (closedWindowState?.sidebar?.command) {
          this.restoreSidebar(aWindow, closedWindowState.sidebar);
        }
      }
      // we actually restored the session just now.
      this._prefBranch.setBoolPref("sessionstore.resume_session_once", false);
    } else if (
      this._closedWindows.length &&
      aWindow.toolbar.visible &&
      !isPrivateWindow
    ) {
      // If we still haven't restored a window, but a sidebar exists, restore.

      // default to the most-recently closed, non-popup, window
      let closedWindowState = this._closedWindows.find(w => !w.isPopup);

      // Always restore sidebar if present in previously closed window
      if (closedWindowState?.sidebar?.command) {
        this.restoreSidebar(aWindow, closedWindowState.sidebar);
      }
    }
...
}
```

2. SessionStore.js:
```
// If sidebar command is truthy, i.e. sidebar is open, store sidebar settings
      let shouldStore =
        hasSaveableTabs || isLastWindow || winData.sidebar?.command;
```

3. The above fixes solved the problem but resulted in`browser/base/content/test/sidebar/browser_sidebar_persist.js` failing due to `onSidebarShown` being called prior to the `SidebarShown` event. Removing the below code from `ext-menus.js` fixed this without breaking any intended behaviour:
```
    await window.SidebarController.promiseInitialized;

    if (
      !window.closed &&
      window.SidebarController.currentID === "viewBookmarksSidebar"
    ) {
      menuTracker.onSidebarShown({ currentTarget: sidebarHeader });
    }
```

--------

However, this resulted in `browser/base/content/test/sidebar/browser_sidebar_adopt.js` failing due to the sidebar being adopted from the most recently closed window rather than the initial window. 

-------

We should revisit this fix and find a better solution for restoring the sidebar when a window is opened and closed without breaking current tests.
Bug: Firstname field accepts special charactor
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2024-05-24 07:36:12+00:00
Resolved: 2024-05-24 08:11:07+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36

Steps to reproduce:

1.Login
2.Enter special character in first name field



Actual results:

1.First name field accepts special character


Expected results:

1.First name field should not accepted
Bug: The Configuration View menu of the Weather widget is auto-dismissed after another element from the New Tab page is focused
Status: NEW
Priority: --
Created: 2024-05-24 07:55:06+00:00
Resolved: 2024-06-25 19:30:58+00:00

**[Affected versions]:**
- Firefox build version: Firefox Beta 127.0b5, Build ID: 20240522100816

**[Affected Platforms]:**
- Windows 10 x64
- macOS 14.5
- Ubuntu 22.04.4

**[Prerequisites]:**
- Have an en-US Firefox build installed and opened.
- Have a VPN solution connected to the US.
- Have the "browser.newtabpage.activity-stream.system.showWeather" pref set to true.


**[Steps to reproduce]:**
1. Open a New Tab page.
2. Focus any element from the New Tab page.
3. Click the Configuration View menu of the Weather widget.
4. Observe the behavior.

**[Expected result]:**
- The Configuration View menu of the Weather widget is successfully opened and it isn't auto-dismissed from the New Tab page.

**[Actual result]:**
- The Configuration View menu of the Weather widget is opened and quickly auto-dismissed after another element from the New Tab page is focused.

**[Notes]:**
- This issue is also reproducible by clicking outside of the browser.
- Attaching a screen recording of the issue.
Bug: Full page screenshot of JIRA tickets with scroll bars gets cut off
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-05-24 08:59:53+00:00
Resolved: 2024-05-29 15:12:13+00:00

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

Steps to reproduce:

1. Go to a ticket in JIRA (e.g. story/bug) that is large enough to need a scroll bar  (afraid I don't know any public ones)
2. Try to to take a full screen screen shot e.g. cmd-shift-s, click on 'full screen'


Actual results:

Screen shot cut off at point of which it falls of the screen (see attached, notice how can see top of a comment but not the rest)


Expected results:

Expected screen shot tool to scroll down and so full page screen shot is captured
Bug: Intermittent browser/base/content/test/permissions/browser_temporary_permissions_navigation.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2024-05-24 10:06:23+00:00
Resolved: 2025-02-17 12:01:54+00:00

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

---
```
[task 2024-05-24T08:35:31.914Z] 08:35:31     INFO - TEST-PASS | browser/base/content/test/permissions/browser_temporary_permissions_navigation.js | {"state":0,"scope":"{SitePermissions.SCOPE_PERSISTENT}"} deepEqual {"state":0,"scope":"{SitePermissions.SCOPE_PERSISTENT}"} - 
[task 2024-05-24T08:35:31.914Z] 08:35:31     INFO - Buffered messages logged at 08:34:03
[task 2024-05-24T08:35:31.914Z] 08:35:31     INFO - TEST-PASS | browser/base/content/test/permissions/browser_temporary_permissions_navigation.js | {"state":0,"scope":"{SitePermissions.SCOPE_PERSISTENT}"} deepEqual {"state":0,"scope":"{SitePermissions.SCOPE_PERSISTENT}"} - 
[task 2024-05-24T08:35:31.915Z] 08:35:31     INFO - Leaving test bound testTempPermissionOnReload
[task 2024-05-24T08:35:31.916Z] 08:35:31     INFO - Entering test bound testTempPermissionOnReloadAllTabs
[task 2024-05-24T08:35:31.916Z] 08:35:31     INFO - Buffered messages finished
[task 2024-05-24T08:35:31.917Z] 08:35:31     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/permissions/browser_temporary_permissions_navigation.js | Test timed out - 
[task 2024-05-24T08:35:31.918Z] 08:35:31     INFO - GECKO(6176) | Completed ShutdownLeaks collections in process 5560
[task 2024-05-24T08:35:31.918Z] 08:35:31     INFO - TEST-START | Shutdown
[task 2024-05-24T08:35:31.919Z] 08:35:31     INFO - Browser Chrome Test Summary
[task 2024-05-24T08:35:31.920Z] 08:35:31     INFO - Passed:  169
[task 2024-05-24T08:35:31.920Z] 08:35:31     INFO - Failed:  1
[task 2024-05-24T08:35:31.921Z] 08:35:31     INFO - Todo:    0
[task 2024-05-24T08:35:31.921Z] 08:35:31     INFO - Mode:    e10s
[task 2024-05-24T08:35:31.922Z] 08:35:31     INFO - *** End BrowserChrome Test Results ***
```
Bug: Firefox fails to relaunch after closing the browser during active DLP request
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-05-24 11:54:19+00:00
Resolved: 2024-05-31 13:42:39+00:00

**Found in**
* 128.0a1 (2024-05-23)

**Affected versions**
* 128.0a1 (2024-05-23)

**Preconditions**
* Download the DLP test assets from https://drive.google.com/file/d/1yjqVRuxdKV3WnO7D2wzMgDXBuYBxUgVw/view 
* Create a distribution folder inside the Firefox folder and paste the policies-1.json to it and then rename it to policies.json

**Tested platforms**
* Affected platforms: Windows 10/11
* Unaffected platforms:Ubuntu 22.04, macOS 12.6.6

**Steps to reproduce**
1. Navigate to yahoo.com
2. Open up a document in an external program (for example Notepad) and type “sample text” into it and copy it
3. Return to Firefox and paste the “sample text” into the search bar at the top of the page
4. After the “You’re not permitted to paste this content” dialog is shown, quit the browser without interacting with the dialog
5. Open Firefox again and observe the behavior

**Expected result**
* Firefox is successfully launched

**Actual result**
* Firefox does not launch 

**Regression range**
* This is not a regression as this is a new feature

**Additional notes**
* See the attached video
* After quitting Firefox while the message is displayed, it remains active as a background process for a few minutes (can be checked in Task Manager) 
* Reproducing if repeating the steps while the DLP agent is also running
* Not reproducing if attempting to relaunch Firefox after it is no longer running in the background 
* Also, after managing to launch the browser, it seems that a silent crash occurred due to the performed actions: 
-- https://crash-stats.mozilla.org/report/index/d7a0bd5d-8dd9-4add-a30c-606660240524  
-- https://crash-stats.mozilla.org/report/index/9d4ccdc0-94d0-4c38-9694-276110240524
Bug: Firefox is freezing after resizing the window while DLP request is in progress
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-05-24 12:28:38+00:00
Resolved: 2024-05-30 07:43:54+00:00

**Found in**
* 128.0a1 (2024-05-23)

**Affected versions**
* 128.0a1 (2024-05-23)

**Preconditions**
* Download the DLP test assets from https://drive.google.com/file/d/1yjqVRuxdKV3WnO7D2wzMgDXBuYBxUgVw/view 
* Create a distribution folder inside the Firefox folder and paste the policies-1.json to it and then rename it to policies.json
* Have the sample DLP agent running (open a command prompt ( not a Powershell prompt!) in the directory where content_analysis_sdk_agent.exe is located and run the command: .\content_analysis_sdk_agent.exe --user --toblock=.*\d{3}-?\d{2}-?\d{4}.* --towarn=.*warn.* --delays=10)

**Tested platforms**
* Affected platforms: Windows 10/11
* Unaffected platforms:Ubuntu 22.04, macOS 12.6.6

**Steps to reproduce**
1. Navigate to https://support.mozilla.org/ 
2. Open up a document in an external program (for example Notepad) and type “123456789” into it and copy it
3. Return to Firefox and paste the “123456789” into the search bar in the middle of the page
4. While the scan is still in progress, continuously resize the window to its minimum size
5. Wait for the scan to finish and observe the behavior

**Expected result**
* Firefox is not freezing after resizing the window while the scan is in progress

**Actual result**
* Firefox is freezing after resizing the window while the scan is in progress, causing the entire desktop to become unresponsive

**Regression range**
* This is not a regression as this is a new feature

**Additional notes**
* This is an S2 issue because the entire desktop becomes unresponsive, and the user is able to use the device only after opening Task Manager (Ctrl+Alt+Delete). Also, the browser needs to be closed from Task Manager. 
* See the attached video
* Sometimes, the above steps might need to be repeated 2-3 time to trigger the issue, but after that, it is reproducible every time
* Also, closing the browser from Task Manager will sometimes generate a silent crash (as mentioned in Bug 1898718): 
– https://crash-stats.mozilla.org/report/index/95355402-58ac-400c-8887-b20100240524
Bug: Moving the tab to a new window while the scan is ongoing will make the page unresponsive
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-05-24 12:49:05+00:00
Resolved: 2024-09-11 11:05:53+00:00

**Found in**
* 128.0a1 (2024-05-23)

**Affected versions**
* 128.0a1 (2024-05-23)


**Tested platforms**
* Affected platforms: Windows 10x64, Windows 11
* Unaffected platforms: Ubuntu 23, macOS 

**Preconditions**
* Download the DLP test assets from https://drive.google.com/file/d/1yjqVRuxdKV3WnO7D2wzMgDXBuYBxUgVw/view
* Create a distribution folder inside the Firefox folder and paste the policies-1.json to it and then rename it to policies.json
* run the DLP agent in CMD using: .\content_analysis_sdk_agent.exe --user --toblock=.*\d{3}-?\d{2}-?\d{4}.* --towarn=.*warn.* --delays=10

**Steps to reproduce**
1. Copy some random text in the clipboard and open https://en.wikipedia.org/wiki/Main_Page.
2. Paste the text and while the scan is ongoing choose to `Move the tab in a new window`.

**Expected result** 
* The scan message is displayed in the new window and the content of the page is responsive.

**Actual result**
* The message disappears and no interaction can be made with the content of the page.



**Regression range**
* Not a regression. New implementation.

**Additional notes**
* Attached a screen recording.
* This happens when drag and dropping the tab to a new window as well.
Bug: Duplicating a tab while a DLP request is active prevents the page from loading
Status: NEW
Priority: --
Created: 2024-05-24 12:54:25+00:00
Resolved: 2024-06-18 19:39:53+00:00

**Found in**
* 128.0a1 (2024-05-23)

**Affected versions**
* 128.0a1 (2024-05-23)

**Preconditions**
* Download the DLP test assets from https://drive.google.com/file/d/1yjqVRuxdKV3WnO7D2wzMgDXBuYBxUgVw/view 
* Create a distribution folder inside the Firefox folder and paste the policies-1.json to it and then rename it to policies.json

**Tested platforms**
* Affected platforms: Windows 10/11
* Unaffected platforms:Ubuntu 22.04, macOS 12.6.6

**Steps to reproduce**
1. Navigate to yahoo.com
2. Open up a document in an external program (for example Notepad) and type “sample text” into it and copy it
3. Return to Firefox and paste the “sample text” into the search bar at the top of the page
4. Duplicate the tab without interacting with the “You’re not permitted..” dialog
5. Open the duplicated tab and observe the behavior

**Expected result**
* yahoo.com webpage is loading

**Actual result**
* yahoo.com webpage is not loading

**Regression range**
* This is not a regression as this is a new feature

**Additional notes**
* See the attached video
* The page is loading after dismissing the dialog from the first tab
* Also reproducing while the sample DLP agent is running