av9ash/GitBugs huggingface dataset:
Bug: Google Meet unexpectedly crops video
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-10-27 09:37:25+00:00
Resolved: 2022-07-27 23:19:24+00:00

It intermittently crops the top-left portion of video, especially when any user turns on/off their video output.

I've seen the issue on Nightly 84 with fission, on Windows 10 19042.
Bug: I need to login several times on wordpress. This issue is ONLY with the latest Firefox 82.0, and not found in Chrome, Safari or other browsers
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-10-27 09:41:39+00:00
Resolved: 2020-10-28 17:40:45+00:00

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

Steps to reproduce:

login to Wordpress in Firefox


Actual results:

On wp-admin page I do enter the login and password.


Expected results:

I should have been logged in permanently, but now I am returned to the login page, and entering again, I get a message that the login is ERROR. I can now Back my firefox and I am IN... This conflict with Wordpress login only occurs in Firefox and Wordpress, so it must be a conflict with Firefox and Wordpress.
Bug: Should use radio items instead of checkboxes in Bookmarks Toolbar visibility submenu
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2020-10-27 09:45:42+00:00
Resolved: 2020-11-25 16:11:27+00:00

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

Steps to reproduce:

The Bookmark Toolbar now has the option to only be shown in a New Tab. The settings for this is located in the Menu Bar under View > Toolbars > Bookmarks Toolbar. Only one option of the three can be selected at a time but the checkbox buttons suggest you can untick the selected option to deselect.

Instead Radio buttons could be used to clearly show only one option is available like it is done in the View > Page Style menu.
Bug: Black spots showing in the browser area
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-10-27 10:56:18+00:00
Resolved: 2020-11-17 08:07:29+00:00

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

Steps to reproduce:

Scrolling through pages creates black spots in the browser.


Actual results:

Black spots are showing.


Expected results:

Black spots should not appear.
Bug: Print Previewing Screenshots renders inconsistencies accross platforms while saving to PDF or Printer Destination
Status: RESOLVED
Priority: P3
Resolution: WORKSFORME
Created: 2020-10-27 11:19:53+00:00
Resolved: 2024-05-09 19:50:48+00:00

**Affected versions**
* 83.0b4
* 84.0a1

**Affected platforms**
* Windows 10x64
* macOS 10.15.7
* Ubuntu 20.04

**Steps to reproduce**
1. Launch FF.
2. Go to any random website(eg: wikipedia.com)
3. Right click the page and select Screenshot
4. Drag the margin of the Screenshot UI and select an area.
5. CTRL+P
6. Select Print to PDF.

**Expected result**
* Only the selected screenshot area should be displayed inside the print preview.

**Actual results**
* Save to PDF mode:
* On macOS , the selected area is displayed as the first page, and the rest of the document follows in the next pages in full. 
* on Ubuntu the same behavior as above is applied.
* On Windows, the whole page is displayed, with the shadow effect and UI of the Screenshot tool and the entirety of the document, disregarding the selection entirely

*Printer destination:
* On macOS, the whole page is displayed, with the shadow effect and UI of the Screenshot tool and the entirety of the document, disregarding the selection entirely
* On Ubuntu the same behavior as above is applied
* On Windows, the whole page is displayed, with the with the shadow effect and UI of the Screenshot tool , but only the selection page is displayed

**Suggested Severity**
*  Seeing as how this occurs on all platforms, and it does concern a functionality that is easy to use by the user without any workarounds, I would S2 this issue.

**Regression range**
* Will return with regression ASAP.

**Additional notes**
* I would consider that the correct behavior would be that only the selected range to be displayed inside the print preview, without the rest of the document of the page for both Save to PDF or Printer destination.
* This issue occurs on the old modal as well.
* Screen cast of the issue: 
https://drive.google.com/file/d/1URtHJIp6eZ7L4pSRVO2aqLtkH04APhUj/view?usp=sharing
Bug: Outreachy contribution to HTTPS-Only
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-10-27 12:59:56+00:00
Resolved: 2020-10-27 14:11:28+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36

Steps to reproduce:

I tried visiting this site http://speedofanimals.com 


Actual results:

It was showing HTTPS-Only Mode alert


Expected results:

It was supposed 
to show the site
Bug: macOS - print to PDF does not open certain PDF file content
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2020-10-27 13:01:53+00:00
Resolved: 2021-12-15 14:54:26+00:00

