av9ash/GitBugs huggingface dataset:
Bug: Perma KeyError: 'template' | Site not up-to-date reason: "/builds/worker/checkouts/gecko/obj-x86_64-pc-linux-gnu/_virtualenvs/common" does not exist
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2023-02-14 10:38:50+00:00
Resolved: 2023-02-20 06:30:59+00:00

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

---
```
[task 2023-02-14T09:51:46.477Z] executing ['bash', '-cx', 'cd browser/components/newtab/content-src/asrouter/schemas && env LD_LIBRARY_PATH=${MOZ_FETCHES_DIR}/firefox \\\n    ${MOZ_FETCHES_DIR}/bin/xpcshell \\\n        -g ${MOZ_FETCHES_DIR}/firefox \\\n        -a ${MOZ_FETCHES_DIR}/firefox/browser \\\n        extract-test-corpus.js\n../../../../../../mach python -- make-schemas.py --check\n']in /builds/worker/checkouts/gecko
[task 2023-02-14T09:51:46.479Z] + cd browser/components/newtab/content-src/asrouter/schemas
[task 2023-02-14T09:51:46.479Z] + env LD_LIBRARY_PATH=/builds/worker/fetches/firefox /builds/worker/fetches/bin/xpcshell -g /builds/worker/fetches/firefox -a /builds/worker/fetches/firefox/browser extract-test-corpus.js
[task 2023-02-14T09:51:46.542Z] + ../../../../../../mach python -- make-schemas.py --check
[task 2023-02-14T09:51:47.909Z] Generating MessagingExperiment.schema.json ...
[task 2023-02-14T09:51:47.910Z] Checking MessagingExperiment.schema.json ...
[task 2023-02-14T09:51:47.910Z]   Checking MessagingExperiment.schema.json for differences...
[task 2023-02-14T09:51:47.910Z]   Validating messages with Experimenter JSON Schema validator...
[task 2023-02-14T09:51:47.910Z]     Validating messages from ReachExperiments:
[task 2023-02-14T09:51:47.910Z] Traceback (most recent call last):
[task 2023-02-14T09:51:47.910Z]   File "make-schemas.py", line 442, in <module>
[task 2023-02-14T09:51:47.910Z]     main(args.check)
[task 2023-02-14T09:51:47.910Z]   File "make-schemas.py", line 424, in main
[task 2023-02-14T09:51:47.910Z]     validate_corpus(schema_def, schema)
[task 2023-02-14T09:51:47.910Z]   File "make-schemas.py", line 404, in validate_corpus
[task 2023-02-14T09:51:47.910Z]     template = message["template"]
[task 2023-02-14T09:51:47.910Z] KeyError: 'template'
[task 2023-02-14T09:51:47.928Z] Creating default state directory: /builds/worker/.mozbuild
[task 2023-02-14T09:51:47.928Z] Site not up-to-date reason: "/builds/worker/checkouts/gecko/obj-x86_64-pc-linux-gnu/_virtualenvs/common" does not exist
[taskcluster 2023-02-14 09:51:48.597Z] === Task Finished ===
[taskcluster 2023-02-14 09:51:48.597Z] Unsuccessful task run with exit code: 1 completed in 110.761 seconds

```
Bug: Unable to remove specific autocomplete entries
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2023-02-14 10:48:55+00:00
Resolved: 2023-02-22 15:43:06+00:00

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

Steps to reproduce:

Experiencing this issue on 3 machines, multiple sites. Specific websites that I've visited maybe once (in the past) are still being suggested above sites I visit all the time, and these suggestions are unable to be removed. Example:

1. I type "up" in the address bar for uploading to Youtube (I use site this regularly)
2. Firefox autocomplete suggests uploaded.net (which I have maybe visited once)
3. I attempt to delete the suggestion using Shift+Del
4. The old entry appears to be gone 


Actual results:

I type "up" again, and the old autocomplete entry is back, and I can't get rid of it 


Expected results:

The uploaded.net entry that was Shift+Deleted should be forgotten by the browser.

At the very least, the uploaded.net entry should be demoted below the site(s) I use more

Note that only some sites are "stuck". Others behave properly with Shift+Del. 

