av9ash/GitBugs huggingface dataset:
Bug: Categories list box in Options window has no a11y label
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2020-10-01 03:37:52+00:00
Resolved: 2023-06-02 15:20:09+00:00

The list box of categories in the Options window (id: categories) has no label for accessibility. While the purpose of this list box might be obvious for sighted users (I guess because a sighted user can see all the categories at a glance), it isn't obvious to some screen reader users. I think aria-label="Categories" should work nicely.

Originally reported to Vispero by a JAWS user, who reported it to us.
Bug: Go Back on SSL warning page doesn't go back to blank new tab page
Status: UNCONFIRMED
Priority: P3
Created: 2020-10-01 04:27:16+00:00
Resolved: 2024-06-03 17:32:33+00:00

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

Steps to reproduce:

1. In preferences set New Windows and Tabs to Blank Page.
2. Open a new tab, blank as expected.
3. Go to an https site with a certificate issue.
4. Warning page shows up.
5. Click "Go Back (Recommended)"


Actual results:

Firefox Home page shows up, with a search bar, top sites and Pocket.


Expected results:

Blank new tab page.
Bug: Application provided engines are potentially unhidden when the region changes
Status: RESOLVED
Priority: P3
Resolution: DUPLICATE
Created: 2020-10-01 10:09:12+00:00
Resolved: 2020-12-23 21:43:26+00:00

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

Steps to reproduce:

Firefox on Windows 10 was updated to version 81. Amazon search was added to the list of my search engines in Firefox. I removed Amazon search for several times already.


Actual results:

Amazon search appears again.


Expected results:

I don't want Amazon to appear in my search engines list after I removed it.
Bug: custom search engine doesn't show up in top sites' search engine window
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2020-10-01 11:47:03+00:00
Resolved: 2023-11-16 16:04:55+00:00

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

Steps to reproduce:

My purpose is to add a custom search engine to Top Sites in new tab page. Below are the steps:

1) First I create a custom search engine (I do it by using the "add custom search engine" add-on, though I don't think that really matter)
2) Then I verify that the custom search engine shows up properly in preference and search bar.
3) Then I try to add it to top sites. I do that by clicking the "Add Search Engine" menu of Top Sites.


Actual results:

Clicking the "Add Search Engine" menu of Top Sites pops up a window containing search engines for me to select. The issue is that the custom search engine is not among them.


Expected results:

The custom search engine should show up in the window.
Bug: The old "Set browser as default" notification is no longer displayed on Beta and Nightly
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-10-01 12:00:31+00:00
Resolved: 2020-10-09 13:54:17+00:00

**[Affected versions]:**
- Nightly 83.0a1 (Build ID: 20200930214529);
- Beta 82.0b5 (Build ID: 20200929175845);

**[Affected Platforms]:**
- All Windows;
- All macOS;
- All Linux;

**[Prerequisites]:**
- Have a new clean Firefox Profile.
- The Firefox browser is NOT set as default.

**[Steps to reproduce]:**
1. Open the Firefox browser using a new profile.
2. Navigate to about:config page.
3. Set the "browser.defaultbrowser.notificationbar" to false.
4. Restart the browser.
5. Observe the behavior.

**[Expected result]:**
- The old "Set browser as default" notification is displayed.

**[Actual result]:**
- No notification is displayed.

**[Regression]:**
- The issue is not reproducible with older Nightly 82.0a1 build. Considering this using mozregression tools I have found the regression range. Here are the results:
Last good revision: 6450088b6b73ffc17c79cd7097b1bfe30d00e207
First bad revision: cf13c1eb474759c665a41294f1b5e01cfd0b66cf
Pushlog: [link](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6450088b6b73ffc17c79cd7097b1bfe30d00e207&tochange=cf13c1eb474759c665a41294f1b5e01cfd0b66cf)

From this pushlog I think the patch for Bug 1662098 introduced this behavior.

**[Notes]:**
- Not sure if the issue will still be reproducible on the late Beta builds where the old "Set browser as default" notification is set to be the default one. However, I will double-check as soon as they are available.
- However, I have also managed to reproduce the issue using the following scenarios:
	- Setting the old notification to be by default by adding the pref in prefs.js file before opening the browser with a new profile. 
	- Setting the old notification to be by default using a rollout recipe created on the Normandy stage server.
- The issue is not reproducible on Firefox 81.0 release.
- This issue will affect the experiment if the experiment will be also live on Firefox 82.0.