**Affected versions**
* 82.0.1, 83.0b4

**Affected platforms**
* macOS 10.15;

**Steps to reproduce**
1. Launch Firefox, open the attached PDF file;
2. Press CTRL+P;
3. Save as PDF;
4. Open the Saved file in a new tab;

**Expected result**
* file content is open;

**Actual result**
* file open is empty;
* quick check on Chrome throws "File might be corrupted" error message;

**Regression range**
* pinpointing the regression range was difficult as; in some cases, a page refresh  or waiting 10-ish seconds appeared to solve everything even on other 3rd party apps(Chrome).
* last good: 2020-09-11;
* first bad: 2020-09-12;
* Pushlog [URL](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=641fc4c5c561f68a153f729d62661d9a2d462bfe&tochange=48f10c4139655c2c4d52fa773f1fd760ea681d42);

**Additional notes**
* S4 as suggested severity since out of 3 machines only 1 had this issue;
* checked with Downloading the file from the UI, there are no issues;
* flipping pdfjs.renderInteractiveForms on/off has no influence over it;
* 84.0a1 (2020-10-27) appears to be unaffected;
* considering the size of the file, waited a good 30seconds+ but still nothing.
Bug: Outreachy contribution to HTTPS-Only
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-10-27 13:06:20+00:00
Resolved: 2020-10-27 14:05:20+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36

Steps to reproduce:

I tried visiting this site https://whatsappweb.com/


Actual results:

It was showing HTTPS-Only Mode alert


Expected results:

It was supposed 
to show the site
Bug: Websocket re-sending old data beginning with Firefox 82
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2020-10-27 14:14:37+00:00
Resolved: 2020-10-27 15:18:35+00:00

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

Steps to reproduce:

Beginning with Firefox 82, if multiple larger arraybuffers are sent via a WebSocket connection in a short interval, Firefox re-sends a previous arraybuffer instead of the actually selected ArrayBuffer.

This issue is newly introduced in Firefox 82, in Firefox 81 no such behaviour was listed. It seems to appear when more than 512KB are sent back-to-back. This issue is not debuggable via the DevTools (which log the data that should have been sent) but only visible in Wireshark.

This bug breaks various european speed tests run by national telecom operators that are based on https://github.com/rtr-nettest/rmbtws/ 

I've written more details of this bug on GitHub here: https://github.com/rtr-nettest/rmbtws/issues/15

A short demo demonstrating the bug can be found here: https://github.com/rtr-nettest/rmbtws/tree/firefox82-reproduce (run /test/Websockettest.html)


Actual results:

An old ArrayBuffer that was sent via `socket.sent` is sent multiple teimes


Expected results:

The actual ArrayBuffers that were sent via `socket.send` should be transmitted over the network.
Bug: Syncing of themes is a bit hit-and-miss, and different for builtin themes vs addon themes.
Status: NEW
Priority: P3
Created: 2020-10-27 14:29:52+00:00
Resolved: 2024-11-08 08:28:54+00:00

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

Steps to reproduce:

I'm using Firefox with a synced profile on multiple machines. On one of them, I wanted to change the theme to a different one (e.g. the new Alpenglow). I have disabled all of those settings keys:

services.sync.prefs.sync.extensions.activeThemeID
services.sync.prefs.sync.lightweightThemes.selectedThemeID
services.sync.prefs.sync.lightweightThemes.usedThemes


Actual results:

Firefox syncs the changed theme to all other synced instances, changing the theme on every machine.


Expected results:

I'm pretty sure that it used to work to not sync theme changes between synced machines. I used that many Firefox versions ago. It seems like a regression has been introduced, syncing the themes despite about:config saying not to do so.
Bug: Tab-to-search onboarding intervention is not localized
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-10-27 14:30:59+00:00
Resolved: 2020-10-27 15:15:04+00:00

[Affected versions]:
- Firefox 83.0b4
- Nightly 84.0a1 2020-10-26

[Affected platforms]:
- Win 10 x64