GIF recording attached
Bug: (latent) permafailing TEST-UNEXPECTED-FAIL | browser/base/content/test/webrtc/browser_devices_get_user_media.js | leaked 1 window(s) until shutdown [url = chrome://browser/content/webrtcLegacyIndicator.xhtml]
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2023-02-14 15:10:58+00:00
Resolved: 2023-02-17 07:33:07+00:00

When re-enabling `browser/base/content/test/webrtc/browser_devices_get_user_media.js` for `test/webrtc/legacyIndicator` I get on linux-debug locally (and [on try](https://treeherder.mozilla.org/jobs?repo=try&selectedTaskRun=dPbiDQyCRTqeQ4g99tiJSQ.0&revision=a32eb04b04e4fd5aa442bccfd429d671a01ec8b6) (including for other platforms)) the following permafailing errors:

> ERROR TEST-UNEXPECTED-FAIL | browser/base/content/test/webrtc/browser_devices_get_user_media.js | leaked 1 window(s) until shutdown [url = chrome://browser/content/webrtcLegacyIndicator.xhtml]
ERROR TEST-UNEXPECTED-FAIL | browser/base/content/test/webrtc/browser_devices_get_user_media.js | leaked 1 window(s) until shutdown [url = about:blank]

These are caused by [opening the permissions panel](https://searchfox.org/mozilla-central/rev/5ccb73c0217d1710b10d6e6e297cf3396d10ec23/browser/base/content/test/webrtc/browser_devices_get_user_media.js#870) through the legacy indicator. [`get_user_media_screen.js` exhibits the same](https://searchfox.org/mozilla-central/rev/5ccb73c0217d1710b10d6e6e297cf3396d10ec23/browser/base/content/test/webrtc/browser_devices_get_user_media_screen.js#704) issue.

I am getting this with the patches on bug 1775945, but also on m-c.
Bug: Missing high contrast icon for enhanced tracking protection shield
Status: NEW
Priority: P3
Created: 2023-02-14 15:52:45+00:00
Resolved: 2023-06-02 15:24:16+00:00

When Enhanced Tracking Protection is active, the shield indicator (`#tracking-protection-icon`) is filled with a color gradient

https://searchfox.org/mozilla-central/rev/5ccb73c0217d1710b10d6e6e297cf3396d10ec23/browser/themes/shared/identity-block/tracking-protection-active-brighttext.svg#6-9

This is still used when the high-contrast theme is active, but using a color-gradient as an indicator doesn't seem appropriate when in this mode.
Bug: Initial fetch of translations models takes longer 10x on Linux than on macOS
Status: RESOLVED
Priority: P3
Resolution: INVALID
Created: 2023-02-14 21:50:04+00:00
Resolved: 2024-03-13 15:56:52+00:00

**Description**

When opening the `about:translations` page and loading models on my macOS machine vs. my Ubuntu machine, I notice a significant difference in the time it takes to build the `TranslationsEngine` when fetching un-cached model and wasm data from remote settings.

On macOS the entire process takes about 1 second on the initial fetch. 
On Ubuntu the entire process takes upwards of 10 seconds on the initial fetch. 

While the user experience will be made better in Bug 1814168 by communicating to the user that the models are being downloaded, a 10x difference in performance between the two systems seems worth investigating.

---

**Steps to Reproduce**

1. Launch Firefox on a clean build.
2. Enable `browser.translations.enable` in `about:config`.
3. Navigate to `about:translations`.
4. Type "This is a test." into the left-side English text box.
5. Switch the right-side language to Spanish by selecting it in the dropdown menu.
6. Observe how long it takes for the translation to load.

---

**Profiles**

Here are two profiles, one from macOS and one from Ubuntu, testing the exact same steps to reproduce on a fresh build. The Ubuntu profile takes roughly 10x longer than the macOS profile for the network requests to finish. 

Both profiles were captured on the same day, connected to the same WiFi network. 

**macOS Profile**
https://share.firefox.dev/3I1PNhr

**Ubuntu Profile**
https://share.firefox.dev/40WrBFT
Bug: Firefox pdfviewer show black rectangles instead of spaces
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2023-02-15 09:12:37+00:00
Resolved: 2023-04-28 15:51:22+00:00

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

Steps to reproduce:

I updated firefox to version 110 (flatpak), and I opened pdf at this link: https://insis.vse.cz/zp/77457



Actual results:

The pdfviewer shows black rectangles instead of spaces. 


Expected results:

The pdfviewer should display spaces correct as it shown in previous versions.
Bug: PanelUI.showSubView and friends should fall back to PanelUI-menu-button as an anchor if the passed anchor is not visible
Status: NEW
Priority: P3
Created: 2023-02-15 09:19:17+00:00
Resolved: 2023-02-16 16:12:37+00:00

Mossop noted in https://phabricator.services.mozilla.com/D169742#inline-937057 that it'd be neat if the API automatically provided a helpful default for opening views, if the anchor turned out to not be visible.

Some care should probably be taken here to deal with layout/style flushes: I _think_ (but haven't confirmed) that trying to show a panel with an anchor, the popup code will flush to determine the visibility of the anchor. If so, any checks in PanelUI could also flush before checking if the anchor is visible and coming up with a default; if not, they should not flush (to avoid overhead from layout/style flushes). Getting this wrong could potentially mean us disregarding the passed anchor when it should have been used (would have been visible with a layout flush) or doing too many unnecessary layout flushes.
Bug: [Experiment] Branch B of the PDFjs Feature Callout experiment displays the wrong messages
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-02-15 13:21:58+00:00
Resolved: 2023-02-16 09:25:41+00:00

**[Affected Versions]:**
- Firefox Release 110.0 (Build ID: 20230214051806)

**[Affected Platforms]:**
- Windows 10
- macOS 13.1
- Linux Mint 20.2

**[Prerequisites]:**
- You have set “nimbus.debug” to “true” from “about:config”.

**[Steps to reproduce]:**
1. Open Firefox.
2. Navigate to “about:studies?optin_slug=pdfjs-feature-callout&optin_branch=treatment-b&optin_collection=nimbus-preview” to enroll in the branch B of the “PDFjs Feature Callout” study.
3. Navigate to a page ending in “.pdf”.
4. Observe the PDF callout.

**[Expected result]:**
- The text of callout for branch B is:
Slide 1: “Ditch the sketchy free online editor. Fill out forms, add comments, or take notes directly in Firefox.”
Slide 2: “No more printing and scanning. Mark up documents, then save your changes.”

**[Actual result]:**
- The text of the callout in branch B is:
Slide 1: “Fill out forms, add comments, or take notes directly in Firefox.”
Slide 2: “Mark up PDFs, then save your changes.”

**[Notes]:**
- Attached is a recording of the issue.
Bug: Allow disable or remove extensions button in the UI
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-02-15 14:22:10+00:00
Resolved: 2023-02-15 14:34:32+00:00

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

Steps to reproduce:

The latest Firefox update forces users to have the extensions button in the toolbar.


Actual results:

In previous versions, the extensions button was disabled via the extensions.unifiedExtensions.enabled configuration in about:config. This no longer works.


Expected results:

Please provide a way for users to be able to remove the extensions button from the UI. This should be accessible from the toolbar or a config flag.
Bug: [Experiment] The Treatment B branch of the “PDFjs Feature Callout” experiment displays the wrong impression pings
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-02-15 14:29:47+00:00
Resolved: 2023-02-16 09:07:23+00:00

**[Affected versions]:**
- Firefox Release 110.0 - Build ID: 20230214051806

**[Affected Platforms]:**
- Windows 10 x64.
- macOS 13.1.
- Linux Mint 20.2 x64.

**[Prerequisites]:**
- Have the “nimbus.debug” and “browser.ping-centre.log” prefs set to true on the “about:config” page.
- Have the browser console opened (Ctrl/Cmd + Shift +J).

**[Steps to reproduce]:**
1.Navigate to the “about:studies?optin_slug=pdfjs-feature-callout&optin_branch=treatment-b&optin_collection=nimbus-preview” URL to force enroll in the Treatment B branch of the “PDFjs Feature Callout”  experiment.
2. Navigate to a page that ends in “.pdf” (e.g.:https://www.clickdimensions.com/links/TestPDFfile.pdf ).
3. Focus the Browser console.
4. Observe the displayed telemetry pings for the first slide.

**[Expected result]:**
 - The "PDFJS_FEATURE_TOUR_0_FEATURE_CALLOUT_1_B_C" is displayed in the Browser Console.

**[Actual result]:**
- The "PDFJS_FEATURE_TOUR_0_FEATURE_CALLOUT_1_A_C" is displayed in the Browser Console.

**[Notes]:**
- This issue is also reproducible for the second slide.
- This issue is also reproducible for the “Click” telemetry pings.
- Attaching a screen recording of the issue [here](https://drive.google.com/file/d/1kHXizgbKN-Y22X6Wrv9m-9QeZpjgV9Nz/view?usp=sharing).
Bug: Search Engine list items are doubled after repeating the deletion and restore default action
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2023-02-15 15:44:42+00:00
Resolved: 2023-02-22 09:42:14+00:00

**Found in**
* Firefox 111.0b1

**Affected versions**
* Firefox 111.0b1
* Firefox 112.0a1

**Tested platforms**
* Affected platforms: Windows 10, Ubuntu 22, macOS 12 

**Steps to reproduce**
1. Launch Firefox.
2. Go to about:preferences#search, last item: Search Shortcuts.
3. Remove one or two search engines then click on Restore Default Search Engines.
4. Repeat the above step (delete search engine and restore default).

**Expected result**
* The Search Engine list appears correctly, each item appears only once.

**Actual result**
* In Search Engine list the items are doubled after repeating the deletion and restore default action, see the attached screenshot (doubled-search-engine.png).

**Regression range**
* It is a recent regression.
* First bad: 20230202172003
* Last good: 20230201215112
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=9a864bf574dbb3c108d053d439c23f00fe3887ca&tochange=f00c3546b0a5f36c6f201b35cb9d523cc25808da
* Potentially regressed by: Bug 1781768 -  When live language switching ensure that search engines installed via add-ons also update. r=search-reviewers,settings-reviewers,mconley,daleharvey


**Additional notes**
* Must repeat several times the step 3, only in this way the issue appears.
Bug: Intermittent browser/components/urlbar/tests/browser/browser_searchMode_indicator.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2023-02-15 17:26:53+00:00
Resolved: 2023-08-11 12:01:16+00:00

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

---
```
[task 2023-02-15T16:41:54.736Z] 16:41:54     INFO - TEST-START | browser/components/urlbar/tests/browser/browser_searchMode_indicator.js
[task 2023-02-15T16:42:00.529Z] 16:42:00     INFO - TEST-INFO | started process screentopng
[task 2023-02-15T16:42:00.828Z] 16:42:00     INFO - TEST-INFO | screentopng: exit 0
[task 2023-02-15T16:42:00.828Z] 16:42:00     INFO - Buffered messages logged at 16:41:54
[task 2023-02-15T16:42:00.829Z] 16:42:00     INFO - Entering setup bound 
[task 2023-02-15T16:42:00.829Z] 16:42:00     INFO - Extension loaded
[task 2023-02-15T16:42:00.829Z] 16:42:00     INFO - Buffered messages logged at 16:41:55
[task 2023-02-15T16:42:00.829Z] 16:42:00     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_searchMode_indicator.js | Search provider extension should be running - "running" == "running" - 
[task 2023-02-15T16:42:00.830Z] 16:42:00     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_searchMode_indicator.js | Extension ID of search provider should be set - "example@tests.mozilla.org" == true - 
[task 2023-02-15T16:42:00.830Z] 16:42:00     INFO - Buffered messages finished
[task 2023-02-15T16:42:00.831Z] 16:42:00     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_searchMode_indicator.js | Uncaught exception in setup bound  - "Waiting for top sites to be updated - timed out after 50 tries."
[task 2023-02-15T16:42:00.836Z] 16:42:00     INFO - Leaving setup bound 
[task 2023-02-15T16:42:00.837Z] 16:42:00     INFO - Entering test bound backspace
[task 2023-02-15T16:42:00.838Z] 16:42:00     INFO - Awaiting for the urlbar panel to open
[task 2023-02-15T16:42:00.839Z] 16:42:00     INFO - Urlbar panel opened
[task 2023-02-15T16:42:00.840Z] 16:42:00     INFO - Enter Search Mode null
[task 2023-02-15T16:42:00.841Z] 16:42:00     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_searchMode_indicator.js | One-offs are visible - true == true - 
```
Bug: MOZ_SERVICES_SYNC is still used in the code
Status: REOPENED
Priority: --
Created: 2023-02-15 17:44:32+00:00
Resolved: 2023-04-21 17:30:55+00:00

`MOZ_SERVICES_SYNC` is still used in `services/moz.build` and in other files, such as `AppConstants.jsm`.
However, setting it to `False` in `browser/moz.configure` results in a build failure, because `@RESPATH@/components/SyncComponents.manifest` cannot be found anymore.
Restoring the `#ifdef` in `browser/installer/package-manifest.in` leads to other errors in the console and in the UI, but they are easily solvable.
Bug: Autoplay settings: Exceptions cannot be deleted
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2023-02-15 19:06:42+00:00
Resolved: 2023-02-16 15:09:13+00:00

(1.) Go to *Tools\Settings\Privacy & Security\Permissions\Autoplay* and press *Settings...*
(2.) Set *Default for all websites: Block Audio and Video*
(3.) Press *Remove All Websites* to clear the list of exceptions
(4.) Confirm with *Save Changes*
(5.) Press *Settings...* again and see...

**Bug:** The two exceptions *about:welcome* and *about:welcome^privateBrowsingId=1* keep coming back regardless how often you delete them!
Bug: Perma [Tier 2] /builds/worker/checkouts/gecko/browser/components/newtab/lib/PlacesFeed.jsm:72:21 | Use of unknown interface Ci.nsINavBookmarkObserver (mozilla/valid-ci-uses)
Status: RESOLVED
Priority: P5
Resolution: FIXED
Created: 2023-02-16 00:49:25+00:00
Resolved: 2023-02-20 06:47:54+00:00

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

---
```
[task 2023-02-16T00:20:56.158Z] TEST-UNEXPECTED-ERROR | /builds/worker/checkouts/gecko/browser/components/newtab/lib/PlacesFeed.jsm:72:21 | Use of unknown interface Ci.nsINavBookmarkObserver (mozilla/valid-ci-uses)
[taskcluster 2023-02-16 00:20:56.514Z] === Task Finished ===
[taskcluster 2023-02-16 00:20:57.101Z] Unsuccessful task run with exit code: 1 completed in 445.93 seconds
```
Bug: Giving camera permission with Remember this decision ticked to a local .html file will automatically give this permission to another .html file (in the same tab)
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2023-02-16 03:28:09+00:00
Resolved: 2024-05-13 16:29:27+00:00

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

Steps to reproduce:

(I think this is a bypassing of the fixing at https://bugzilla.mozilla.org/show_bug.cgi?id=1811181.)

On macOS Ventura 13.1 and Firefox Nightly 112.0a1 (2023-02-15) (64-bit):

Create two local .html files with different names and the same source code:

<div id="container">

    <video id="gum-local" autoplay playsinline></video>
    <button id="showVideo">Open camera</button>

</div>

<script src="https://webrtc.github.io/samples/src/content/getusermedia/gum/js/main.js"></script>

Load the first file, click Open camera, tick Remember this decision and allow the camera permission. 

In the same tab, change the path to the second file, click Open camera, the camera permission is automatically granted to the second file.


Actual results:

In the same tab, change the path to the second file, click Open camera, the camera permission is automatically granted to the second file.


Expected results:

Remember this decision is used for the current file or for the current files and all the next files?
Bug: Study interferes with RTAMO onboarding being displayed
Status: NEW
Priority: P3
Created: 2023-02-16 07:34:18+00:00
Resolved: 2023-06-18 00:30:54+00:00

Description:
The RTAMO onboarding page is not displayed when launching the browser due to possible interference from an active study - Window Modal vs Tab Modal.

Upon browser launch following the initiation of the RTAMO flow, a modal is displayed showing the default Firefox onboarding and not the RTAMO onboarding.
 
After completing the default Firefox onboarding, accessing about:welcome will show the RTAMO page and the RTAMO flow can be completed i.e. the add-on can be installed.

Steps to reproduce:
1. Using a VM with Windows, launch Edge or Chrome
2. Navigate to AMO and access the page of an add-on
3. Click the “Download Firefox and get the extension” button on the add-on’s page
4. Once the installer is downloaded, run it to install Firefox
5. After installation, Firefox will launch in a Window Modal due to the study being active and display the default onboarding and not the RTAMO onboarding as would be expected

Actual:
The RTAMO onboarding page is not displayed when Firefox launches.

Expected:
The RTAMO onboarding page should be displayed when Firefox launches.
Bug: In engagement telemetry don't return results or groups for engagement_type that didn't show the view
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2023-02-16 09:19:04+00:00
Resolved: 2023-03-06 13:57:25+00:00

paste_go and drop_go are two engagement_type values that won't show a results pane, they are immediate engagement.
For them we are instead returning results and groups from the previous query. We should return those values only if the view was actually open at the time of interaction.
Bug: In engagement telemetry when engagement_type is a _go one, selected_result is unknown
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2023-02-16 09:26:22+00:00
Resolved: 2023-03-06 12:13:27+00:00

paste_go and drop_go are two engagement_type values that won't have a selected_result, because we don't show the view for them.
We should document this fact in the metric documentation.
Whether we want to use an empty string, unknown or a special input_field value, is something I asked Rebecca about, let's wait for an answer.