av9ash/GitBugs huggingface dataset:
Bug: Anchor, re-click/scroll not working
Status: RESOLVED
Priority: P3
Resolution: DUPLICATE
Created: 2020-10-13 19:37:22+00:00
Resolved: 2020-11-05 10:44:24+00:00

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0

Steps to reproduce:

Open a url with an anchor (#), for example: https://www.npmjs.com/package/ws#websocket-compression.


Actual results:

Firefox scrolls to the anchor, but can scroll to it agian.

Scroll on the webpage up/down, click on the URL bar and hit enter, nothing happens.

Same as when you click on the same anchor link again.
The anchor needs to changed to be working again.


Expected results:

Scroll to the anchor in the URL again.
Bug: Force Installed extensions don't repair if removed from outside of firefox
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-10-13 19:52:20+00:00
Resolved: 2020-10-14 20:32:58+00:00

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

Steps to reproduce:

Use Enterprise Policy Extension Settings to Force Install an Extension: ID

`rm -rf ~/Library/Application\ Support/Firefox/Profiles/2egnzcky.default-esr/extensions/ID.xpi`

Firefox shows the extension as still installed.


Actual results:

Firefox shows the extension as installed and prevents a way to reinstall it or repair it.


Expected results:

Firefox should see that the extension itself is missing from the user profile and reinstall the required extension
Bug: Can't Login using Firebase Auth
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-10-13 20:13:23+00:00
Resolved: 2020-10-14 12:32:55+00:00

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

Steps to reproduce:

I tried to put in credentials


Actual results:

Your email was badly formatted


Expected results:

It should take my credentials and put it in the Firebase Firestore.
Bug: Default font selection doesn't scroll, goes offscreen
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-10-13 21:52:38+00:00
Resolved: 2020-10-13 22:14:32+00:00

STR:

about:preferences > General > Language and Appearance > Default Font
(Also applies to the selection under Advanced...)

Clicking on the dropdown shows a very large dropdown that displays to the top of the content area and off the bottom of the window.  And the screen.  There is no scroll bar.  The mouse wheel does nothing.  Using arrow keys causes the selection to disappear off screen.

I get to about E, and I've a pretty large screen.
Bug: Why is Firefox increasingly not accessible?
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-10-14 01:35:59+00:00
Resolved: 2020-10-18 02:51:49+00:00

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

Steps to reproduce:

This is not a bug like that. My issue is that it seems as I install newer updates, FF is increasingly not accessible. I have a significant visual impairment. I thought FF was going to remove the "hamburger" because screen readers don't know what to do with that. Nor do they know what to do with three horizontal or vertical dots. It's also become harder to get bookmarks to show, but that's not an accessibility issue. Your menu items are not in the font I chose for FF to use as a default. They are much smaller. 


Actual results:

I cannot always figure out what to do because of features that my screen reader does not understand.


Expected results:

No hamburgers. No rows or column of dots. Or, at the very least, provide an opotion to change to only words instead of these other options.
Bug: Three dot ellipsis is blurry on hover for a split second on about new:tab
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-10-14 08:30:44+00:00
Resolved: 2020-10-15 06:23:23+00:00

*Affected versions*
* 83.0a1 (20201013094053)
* 82.0 (20201012131351)
* 81.0.2 (20201012085804)

*Affected platforms*

* Windows 10x64
* Ubuntu 18.04
* macOS 10.12

*Steps to reproduce*
1. Open Firefox with a new profile and a new tab.
2. Hover over a random item Top Sites section multiple times.
3. Observe the three-dot ellipsis.

*Expected result*
* The three-dot ellipsis is displayed as expected.

*Actual result*
* The three-dot ellipsis is blurry for a split second when shown. See [here](https://drive.google.com/file/d/1Liyr-hVUuu2kN55h_h7mpHuahOv0npGO/view?usp=sharing) how it first shows.

*Regression range*
* Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=598d441e4ebaa93ab098d266035a396057c82129&tochange=6cbf1430a66ef5aa5f066ed77677f47ea44fc0e1 

*Notes*
* Attached a screen recording.
* From what I saw the issue is intermittent sometimes and is not reproducible every time while hovering over a random item. It needs some hovers in order to trigger.
* If opening a Nightly with a new profile the issue is reproducible from the first time for me at least while having `browser.search.region: RO` and hovering over the Top Sites items.
* The issue can be reproduced on every Highlights cards, Recommended by pocket cards and Top Sites. 


**Suggested Severity: S4**
Bug: Searchbar menu not dismissed after pressing Change Search Settings if triggered from overflow menu
Status: NEW
Priority: P5
Created: 2020-10-14 10:03:38+00:00
Resolved: 2020-10-14 11:59:50+00:00

**Affected versions**
* 82.0, 83.0a1(2020-10-08);

**Affected platforms**
* Windows 10, macOS 11.0;

**Steps to reproduce**
1. Launch Firefox;
2. Customize and add Search bar and some other items between megabar-searchbar;
3. Resize browser so that >> buttons displayed;
4. Click on the >> button;
5. Click inside the SearchBar and type any character;
6. Click on the Change Search Settings button;

**Expected result**
* about:preferences#search page loaded and any (overflow) menu is dismissed;

**Actual result**
* overflow menu remains in view;

**Regression range**
* will check and provide one asap;

**Additional notes**
* issue does not reproduce if browser is maximized;
* attached recording with the issue;
* S4 as suggested severity.
Bug: Pressing Enter in the URL sometimes does nothing
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-10-14 12:14:26+00:00
Resolved: 2020-10-15 01:16:16+00:00

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

Steps to reproduce:

0. Close all opened instances of Firefox
1. Open Firefox
2. Press CTRL-D (address bar's default address will be highlighted)
3. Type "mai"
4. "mail.google.com/" will appear (in my case)
5. Press Enter




Actual results:

Default address will remain the same and "mail.google.com" will not be loaded.


Expected results:

Always the address should be loaded on which I pressed Enter.
Bug: Group field missing for Messaging System reach ping
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2020-10-14 12:56:45+00:00
Resolved: 2022-01-21 17:20:40+00:00

The `group` property of messages that come from experiments was accidentally removed in bug 1656502. This is required for filtering which types of messages should send a reach ping.
Bug: Instagram Stories aren't loading with HTTP 3 enabled
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2020-10-14 14:36:38+00:00
Resolved: 2020-10-15 12:55:51+00:00

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

Steps to reproduce:

- Enable HTTP 3 (network.http.http3.enabled)
- Open instagram.com (and log in)
- Open a user story

(retry with HTTP 3 disabled to verify)


Actual results:

A loading indicator at the top appears but the story never shows.

Looking at the DevTools, it shows a request to `https://www.instagram.com/stories/{username}?__a=1` which loads infinitely. On reloading the page, the request status changes to `301 - Moved`, indicating a redirect.

This is in fact the behaviour spotted with HTTP 3 disabled (and on Chrome); this request redirects to `https://www.instagram.com/stories/{username}/?__a=1` (notice the last slash).



Expected results:

The story loads and shows.
Bug: Include event sources in telemetry events sent by new tab section menus.
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2020-10-14 14:56:47+00:00
Resolved: 2020-11-17 09:52:25+00:00

`MENU_COLLAPSE` and `MENU_EXPAND` events from newtab are not segmented based on where they are originated (for eg. highlights, top_sites, etc).
Bug: Always HTTPS mode breaks POST requests on insecure websites
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-10-14 14:57:26+00:00
Resolved: 2020-11-11 11:12:09+00:00

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Steps to reproduce:

1. Go to insecure website with POST form
2. Submit the form


Actual results:

I have been shown insecure warning, then same form after accepting the risk (not submitted)


Expected results:

This form should have been submitted
Bug: Set aria-activedescendant upon selecting a tab-to-search result if the user's previous action wasn't typing
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2020-10-14 17:16:50+00:00
Resolved: 2023-06-02 15:20:09+00:00

Following the work in bug 1647929, we don't set aria-activedescendant to tab-to-search results when the user presses tab to select them. This is because the result is announced to screen readers when the user is typing and we don't want to announce it twice. However, Marco pointed out in [this](https://phabricator.services.mozilla.com/D93451#3009739) review comment that we don't handle the edge case where the user Tabs through all the results and eventually ends up back at the tab-to-search result. Or if the user passes the tab-to-search result then Shift+Tabs back up to it. We should set aria-activedescendant in these cases, since we didn't recently announce the result to the user.
Bug: Vendor in UniFFI runtime
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2020-10-14 17:51:57+00:00
Resolved: 2022-02-22 17:10:14+00:00

Right now, we're using uniffi_build, which is a hack, and may not even be working.  Need to chat with :eoger to understand what the various issues are and what makes the most sense to do.
Bug: Intermittent TV browser/components/preferences/tests/browser_media_control.js | Test timed out - | Found a tab after previous test timed out: about:preferences#general
Status: RESOLVED
Priority: P5
Resolution: FIXED
Created: 2020-10-14 18:34:13+00:00
Resolved: 2020-10-14 20:03:00+00:00

**Filed by:** rmaries [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer.html#?job_id=318626135&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/eRF1P74ESI21EIeH2yiEDQ/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/eRF1P74ESI21EIeH2yiEDQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---
```
[task 2020-10-14T17:23:55.877Z] 17:23:55     INFO - TEST-START | browser/components/preferences/tests/browser_media_control.js
[task 2020-10-14T17:25:26.514Z] 17:25:26     INFO - Buffered messages finished
[task 2020-10-14T17:25:26.514Z] 17:25:26     INFO - TEST-UNEXPECTED-FAIL | browser/components/preferences/tests/browser_media_control.js | Test timed out - 
[task 2020-10-14T17:25:26.514Z] 17:25:26     INFO - GECKO(1621) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2020-10-14T17:25:26.515Z] 17:25:26     INFO - GECKO(1621) | MEMORY STAT | vsize 7599MB | residentFast 317MB | heapAllocated 127MB
[task 2020-10-14T17:25:26.515Z] 17:25:26     INFO - TEST-OK | browser/components/preferences/tests/browser_media_control.js | took 90629ms
[task 2020-10-14T17:25:26.515Z] 17:25:26     INFO - Not taking screenshot here: see the one that was previously logged
[task 2020-10-14T17:25:26.515Z] 17:25:26     INFO - TEST-UNEXPECTED-FAIL | browser/components/preferences/tests/browser_media_control.js | Found a tab after previous test timed out: about:preferences#general - 
[task 2020-10-14T17:25:26.591Z] 17:25:26     INFO - GECKO(1621) | [Parent 1621, Main Thread] WARNING: '!inner', file /builds/worker/checkouts/gecko/dom/ipc/jsactor/JSWindowActorProtocol.cpp:172
[task 2020-10-14T17:25:26.591Z] 17:25:26     INFO - GECKO(1621) | [Parent 1621, Main Thread] WARNING: '!inner', file /builds/worker/checkouts/gecko/dom/ipc/jsactor/JSWindowActorProtocol.cpp:172
[task 2020-10-14T17:25:26.681Z] 17:25:26     INFO - GECKO(1621) | [Child 1623: Main Thread]: I/DocShellAndDOMWindowLeak ++DOCSHELL 0x104960800 == 1 [pid = 1623] [id = 1]
[task 2020-10-14T17:25:26.681Z] 17:25:26     INFO - GECKO(1621) | [Child 1623: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 1 (0x104809480) [pid = 1623] [serial = 5] [outer = 0x0]
[task 2020-10-14T17:25:26.681Z] 17:25:26     INFO - GECKO(1621) | [Child 1623: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 2 (0x10bc50000) [pid = 1623] [serial = 6] [outer = 0x104809480]
[task 2020-10-14T17:25:26.732Z] 17:25:26     INFO - checking window state```
Bug: PDF bank statement will not open
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2020-10-14 19:06:00+00:00
Resolved: 2021-12-11 11:30:23+00:00

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

Steps to reproduce:

I logged into my Tesco BAnk Account and clicked on a link to open a .pdf bank statement.
This has only happened since the Firefox update of 13tH October 2020.
The problem does not occur in Microsoft Edge.
This is a Windows 10 x64 PC with all windows updates installed.


Actual results:

A new tab opened, but the immediately closed.


Expected results:

A new tab should have opened the .pdf statement.
Bug: Font rendering glitch with pdf viewer
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2020-10-15 02:14:51+00:00
Resolved: 2021-02-08 19:54:13+00:00

See:

https://www.cityofpaloalto.org/civicax/filebank/documents/8700

In the upper right corner "Purposes' has bad kerning. This looks correct in Preview.
Bug: MMPolicyBase::FindRegion fails to find a free region
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2020-10-15 02:29:41+00:00
Resolved: 2020-10-27 23:10:03+00:00

The launcher process ping shows failures with [`MMPOLICY_RESERVE_FINDREGION_VIRTUALQUERY_ERROR`](https://searchfox.org/mozilla-central/rev/9c72508fcf2bba709a5b5b9eae9da35e0c707baa/mozglue/misc/interceptor/MMPolicies.h#358).  A possible reason is that we don't scan the full range for free regions and the scanned region was too small due to a big random number generated.
Bug: WriteProcessMemory fails in FuncHookCrossProcess::CopyStubToChildProcess
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2020-10-15 02:37:50+00:00
Resolved: 2020-11-02 16:45:01+00:00

The launcher process ping shows failures with [`FUNCHOOKCROSSPROCESS_COPYSTUB_ERROR`](https://searchfox.org/mozilla-central/rev/9c72508fcf2bba709a5b5b9eae9da35e0c707baa/mozglue/misc/nsWindowsDllInterceptor.h#250).  The top win32 error in those instances is `ERROR_NOACCESS`.   A possible reason is the same as bug 1662560 that the executable was mapped onto a different address in a child process.
Bug: 'session restore' doesn't show up if browser restarts after clearing history for a day
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-10-15 07:39:21+00:00
Resolved: 2021-05-25 14:44:03+00:00

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

Steps to reproduce:

1. Browser running for more than a day; ie running time is from before midnight to after midnight.
2. Clear all history for 'Today'
3. Browser crashes.
4. Start browser; 'about:sessionrestore' is not displayed.



Expected results:

'about:sessionrestore' page should be displayed on restarting after a crash
Bug: Setting Firefox to automatically download PDF files automatically changes Applications settings to "PDF Save File"
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-10-15 07:44:59+00:00
Resolved: 2022-06-11 04:39:52+00:00

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

Steps to reproduce:

1. Go to Preferences -> Applications
2. Change Portable Document Format to Open in Firefox
3. Open a PDF in pdf.js (https://napocaro.files.wordpress.com/2015/02/david_m-_burton_elementary_number_theory_sixth_bookfi-org.pdf)
4. Download the PDF
5. A download dialog appears -> Check the box for automatically downloading PDFs -> Download the PDF
6. Check the Applications settings again.


Actual results:

The Applications settings of PDF gets automatically changed to Save File.
So, clicking on any PDF link will download it instead of opening in Firefox.
However, the user explicitly set PDFs to Open in Firefox in the Preferences.


Expected results:

This is buggy on multiple levels. 
Until now, I couldn't figure out what was happening.
No action outside of the Preferences page should change it, otherwise it loses its purpose.

Chrome behaviour is simple. Clicking any PDF link opens the PDF in its native viewer. You can then download the PDF from the native viewer and no unnecessary download dialog is shown.

The Open in Firefox Settings should not be changed when setting Firefox to automatically download PDFs in the pdf.js viewer.
Bug: Some Preferences page elements focus rings are interrupted by selecting them with Tab key
Status: NEW
Priority: P3
Created: 2020-10-15 08:15:22+00:00
Resolved: 2020-10-22 16:06:50+00:00

**Affected versions**
- Firefox 82.0
- Firefox 83.0a1

**Affected platforms**
- macOS 11
- Ubuntu 20.04
- Windows 10

**Steps to reproduce**
1. Launch Firefox
2. Access about:preferences
3. Press on Tab to highlight with the focus ring the page entire page and the options from the down-left corner

**Expected result**
- The page and options are fully covered by the focus ring

**Actual result**
- The page and options's focus rings are interrupted

**Regression range**
- I will see for a regression if there is one

**Additional notes**
- The issue can be seen in the following [attachment](https://drive.google.com/file/d/19u_-Lqxsda-NAI5UFMp3jlymDBfgpWC5/view?usp=sharing)

**Suggested severity**
- S3-S4
Bug: Search Region detection issues with system wide VPN
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-10-15 10:49:10+00:00
Resolved: 2021-03-29 17:19:50+00:00

##### [Description:]
Given a system wide VPN and also reproducible with a system wide http proxy, the browser.search.region doesn't get initialized.
I would guess that you could also achieve this kind of result with the right custom re-routing to reach this result.

##### [Environment:]
Windows 10 x 64
Ubuntu 20.04
Mac 10.13.6

Firefox 83.0a1 2020-10-14
Firefox 82RC2
Firefox 81
..
79
76.0.1
68esr

##### [Steps:]
1. Set-up a system wide VPN/ http proxy.
2. Get Fx and start it up with a new profile.
3. Open about:config and check the value for browser.search.region.


##### [Actual Result:]
browser.search.region is not found in the config.

##### [Expected Result:]
browser.search.region is initialized, although I'm uncertain what the expectancy would be here. (get the proxy/vpn region ?)

##### [Note:]
The tests were conducted with NordVPN, UrbanVPN and a http proxy.
Bug: Minor visual improvements to about:certificate
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2020-10-15 11:13:19+00:00
Resolved: 2020-10-17 16:11:39+00:00

1. For RTL, the border-radius for the tabs at the top are applied on the opposite sides:
https://searchfox.org/mozilla-central/rev/9c72508fcf2bba709a5b5b9eae9da35e0c707baa/toolkit/components/certviewer/content/components/certificate-section.css#44,48
2. Each `<list-item>` has border on the left/right side, so it's not flush with the panel
3. For RTL, some values should be LTR
Bug: [Experiment] The "Sign in" hiperlink from the about:welcome is not working while enrolled in the "msw-no-titles" branch
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-10-15 11:56:04+00:00
Resolved: 2020-10-16 10:30:21+00:00

[Affected versions]:
- Firefox Beta 82.0;

[Affected Platforms]:
- Windows 10 x64;
- Windows 8.1 x32;
- Windows 7 x64;

[Prerequisites]:
- Have a new Firefox profile created.
- Have the [User.js](https://drive.google.com/file/d/1ci9BMCsHSr9uZlsYtAGovRF7jqM3SsBY/view?usp=sharing) saved in the profile folder before opening the profile. (Note there should only be 2 files in the folder, times.json and the user.js)
- Have the Terminal opened.

[Steps to reproduce]:
1. Dag and drop the Firefox.exe in the terminal and add the "--first-startup" argument at the end.
2. Press the "Enter" key and select the new FIrefox profile created in prerquisties.
3. From the about:wlecome page click the "Sign in" hiperlink.
4. Observe the behavior. 

[Expected results]:
- The "Sign in to Firefox Sync" page is loaded.

[Actual results]:
- Nothing happens.

[Notes]:
- This issue is not reproducible when enrolled in the "treatment-deafult" branch,.
- This issue is not reproducible on the latest Nigntly 83.0a1 build with the deafult behavior.
- No errors are displayed in the browser console when clicking the "Sign in" link. Only the following message: "AboutWelcomeParent: Received content event: AWPage:TELEMETRY_EVENT AboutWelcomeParent.jsm:173".
- Unfortunatelly I didn't managed to enrolled in the experiment on Nightly 83.0a1. However, probably the issue will also reporduce on these builds. Considering this I will also set the flag to "affected" for 83. As soon as we will have the Beta 83 build availbable I will try to reproduce the issue and add a comment.
- Attached screen recording off the issue.
Bug: Intermittent browser/components/preferences/tests/browser_searchsuggestions.js | Should have flipped the private suggestion checkbox - Got false, expected true
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2020-10-15 12:33:51+00:00
Resolved: 2021-02-09 17:01:52+00:00

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

---
```
[task 2020-10-15T11:10:42.149Z] 11:10:42     INFO - TEST-PASS | browser/components/preferences/tests/browser_searchsuggestions.js | Should have updated the urlbar preference back to the original value - 
[task 2020-10-15T11:10:42.149Z] 11:10:42     INFO - Console message: [JavaScript Error: "TypeError: event.target.closest is not a function" {file: "resource:///modules/UrlbarInput.jsm" line: 2810}]
[task 2020-10-15T11:10:42.149Z] 11:10:42     INFO - _on_mousedown@resource:///modules/UrlbarInput.jsm:2810:26
[task 2020-10-15T11:10:42.149Z] 11:10:42     INFO - handleEvent@resource:///modules/UrlbarInput.jsm:415:23
[task 2020-10-15T11:10:42.149Z] 11:10:42     INFO - synthesizeMouseAtPoint@chrome://mochikit/content/tests/SimpleTest/EventUtils.js:606:13
[task 2020-10-15T11:10:42.149Z] 11:10:42     INFO - synthesizeMouse/<@resource://testing-common/BrowserTestUtilsChild.jsm:334:34
[task 2020-10-15T11:10:42.149Z] 11:10:42     INFO - wrapHandlingUserInput@resource://gre/modules/E10SUtils.jsm:1069:7
[task 2020-10-15T11:10:42.149Z] 11:10:42     INFO - synthesizeMouse@resource://testing-common/BrowserTestUtilsChild.jsm:330:15
[task 2020-10-15T11:10:42.150Z] 11:10:42     INFO - receiveMessage@resource://testing-common/BrowserTestUtilsChild.jsm:149:21
[task 2020-10-15T11:10:42.150Z] 11:10:42     INFO - 
[task 2020-10-15T11:10:42.150Z] 11:10:42     INFO - Buffered messages finished
[task 2020-10-15T11:10:42.150Z] 11:10:42     INFO - TEST-UNEXPECTED-FAIL | browser/components/preferences/tests/browser_searchsuggestions.js | Should have flipped the private suggestion checkbox - Got false, expected true```