[Steps to reproduce]:
1. Open a Firefox RTL localized build
2. Perform a few searches so that search engines domains are autofilled
3. Restart the browser (this step should be optional, but I didn't see the onboarding intervention on a clean profile, at start-up)
4. Start typing "goo.." so that Tab To Search result is shown on the second line along with the onboarding message

[Expected result]:
Tab To Search onboarding message is localized.

[Actual result]:
Onboarding message is not localized, please see the attachment. 

[Regression range]:
- This issue is not a regression

[Suggested severity]:
S4
Bug: Outreachy contribution to HTTPS-Only
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2020-10-27 14:57:49+00:00
Resolved: 2021-01-08 12:47:43+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36

Steps to reproduce:

I tried visiting this site http://app.mast.io/


Actual results:

It was showing;
The account being accessed does not support http.

    HttpStatusCode: 400
    ErrorCode: AccountRequiresHttps
    RequestId : 914b7720-901e-0088-5571-acb0f4000000
    TimeStamp : 2020-10-27T14:54:37.5446051Z


Expected results:

It was supposed to open the site
Bug: The handoff to awesomebar pref set to false has no effect in private browsing mode
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2020-10-27 15:37:50+00:00
Resolved: 2020-10-27 15:54:18+00:00

**Suggested severity**
* S2

**Affected versions**
* Fx84.0a1
* Fx83.0b4

**Affected platforms**
* Win 10 x64
* Ubuntu 18.04

**Steps to reproduce**
1. Launch Firefox beta.
2. Open a private browsing window.
3. Click inside the websearch bar (middle of the window).
4. Start typing something.

**Expected result**
* A drop-down with search suggestions is opened beneath the websearch bar.

**Actual result**
* The search is handed off to the awesome bar (address bar).

**Regression range**
* This is not a regression, as I could reproduce the issue all the way back to Fx67.0b3 when the websearch was introduced in Private Browsing.

**Additional notes**
* The "browser.newtabpage.activity-stream.improvesearch.handoffToAwesomebar" is set to false by default in beta builds.
* Websearch is not handed off to awesomebar in normal browsing windows.
Bug: When searching by urlbar in Korean, last word is ignored when length of last word is even
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2020-10-27 15:50:05+00:00
Resolved: 2020-12-18 20:48:29+00:00

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

Steps to reproduce:

While using Korean IME, the last character is highlighted with blue or white background to notify that more vowels or consonants might be combined with this letter. The error occurs when typing search query word with Korean in urlbar while last word highlighted, pressing enter. It only happens on narrow condition. The condition can be reproduced only when:
0) As described, the last word should be highlighted by Korean IME. Copy & paste Korean words does not reproduce the bug.

1) The search query word should include space
ex) "한국어위키"(X), "한국어 위키"(O)
"한국서버"(X), "한국 서버"(O)

2) The last word's length of the search query should be even. Words in odd length seems to have no problem so far.
ex) "한국어 파이썬"(X), "한국어 자바스크립트"(O)

3) The last word does not require to be in combined form. Typing only ㅁ or ㅏ or anything can reproduce it. 
ex) "ㅁㄴㅇㄹ ㅇㅇㅇㅇ"(O), "ㅁㅁㅁㅁ ㅁㅁ"(O)


Actual results:

The highlighted word is ignored, and the the query word is sent without the last letter.
ex) "한국어 위키" -> "한국어 위"
"자바스크립트 강좌" -> "자바스크립트 강"
"파이썬 알고리즘" -> "파이썬 알고리"
"ㅁㄴㅇㄹ ㅇㅇㅇㅇ" -> "ㅁㄴㅇㄹ ㅇㅇㅇ"
"ㅁㅁㅁㅁ ㅁㅁ" -> "ㅁㅁㅁㅁ ㅁ"

The symptom also occurs whatever language is located before. 
"javascript 구문" -> "javascript 구"


Expected results:

The search query should be sent with highlighted last word
Bug: Intermittent browser/base/content/test/protectionsUI/browser_protectionsUI_categories.js | application terminated with exit code -6
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2020-10-27 16:55:59+00:00
Resolved: 2021-01-19 14:31:39+00:00

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