Jared, can you please take a look over this issue?
Bug: Page saving doesn't work properly due to mixed content blocking
Status: NEW
Priority: P3
Created: 2020-10-01 13:39:09+00:00
Resolved: 2023-03-03 09:55:19+00:00

+++ This bug was initially created as a clone of Bug #1668414 +++

Reproduce the issue on Nightly83.0a1 Windows10. 
Chrome works without failure.

Steps to reproduce:
1. Open https://developer.mypurecloud.com/forum/t/problem-with-the-transcription-of-an-interaction/8507
2. Click Accept button if Cookie Consent dialog pops up.
3. Save page as(Ctrl+S) > Web page complete > Save

Actual results:
Download failed.

Expected results:
Page is saved successfully.
Bug: [macOS] The elements from the "Saved to Pocket" doorhanger are not accessible through the "VoiceOver" screen reader
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2020-10-01 14:53:44+00:00
Resolved: 2020-11-30 19:04:17+00:00

**[Affected versions]:**
- Firefox Beta 82.0b5 - Build ID: 20200929175845
- Firefox Nightly 83.0a1 - Build ID: 20201001094020

**[Affected Platforms]:**
- macOS 10.15

**[Prerequisites]:**
- You are logged in to Pocket.
- Have the "extensions.pocket.onSaveRecs" pref set to "true" in the "about:config" page.
- Have the "VoiceOver" screen reader enabled.

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Click the "Save to Pocket" button from the right part of the "Address Bar".
3. Press any "Tab" key several times and observe the behavior.

**[Expected result]:**
- All the elements are successfully recognized by the "VoiceOver" screen reader.
	
**[Actual result]:**
- The "VoiceOver" screen reader does not recognize any element from the "Saved to Pocket" doorhanger.

**[Notes]:**
- This issue is not reproducible on Firefox Release 81.0.
Bug: Sometimes pinned tabs do not reload after browser startup
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2020-10-01 20:42:59+00:00
Resolved: 2023-01-26 19:20:04+00:00

Sometimes after launching Nightly, I find that a pinned tab that has not not fully reload. I've noticed this a few times with a pinned Spotify tab. I am not sure if the problem only occurs when the window with the pinned tab is minimized from the previous session. (Restore previous session is enabled in preferences.) I have noticed this on Nightly 83 and possibly 82. Reloading the tab works to restore the tab fully.
Bug: Pinned tab changes when typing URL
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-10-01 21:25:55+00:00
Resolved: 2020-10-02 07:58:28+00:00

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

Steps to reproduce:

Go to a pinned tab, type a new URL and press enter (or press the arrow on screen)


Actual results:

The pinned tab changes from the original site, to the URL I typed which is now pinned. So the original pinned tab is replaced.


Expected results:

Open a new tab with the URL, as this is not the pinned tab URL. Similar to the behaviour of pressing external (outside of the pinned tab URL domain) links: They also open in a new tab (which is great)
Bug: When opening Firefox it opens in a smaller box
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-10-02 00:03:00+00:00
Resolved: 2020-10-14 02:05:15+00:00

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

Steps to reproduce:

I opened Firefox.


Actual results:

Firefox opens, but in a box


Expected results:

Firefox should've opened in a window that's Maximized that fills your screen except the taskbar. Not talking about the Full-Screen mode.
Bug: The "Set browser as default" notification bar is wrongly displayed in Private Window
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2020-10-02 08:38:23+00:00
Resolved: 2020-10-30 21:24:04+00:00

[Affected versions]:
- Firefox Nightly 83.0a1 (Build ID: 20201001094020)
- Firefox Beta 82.0b5 (Build ID: 20200929175845)

[Affected Platforms]:
- Windows 10 x64
- Mac 10.15
- Ubuntu 20.04

[Prerequisites]:
- Have the Firefox browser installed.
- Have a new Firefox profile.
- The Firefox browser is NOT set as default.

[Steps to reproduce]:
1. Open the Firefox browser with the profile from prerequisites.
2. Make sure that the "Set browser as default" notification bar was not displayed in the current session.
3. Open a new private window.
4. Navigate to the “about:home” page.
5. Observe the top part of the page.

[Expected result]:
- The “Set browser as default” notification bar is not displayed.

[Actual result]:
- The "Set browser as default" notification bar is displayed under the Address bar.

[Regression]
- The issue is not reproducible with older Nightly 82.0a1 build. Considering this using mozregression tools I have found the regression range. Here are the results:
 Last good revision: 6450088b6b73ffc17c79cd7097b1bfe30d00e207
 First bad revision: cf13c1eb474759c665a41294f1b5e01cfd0b66cf
 Pushlog: link