---
```
[task 2020-10-27T16:33:09.985Z] 16:33:09     INFO - TEST-START | browser/base/content/test/protectionsUI/browser_protectionsUI_categories.js
[task 2020-10-27T16:33:29.237Z] 16:33:29     INFO - TEST-PASS | browser/base/content/test/protectionsUI/browser_protectionsUI_categories.js | Should have blocked protections-popup-category-fingerprinters - 
[task 2020-10-27T16:33:29.238Z] 16:33:29     INFO - Buffered messages finished
[task 2020-10-27T16:33:29.238Z] 16:33:29    ERROR - TEST-UNEXPECTED-FAIL | browser/base/content/test/protectionsUI/browser_protectionsUI_categories.js | application terminated with exit code -6
[task 2020-10-27T16:33:29.238Z] 16:33:29     INFO - runtests.py | Application ran for: 0:01:11.986543
[task 2020-10-27T16:33:29.239Z] 16:33:29     INFO - zombiecheck | Reading PID log: /tmp/tmpnyBwoIpidlog
[task 2020-10-27T16:33:29.239Z] 16:33:29     INFO - ==> process 1521 launched child process 1541
[task 2020-10-27T16:33:29.240Z] 16:33:29     INFO - ==> process 1521 launched child process 1584
[task 2020-10-27T16:33:29.240Z] 16:33:29     INFO - ==> process 1521 launched child process 1602
[task 2020-10-27T16:33:29.244Z] 16:33:29     INFO - ==> process 1521 launched child process 1668
[task 2020-10-27T16:33:29.244Z] 16:33:29     INFO - ==> process 1521 launched child process 1696
[task 2020-10-27T16:33:29.245Z] 16:33:29     INFO - ==> process 1521 launched child process 1731
[task 2020-10-27T16:33:29.245Z] 16:33:29     INFO - ==> process 1521 launched child process 1762
[task 2020-10-27T16:33:29.246Z] 16:33:29     INFO - zombiecheck | Checking for orphan process with PID: 1696
[task 2020-10-27T16:33:29.246Z] 16:33:29     INFO - zombiecheck | Checking for orphan process with PID: 1602
[task 2020-10-27T16:33:29.247Z] 16:33:29     INFO - zombiecheck | Checking for orphan process with PID: 1731
[task 2020-10-27T16:33:29.247Z] 16:33:29     INFO - zombiecheck | Checking for orphan process with PID: 1668
[task 2020-10-27T16:33:29.247Z] 16:33:29     INFO - zombiecheck | Checking for orphan process with PID: 1541
[task 2020-10-27T16:33:29.247Z] 16:33:29     INFO - zombiecheck | Checking for orphan process with PID: 1762
[task 2020-10-27T16:33:29.248Z] 16:33:29     INFO - zombiecheck | Checking for orphan process with PID: 1584
[task 2020-10-27T16:33:29.248Z] 16:33:29     INFO - Stopping web server
[task 2020-10-27T16:33:29.248Z] 16:33:29     INFO - Stopping web socket server
[task 2020-10-27T16:33:29.248Z] 16:33:29     INFO - Stopping ssltunnel
[task 2020-10-27T16:33:29.264Z] 16:33:29  WARNING - leakcheck | refcount logging is off, so leaks can't be detected!```
Bug: Crash in [@ AsyncShutdownTimeout | quit-application-granted | AboutHomeStartupCache: Writing cache]
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2020-10-27 19:28:21+00:00
Resolved: 2022-04-09 15:00:46+00:00

1 installation (OS X 10.12)

Maybe Fission related. (DOMFissionEnabled=1)


Crash report: https://crash-stats.mozilla.org/report/index/d27f47b6-89d8-4cc8-b39c-5dcf60201027

MOZ_CRASH Reason: ```MOZ_CRASH()```

Top 10 frames of crashing thread:
```
0 libmozglue.dylib mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:33
1 XUL NS_DebugBreak xpcom/base/nsDebugImpl.cpp:435
2 XUL nsDebugImpl::Abort xpcom/base/nsDebugImpl.cpp:134
3 XUL NS_InvokeByIndex 
4 XUL XPCWrappedNative::CallMethod js/xpconnect/src/XPCWrappedNative.cpp:1142
5 XUL XPC_WN_CallMethod js/xpconnect/src/XPCWrappedNativeJSOps.cpp:925
6 XUL js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:598
7 XUL Interpret js/src/vm/Interpreter.cpp:3336
8 XUL js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:635
9 XUL js::Call js/src/vm/Interpreter.cpp:680
```
Bug: One-off search engines in the search bar don't switch correctly when in private mode
Status: NEW
Priority: P3
Created: 2020-10-27 20:33:23+00:00
Resolved: 2020-11-04 13:54:10+00:00