From this pushlog I think the patch for Bug 1662098 introduced this behavior.
[Notes]:
- The issue is not reproducible on Firefox 81.0 release.
- Attached a screen recording with the issue.
Bug: [macOS] An extra “ , “ is wrongly displayed after a tag if the tag is added in the “Add Tags” field using the “ , “ character
Status: NEW
Priority: P4
Created: 2020-10-02 08:49:52+00:00
Resolved: 2020-11-02 18:39:12+00:00

**[Affected Versions]:**
- Firefox Nightly 83.0a1 (Build ID: 20201001094020)
- Firefox Beta 82.0b6 (Build ID: 20201001171107)
- Firefox Release 81.0.1 (Build ID: 20200930150533)

**[Affected Platforms]:**
- macOS 10.15.6

**[Prerequisites]:**
- Have a new profile created.
- Be logged in a Pocket account.
- Have the “browser.search.region” pref value set to “US”, “CA”, or “GB”.

**[Steps to reproduce]:**
1. Start the Firefox Browser with the profile from prerequisites.
2. Open a “New Tab” page and click on one of the “Recommended by Pocket” cards.
3. Click the “Save to Pocket” button located on the right side of the “Address Bar”.
4. Click inside the “Add Tags” field.
5. Write “pocket”, press the “ , “ key from the keyboard, and observe the “Add Tags” field

**[Expected results]:**
- Only the “pocket” tag and the text caret are displayed in the “Add Tags” field.

**[Actual results]:**
- An extra “ , “ is displayed after the newly added tag.

**[Notes]:**
- The issue is not reproducible on Windows or Linux.
- Attached a screen recording of the issue.
Bug: CSS 'all' shorthand makes SVG child elements forget various HTML attributes
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-10-02 10:11:55+00:00
Resolved: 2020-10-02 12:54:46+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. In HTML, create an inline SVG
2. In CSS, select the children of the SVG
3. Set the `all` shorthand to one of the global values (`inherit`, `initial`, `unset`)


Actual results:

Multiple SVG children elements don't show up or are not drawn as specified by their HTML attributes (color, fill, stroke, etc.).

Reduced test case: https://jsfiddle.net/1c2t7o8n/


Expected results:

The SVG children elements are visible and drawn as specified by their HTML attributes.
Bug: Security: Access to Gmail account cookies and website spoofing
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-10-02 10:32:36+00:00
Resolved: 2024-05-30 17:19:21+00:00

Steps:

1- The user is instructed to select the Gmail access icon and drag it to the favorites bar.
2- The user clicks and accesses his account
3- With a double click the javascript code is executed and the Gmail session cookies are intercepted and the web page can also be impersonated.
This information could be captured from the attacker's domain.

Video is attached.
PoC: https://www.finanser.es/test/gmail.html

Mozilla Firefox Version 81.0.1 (64-bit)
Bug: Revise message for [Allow users to delete their data when signing out]
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-10-02 10:48:34+00:00
Resolved: 2020-10-02 14:24:39+00:00

**Affected versions**
* 82.0b5, 83.0a1;

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

**Steps to reproduce**
1. Launch Firefox, sync with a valid account;
2. Click on userIMG -> Account Settings;
3. Click to Sign out;

**Expected result**
* clear message;

**Actual result**
* check attached image;

**Regression range**
* last good: 2020-08-19;
* first bad: 2020-08-20;
* Pushlog: [URL](https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b0888d07df690ed43df31a2b013d12464b183a30&tochange=8cb700c12bd3acfdef56ce084c87d64fa4daae03);
* mozregression points towards: bug 1657463; 

**Additional notes**
* S4 as suggested severity;
* attached screenshot to illustrate the issue.

**Suggestions:**
* "Delete data from this device: logins, passwords, history, bookmarks, etc."
* "Delete data from this device (such as logins, passwords, history, bookmarks)."
* "Delete data from this device such as logins, passwords, history, bookmarks."
Bug: Sharing controls are always displayed on the main display with a dual screen setup
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-10-02 12:51:10+00:00
Resolved: 2020-10-06 14:04:24+00:00

**Affected versions**
- Firefox 81.0.1
- Firefox 82.0b6

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

**Pre-requisites**
- Have a dual monitor setup

**Steps to reproduce**
1. Launch Firefox and keep it in the non-main display
2. Access this [test page](https://jan-ivar.github.io/dummy/iframe_iframe_gum_starcross2.html)
3. Allow sharing video / mic

**Expected result**
- The sharing controls are visible on the display where Firefox is launched

**Actual result**
- The sharing controls are displayed on the main display

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

**Additional notes**
- The issue can be seen in the attachment
- macOS is not affected, as controls are shown in the top right bar separately
- Firefox 83.0a1 doesn't seem to be affected, as the new sharing controls will pop-up over Firefox as expected.

**Suggested severity**
- S3
Bug: If permanent private browsing is enabled, the “Save to Pocket” asks for “Log in” or “Sign up” even if the user is already logged in
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2020-10-02 13:16:56+00:00
Resolved: 2022-06-30 10:15:53+00:00

**[Affected Versions]:**
- Firefox Nightly 83.0a1 (Build ID: 20201002092536)
- Firefox Beta 82.0b6 (Build ID: 20201001171107)
- Firefox Release 81.0.1 (Build ID: 20200930150533)

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

**[Prerequisites]:**
- Have a new profile created.
- Have a valid Pocket account
- Have the “browser.search.region” pref value set to “US”, “CA”, or “GB”.
- Have the “browser.privatebrowsing.autostart” pref value set to “true”.

**[Steps to reproduce]:**
1. Start the Firefox Browser with the profile from prerequisites.
2. Open a “New Tab” page and click on one of the “Recommended by Pocket” cards.
3. Click the “Save to Pocket” button located on the right side of the “Address Bar”.
4. Click the “Log in.” button.
5. Log in with the account from prerequisites.
6. Open a “New Tab” page and click on one of the “Recommended by Pocket” cards.
7. Click the “Save to Pocket” button and observe the doorhanger.

**[Expected results]:**
- The “Saved to Pocket” doorhanger is displayed
    
**[Actual results]:**
- The “Log in/ Sign up” Pocket doorhanger is displayed.


**[Notes]:**
- The login is working for the “https://getpocket.com” website even if the permanent private browsing mode is enabled.
- Attached a screen recording of the issue.
Bug: The text cursor and chars are partially out of the text field’s view while typing tags that exceed the limit of the text field from the Pocket doorhanger
Status: NEW
Priority: P3
Created: 2020-10-02 13:45:42+00:00
Resolved: 2020-11-02 18:39:17+00:00

**[Affected versions]:**
- Firefox Nightly 83.0a1
- Firefox Beta 82.0b5
- Firefox Release 81.0.1

**[Affected platforms]:**
- Windows 10 x64
- macOS 10.15
- Ubuntu 18.04 x64

**[Prerequisites]:**
- Have the Firefox browser installed.
- You are logged into your Pocket account.

**[Steps to reproduce]:**
1. Open the Firefox browser.
2. Navigate to any website (e.g. www.wikipedia.org).
3. Click the "Save to Pocket" button from the right part of the "Address Bar".
4. Type and separate using commas as many tags as needed to reach the visible limit of the text field.
5. Type a new tag so that you exceed the limit of the text field.
6. Observe what happens next.

**[Expected result]:**
- The text cursor and chars are always visible while typing a tag.

**[Actual result]:**
- The text cursor and chars are partially out of the text field’s view.

**[Notes]:**
- Attached a screen recording of the behavior.
Bug: There is no UI notification that the user has exceeded the maximum limit of characters number of a tag if another tag is already written in the input field of the Pocket doorhanger
Status: NEW
Priority: P4
Created: 2020-10-02 13:53:26+00:00
Resolved: 2020-11-02 18:39:19+00:00

**[Affected versions]:**
- Firefox Nightly 83.0a1
- Firefox Beta 82.0b5
- Firefox Release 81.0.1

**[Affected platforms]:**
- Windows 10 x64
- macOS 10.15
- Ubuntu 18.04 x64

**[Prerequisites]:**
- Have the Firefox browser installed.
- You are logged into your Pocket account.

**[Steps to reproduce]:**
1. Open the Firefox browser.
2. Navigate to any website (e.g. www.wikipedia.org).
3. Click the "Save to Pocket" button from the right part of the "Address Bar".
4. Type a string in the tags field.
5. Press the comma “,” key.
6. Type at least 26 chars.
7. Observe the “Save” button from the right side of the text field.

**[Expected result]:**
- The “Save” button is greyed-out due to reaching the limit of the chars’ maximum number.

**[Actual result]:**
- The “Save” button is not greyed out, but actionable. 

**[Notes]:**
- The “Tags are limited to 25 characters.” warning notice is displayed only after clicking the actionable “Save” button.
- Attached a screen recording of the behavior.
Bug: Several symbols are not displayed in the drop down tags list even if they were previously saved as tags in the Pocket doorhanger
Status: NEW
Priority: P4
Created: 2020-10-02 14:03:07+00:00
Resolved: 2023-01-12 16:04:17+00:00

**[Notes]:**
- This issue is also reproducible using the following symbols: $, *, (, ) and [.
- This issue is not reproducible if the symbol is written along a string.

**[Affected versions]:**
- Firefox Nightly 83.0a1
- Firefox Beta 82.0b5
- Firefox Release 81.0.1

**[Affected platforms]:**
- Windows 10 x64
- macOS 10.15
- Ubuntu 18.04 x64

**[Prerequisites]:**
- Have the Firefox browser installed.
- You are logged into your Pocket account.

**[Steps to reproduce]:**
1. Open the Firefox browser.
2. Navigate to any website (e.g. www.wikipedia.org).
3. Click the "Save to Pocket" button from the right part of the "Address Bar".
4. Type the “+” key.
5. Press the comma “,” key and click the “Save” button.
6. Click the "Save to Pocket" button from the right part of the "Address Bar".
7. Type the “+” key and observe what happens next.

**[Expected result]:**
- The “+” tag is listed in the tags drop down list.

**[Actual result]:**
- The “+” tag is NOT listed in the tags drop down list.

**[Additional Notes]:**
- Even though the symbols are not displayed in the tags drop down list of the doorhanger, they are correctly listed in the Tags category from the Pocket account.
- Attached a screen recording of the behavior.
Bug: There are encoding issues displayed with several symbols saved as tags in the Save to Pocket doorhanger
Status: NEW
Priority: P4
Created: 2020-10-02 14:12:44+00:00
Resolved: 2020-11-02 18:39:19+00:00

**[Notes]:**
- This issue is reproducible using the following symbols: &, ', ", and >.

**[Affected versions]:**
- Firefox Nightly 83.0a1
- Firefox Beta 82.0b5
- Firefox Release 81.0.1

**[Affected platforms]:**
- Windows 10 x64
- macOS 10.15
- Ubuntu 18.04 x64

**[Prerequisites]:**
- Have the Firefox browser installed.
- You are logged into your Pocket account.

**[Steps to reproduce]:**
1. Open the Firefox browser.
2. Navigate to any website (e.g. www.wikipedia.org).
3. Click the "Save to Pocket" button from the right part of the "Address Bar".
4. Type the following string “black&white”.
5. Click the “Save” button.
6. Click the "Save to Pocket" button from the right part of the "Address Bar".
7. Type “black” and observe what happens next.

**[Expected result]:**
- The “black&white” tag is displayed in the tags drop down list.

**[Actual result]:**
- The “black`&amp;`white” tag is displayed in the tags drop down list.

**[Additional Notes]:**
- Attached a screen recording of the behavior.
Bug: Intermittent TV tier 2 browser/components/privatebrowsing/test/browser/browser_privatebrowsing_about_search_banner.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2020-10-02 14:15:02+00:00
Resolved: 2020-10-27 17:05:12+00:00

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

---
```
[task 2020-10-02T12:43:58.166Z] 12:43:58     INFO - TEST-START | browser/components/privatebrowsing/test/browser/browser_privatebrowsing_about_search_banner.js
[task 2020-10-02T12:45:07.652Z] 12:45:07     INFO - TEST-PASS | browser/components/privatebrowsing/test/browser/browser_privatebrowsing_about_search_banner.js | Should have set the shown preference to the maximum - 5 == 5 - 
[task 2020-10-02T12:45:07.652Z] 12:45:07     INFO - Leaving test bound test_show_banner_open_preferences_and_no_more
[task 2020-10-02T12:45:07.652Z] 12:45:07     INFO - Buffered messages finished
[task 2020-10-02T12:45:07.653Z] 12:45:07     INFO - TEST-UNEXPECTED-FAIL | browser/components/privatebrowsing/test/browser/browser_privatebrowsing_about_search_banner.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 2020-10-02T12:45:07.653Z] 12:45:07     INFO - GECKO(1614) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2020-10-02T12:45:07.653Z] 12:45:07     INFO - GECKO(1614) | MEMORY STAT | vsize 7629MB | residentFast 372MB | heapAllocated 171MB
[task 2020-10-02T12:45:07.653Z] 12:45:07     INFO - TEST-OK | browser/components/privatebrowsing/test/browser/browser_privatebrowsing_about_search_banner.js | took 69334ms
[task 2020-10-02T12:45:07.653Z] 12:45:07     INFO - checking window state```