**[Sugested Severity:]**
S3

**[Description:]**
when you set an engine as a default search engine from the context menu, the icon representing the search engine which was set as default is NOT replaced by the icon of the old default search engine. So we end up with two icons of the new search engine.

**[Steps:]**
1. Open Firefox with a new profile.
2. Enable the search bar
3. Open a private window
4. Go to baidu.com and add it as a one-off
5. Open a new tab
6. Type something in the search bar
7. From the context menu click "Set as default search engine". 

**[Actual result:]**
The icon representing the search engine that was set as default is NOT replaced by the icon of the old default search engine. So we end up with two icons of the new search engine.
See the attached video.
 
**[Expected result:]**
The icon representing the search engine which was set as default should be replaced by the previous search engine's icon

**[Notes:]**
This has happened for over a year.
Bug: WNPanel devtools "Open What's New Panel" and "Render Selected Messages" buttons aren't working
Status: RESOLVED
Priority: P1
Resolution: DUPLICATE
Created: 2020-10-27 21:00:38+00:00
Resolved: 2020-11-18 15:29:34+00:00

The refactor of ASRouter caused a couple workarounds we were using to access the What's New Panel in devtools to break. I'll fix them here.
Bug: The existence of the XPCSHELL_TEST_PROFILE_DIR variable breaks a couple of features
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2020-10-27 21:15:21+00:00
Resolved: 2022-03-11 11:55:51+00:00

* no Telemetry in the Browser Console for Activity Stream
* no Normandy debug information in the Browser Console
* no access to the Multiprocess Browser Toolbox
Bug: Intermittent <something> | uncaught exception - ReferenceError: ok is not defined at mockTransferCallback@chrome://mochitests/content/browser/browser/base/content/test/general/
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2020-10-27 21:23:53+00:00
Resolved: 2021-03-15 06:08:15+00:00

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

---
```
[task 2020-10-27T17:57:15.034Z] 17:57:15     INFO - TEST-START | browser/base/content/test/general/browser_search_discovery.js
[task 2020-10-27T17:57:15.115Z] 17:57:15     INFO - TEST-INFO | started process screencapture
[task 2020-10-27T17:57:15.201Z] 17:57:15     INFO - TEST-INFO | screencapture: exit 0
[task 2020-10-27T17:57:15.201Z] 17:57:15     INFO - Buffered messages logged at 17:57:15
[task 2020-10-27T17:57:15.201Z] 17:57:15     INFO - Entering test bound 
[task 2020-10-27T17:57:15.202Z] 17:57:15     INFO - Test search discovery
[task 2020-10-27T17:57:15.202Z] 17:57:15     INFO - Buffered messages finished
[task 2020-10-27T17:57:15.202Z] 17:57:15     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/general/browser_search_discovery.js | uncaught exception - ReferenceError: ok is not defined at mockTransferCallback@chrome://mochitests/content/browser/browser/base/content/test/general/browser_save_video_frame.js:39:7
[task 2020-10-27T17:57:15.202Z] 17:57:15     INFO - MTFC_onStateChange@chrome://mochitests/content/browser/toolkit/content/tests/browser/common/mockTransfer.js:46:27
[task 2020-10-27T17:57:15.202Z] 17:57:15     INFO - DownloadListener/makeClosure/<@chrome://global/content/contentAreaUtils.js:133:22
[task 2020-10-27T17:57:15.202Z] 17:57:15     INFO - 
[task 2020-10-27T17:57:15.202Z] 17:57:15     INFO - Stack trace:
[task 2020-10-27T17:57:15.203Z] 17:57:15     INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:simpletestOnerror:2089
[task 2020-10-27T17:57:15.203Z] 17:57:15     INFO - chrome://global/content/contentAreaUtils.js:DownloadListener/makeClosure/<:133
[task 2020-10-27T17:57:15.203Z] 17:57:15     INFO - GECKO(1313) | JavaScript error: chrome://mochitests/content/browser/browser/base/content/test/general/browser_save_video_frame.js, line 39: ReferenceError: ok is not defined
[task 2020-10-27T17:57:15.203Z] 17:57:15     INFO - Not taking screenshot here: see the one that was previously logged```