av9ash/GitBugs huggingface dataset:
Bug: Browsing history checkbox is redundent
Status: NEW
Priority: P3
Created: 2023-04-11 11:22:51+00:00
Resolved: 2023-04-17 06:23:11+00:00

In the new migration wizard on macOS I see a single checkbox for the data to import and then buttons to proceed with or cancel the import. Unchecking the checkbox makes it impossible to proceed so it seems that this checkbox is redundant implying that I have two choices to make when really I only have one, either I want to import the data or not.

I'm guessing that in some cases there are more data types available (passwords, etc.) and so there could be multiple checkboxes which would make more sense but maybe when there is only a single checkbox it should instead be just a plain text note that browsing history is the only data supported in this case. Might be nice to know why passwords aren't supported mind you.
Bug: Clicking in the address bar still selects all after making an empty selection, interfering with caret insertion
Status: NEW
Priority: P5
Created: 2023-04-11 11:36:51+00:00
Resolved: 2023-10-23 15:51:18+00:00

STR:
1. Start without the address bar being focused.
2. Press and hold the left mouse button in the address bar, start a selection and then return to the original place so the selection is empty.
3. Release the mouse button.

Expected:
Caret inserted without any selection.

Actual:
Entire URL selected like a normal click, as if the selection event did not occur. This prevents inserting the caret with a single click, instead the user needs to click once, wait for the double-click timer to elapse and then click again.

Select all could also potentially be cancelled when the mouse button is held down for long enough to make caret insertion easier.
Bug: [Experiment] The "Fox" gif is still animated even if "reduce motion" OS settings is activated
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-04-11 12:08:16+00:00
Resolved: 2023-04-20 14:35:54+00:00

**[Affected versions]:**
- Firefox Release 112.0 - Build ID: 20230406114409

**[Affected Platforms]:**
- Windows 10 x64
- macOS 12.3.1
- Ubuntu 22.04 x64

**[Prerequisites]:**
- Have the “nimbus.debug” pref set to “true” in the about:config page
- Firefox is not pinned to the taskbar/dock
- Reduce motion OS option is activated from Accessibility display

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Navigate to “about:studies?optin_slug=q2-pin-to-taskbar-fox-doodle-en-holdback&optin_branch=treatment-a&optin_collection=nimbus-preview”.
3. Restart the browser.
4. Observe the “Pin to taskbar” spotlight.

**[Expected result]:**
- The fox gif from the spotlight is **not** animated.
    
**[Actual result]:**
- The fox gif from the spotlight is **still** animated.

**[Additional Notes]:**
- The issue is also reproducible on the "Set to default" spotlight.
-  Attached is a screen recording of the issue.
Bug: Cookies are shared between two/more different origins !
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2023-04-11 12:26:33+00:00
Resolved: 2024-05-30 18:08:11+00:00

Hello Firefox Security Team,

The same-origin policy is a critical security mechanism that restricts how a document or script loaded by one origin can interact with a resource from another origin.

As you know, if 2 URL have the same schema, domain, and port we can say these are the same origin. The data is shared between the same origin domains.

As you mentioned in the following link, if the port is different it will be a failure.
https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy

I realized that port info doesn't check by firefox. The cookies are shared with two application that runs on two different port. (same schema and domain but different port)

I've uploaded POC video that shows cookie shares between different origins.

All the best,
Musa
Bug: When migrating from a browser that uses multiple profiles, all resources are imported no matter what is selected from the wizard
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-04-11 14:44:22+00:00
Resolved: 2023-05-02 12:39:53+00:00

I noticed this while doing some exploratory testing of the new migration wizard. This line here:

https://searchfox.org/mozilla-central/rev/2ce39261ea6a69e49d87f76a119494b2a7a7e42a/browser/components/migration/MigrationWizardParent.sys.mjs#162

isn't passing the profileObj into `getMigrateData`, so `getMigrateData` is always returning `0`, which maps to MigrationUtils.resourceTypes.ALL.
Bug: Firefox constantly freezes
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-04-11 14:49:27+00:00
Resolved: 2024-01-26 17:51:56+00:00

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

Steps to reproduce:

Literally anything. This issue will literally happen even if I'm not touching my computer and not doing anything. 

For months now I've had this issue where the browser will freeze for a second or two and the window expands over the start bar.

At worst if I push any button or click when it happens it crashes the browser with no crash report.

It doesn't matter what I'm doing, watching a video, scrolling, typing, nothing. It happens. I've noticed that this tends to happen most after updates but it does go away after weeks.

Don't ask me to record or induce it, as I've said it's pretty much random but I do notice it happening more later in the day.  It's 10:46 AM as of writing this and it's already started.

I want a permanent solution.

Windows 10. Latest version. 



Actual results:

As stated it will freeze briefly for a few moments and overlap the bar at the bottom of my screen. It happens if I'm typing, if I'm just watching a video, or even when I'm just LOOKING at my computer. I can restart my computer to get it to stop but I refuse to accept that as an option.

I know from asking around that it's not just happening to me. There are certain sites like Tumblr that make it happen more but it will happen on any website.

When it does happen I can sometimes hear the fans in my computer get louder if that helps at all.


Expected results:

It SHOULD run fine without this issue happening!
Bug: [Experiment] The "Make primary browser" prompt is wrongly displayed right after Firefox was set as the default browser through the "Set as default" doodle spotlight
Status: RESOLVED
Priority: P1
Resolution: WONTFIX
Created: 2023-04-11 15:22:41+00:00
Resolved: 2023-05-01 16:15:29+00:00

**[Affected versions]:**
- Firefox Release 112.0 - Build ID: 20230406114409

**[Affected Platforms]:**
- Windows 10 x64
- macOS 12.6.1

**[Prerequisites]:**
- Have the "[user.js](https://drive.google.com/file/d/1wMRUF7QqaxhrbrMPGNi468HjiB6LjokT/view?usp=share_link)" file saved to your PC.
- Have a profile older than 28 days.
- Firefox is not set as the default browser.
- The "Always check if Firefox is your default browser" option from the "about:preferences" page is checked.

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Navigate to the profile folder and paste the "user.js" file from prerequisites.
3. Restart the browser and click the "Not now" button from the "Make primary browser" prompt.
4. Restart the browser again.
5. Click the "Open my links with Firefox" from the "Set as default" spotlight.
6. Observe the behavior.

**[Expected result]:**
- The "Set as default" spotlight is dismissed and the browser is set as default.
    
**[Actual result]:**
- The "Set as default" spotlight is dismissed, however, the "Make primary browser" prompt is displayed even if the browser is already set as default.

**[Notes]:**
- Attached is a screen recording of the issue:
Bug: ~perma assertion hit in CI (dom/tests/browser/browser_bug1685807.js), always reported as success
Status: NEW
Priority: --
Created: 2023-04-11 20:02:42+00:00
Resolved: 2023-04-12 20:46:39+00:00

I found we have thousands of lines parsed by treeherder from browser-chrome tests, all from the testcase dom/tests/browser/browser_bug1685807.js.
```
JavaScript error: resource:///modules/AsyncTabSwitcher.jsm, line 506: Error: Assertion failure
```

https://treeherder.mozilla.org/jobs?repo=mozilla-central&searchStr=bc11%2Cdebug

I suspect we can just delete [this line](https://searchfox.org/mozilla-central/source/browser/modules/AsyncTabSwitcher.jsm#334):
`this.assert(!this.blankTab);`
Bug: BUG: file picker crashes in Firefox Headless on Ubuntu
Status: UNCONFIRMED
Priority: --
Created: 2023-04-12 04:46:27+00:00
Resolved: 2024-11-25 10:16:41+00:00

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

Steps to reproduce:

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:

OS: Ubuntu 20.04
Firefox: 110 stable
Downstream bug: https://github.com/microsoft/playwright/issues/21550

Consider running the following puppeteer snippet:
```
// a.mjs
import puppeteer from 'puppeteer-core';

const browser = await puppeteer.launch({
  product: 'firefox',
  executablePath: '/usr/bin/firefox',
  dumpio: true,
});
const page = await browser.newPage();

await page.setContent(`
  <input type=file>
`);
const inputElement = await page.$('input');
await inputElement.click();

await browser.close();
```

NOTE: this looks similar to https://bugzilla.mozilla.org/show_bug.cgi?id=1821754



Actual results:

Actual results:

Firefox crashes with the following output:

(firefox:3295229): Gtk-CRITICAL **: 11:03:34.737: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
[Parent 3295229, Main Thread] WARNING: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed: 'glib warning', file /build/firefox-jjwe4i/firefox-110.0.1+build2/toolkit/xre/nsSigHandlers.cpp:167




Expected results:

Expected results:

The browser should not crash.
Bug: www.qwant.com - : Search problem with "HTTPS only"
Status: RESOLVED
Priority: P1
Resolution: WORKSFORME
Created: 2023-04-12 07:23:30+00:00
Resolved: 2023-04-14 15:47:57+00:00

From github: https://github.com/webcompat/web-bugs/issues/120783.

> <!-- @browser: Firefox Mobile 114.0 -->
> <!-- @ua_header: Mozilla/5.0 (Android 13; Mobile; rv:109.0) Gecko/114.0 Firefox/114.0 -->
> <!-- @reported_with: android-components-reporter -->
> <!-- @extra_labels: browser-fenix -->
> 
> **URL**: http://www.qwant.com/?q=hello+world&client=ff_android
> 
> **Browser / Version**: Firefox Mobile 114.0
> **Operating System**: Android 13
> **Tested Another Browser**: Yes Chrome
> 
> **Problem type**: Something else
> **Description**: Search problem with "HTTPS only"
> **Steps to Reproduce**:
> From the search bar, with the "HTTPS only" mode, Qwant only works with single-word searches.  Several words in the search bar lead to an unavailable page.
> The problem is solved by disabling the mode.
> <details>
>       <summary>View the screenshot</summary>
>       <img alt="Screenshot" src="https://webcompat.com/uploads/2023/4/1afcc7d7-9c3d-4388-8373-9e43fb96e16c.jpeg">
>       </details>
> 
> <details>
> <summary>Browser Configuration</summary>
> <ul>
>   <li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20230410212705</li><li>channel: nightly</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
> </ul>
> </details>
> 
> [View console log messages](https://webcompat.com/console_logs/2023/4/465e3b13-f505-4d6a-a278-576a9d5ec52b)
> 
> _From [webcompat.com](https://webcompat.com/) with ❤️_

Change performed by the [Move to Bugzilla add-on](https://addons.mozilla.org/en-US/firefox/addon/move-to-bugzilla/).
Bug: Impression ping for first screen is always EASY_SETUP instead of actually shown screen
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-04-12 08:40:17+00:00
Resolved: 2023-04-26 17:57:12+00:00

**Found in**
* Firefox 113.0b2

**Affected versions**
* Firefox 113 beta
* Nightly 114.0a1

**Tested platforms**
* Affected platforms: Windows 10, macOS 11.7

**Preconditions**
* Firefox is set as the default browser and it is pinned to the taskbar/dock;
* browser.ping-centre.log set to true;
* Have the "Browser Console" opened.

**Steps to reproduce**
1. Navigate to the "about:welcome" page and focus on the "Browser Console".
2. Observe the displayed pings.

**Expected result**
* A telemetry ping specific to the "about:welcome" and the "Get Started" slide should be triggered. It should look like this: 

** TELEMETRY PING (about:welcome): {"experiments":{},"locale":"en-US","version":"112.0","release_channel":"release","event":"IMPRESSION","event_context":"{\"page\":\"about:welcome\"}","message_id":"MR_WELCOME_DEFAULT_0_AW_GET_STARTED_GLIMG","addon_version":"20230406114409","client_id":"41dee36e-9b18-4665-bde9-d93306a75f76","browser_session_id":"99799259-9c36-4b28-92b5-4d77a2445145"}

**Actual result**
* The telemetry ping is triggered but is specific to the "Easy setup" slide. It looks like this:

**TELEMETRY PING (about:welcome): {"experiments":{"beta-ech-validation":{"branch":"enabled-fallbacks"}},"locale":"en-US","version":"113.0","release_channel":"beta","event":"IMPRESSION","event_context":"{\"page\":\"about:welcome\"}","message_id":"MR_WELCOME_DEFAULT_0_AW_EASY_SETUP_EGLIMG","addon_version":"20230411180038","client_id":"f7f79348-4654-4655-ac78-62cd4c7236a2","browser_session_id":"b1e3278e-3045-40d6-b8cd-32c56a11b42d","attribution":{"dlsource":"mozillaci"}}

**Regression range**
This is a recent regression as it is not reproducible on the latest Firefox 112 release. I will look for a regression range as soon as possible.
Bug: The title from the left part  of the “Choose Your Language” screen is not translated, and the <OS Language> is missing from the primary button
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-04-12 08:43:58+00:00
Resolved: 2023-09-28 14:49:52+00:00

**[Affected versions]:**
- Firefox Beta 113.0b2 (Build ID: 20230411180038)

**[Affected Platforms]:**
- Windows 10 x64
- Windows 11 x64

**[Prerequisites]:**
- Have the Firefox Beta 113.0b2 en-US build installed and opened.
- Have set the Japanese OS language.
- Have the “nimbus.debug” pref set to true in the “about:config” page.


**[Steps to reproduce]:**
1. Force enroll in the Treatment B branch of the experiment using the following link: about:studies?optin_slug=prompt-fxa-creation-after-import&optin_branch=treatment-b&optin_collection=nimbus-preview
2. Navigate to the “about:welcome” page.
3. Click the “Save and continue” button from the first screen and complete the import flow.
4. Observe the elements from the “Choose Your Language” screen.

**[Expected result]:**
- The title from the left part of the screen and the label of the primary button are translated into Japanese.

**[Actual result]:**
- The title from the left part of the screen is not translated.
- The “Switch to” label of the primary button is displayed.

**[Notes]:**
- This issue is ONLY reproducible when being enrolled in the experiment.
- This issue is NOT reproducible on the Treatment A branch of the experiment.
- The elements of the “Choose Your Language” screen are correctly displayed after the page refresh.
- This issue is also reproducible when the German(Germany) OS language is set.
- This issue is also reproducible when naturally enrolled in the experiment.
- Attached is a screen recording of the issue.
Bug: Snap Firefox for Ubuntu 22.04 losing session
Status: UNCONFIRMED
Priority: P3
Created: 2023-04-12 10:11:24+00:00
Resolved: 2023-11-06 16:22:56+00:00

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

Steps to reproduce:

1. Configure Firefox to open Windows and Tabs on startup.
2. Start Firefox using launcher (normally). 
3. Open some tabs. 
4. Close firefox. 
5. Start Firefox again. 



Actual results:

Observe that no window and no tabs are restored and that the History menu does not offer a Restore Previous Session. Also observe that the Window history does show my window in the list. Observe that the settings still reflect that Firefox is configured to open windows and tabs upon startup.


Expected results:

I expected the windows and tabs to be reopened when I start Firefox, or that the History menu offers the Restore Previous Session (if Firefox isn't configured to open windows and tabs upon startup).
Bug: Intermittent browser/base/content/test/favicons/browser_favicon_nostore.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2023-04-12 14:11:31+00:00
Resolved: 2023-07-12 12:02:07+00:00

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

---
```
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - TEST-PASS | browser/base/content/test/favicons/browser_favicon_nostore.js | Should have seen the expected icon. - 
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - Buffered messages logged at 12:52:17
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - Leaving test bound browser_loader
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - Entering test bound places_loader
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - Buffered messages finished
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/favicons/browser_favicon_nostore.js | Uncaught exception in test bound places_loader - at resource://gre/modules/PlacesUtils.sys.mjs:782 - Error: PageInfo: Invalid value for property 'visits': [{"date":"2023-04-12T12:52:17.310Z","referrer":null}]
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - Stack trace:
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - validateItemProperties@resource://gre/modules/PlacesUtils.sys.mjs:782:19
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - validatePageInfo@resource://gre/modules/PlacesUtils.sys.mjs:1180:17
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - insertMany@resource://gre/modules/History.sys.mjs:320:35
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - addVisits@resource://testing-common/PlacesTestUtils.sys.mjs:94:36
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - places_loader@chrome://mochitests/content/browser/browser/base/content/test/favicons/browser_favicon_nostore.js:51:25
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - async*handleTask@chrome://mochikit/content/browser-test.js:1039:26
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - _runTaskBasedTest@chrome://mochikit/content/browser-test.js:1111:18
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - async*Tester_execTest@chrome://mochikit/content/browser-test.js:1253:14
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - nextTest/<@chrome://mochikit/content/browser-test.js:1028:14
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - SimpleTest.waitForFocus/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:1053:13
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - Leaving test bound places_loader
[task 2023-04-12T12:52:17.405Z] 12:52:17     INFO - Entering test bound test_later_addition
[task 2023-04-12T12:52:17.719Z] 12:52:17     INFO - TEST-PASS | browser/base/content/test/favicons/browser_favicon_nostore.js | Should have seen the expected icon. - 
```
Bug: Dragging two or more bookmarks into a Windows Explorer window does nothing
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-04-12 14:59:41+00:00
Resolved: 2023-04-27 11:55:27+00:00

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

Steps to reproduce:

I can reproduce this bug by following these steps (Windows only):
1. Open Firefox side-by-side with an Explorer window.
2. Bookmark two websites in Firefox, if necessary.  (I used github.com and duckduckgo.com.  Bookmark data do not seem to matter here.)
3. Open the Library window with Ctrl+Shift+O.
4. Locate and select the two bookmarks in the Library window.
5. Use the mouse to drag-and-drop them from that window into the adjacent Explorer window.

I am able to reproduce this bug on Windows 7 and Windows 10.  I haven't tried other versions of Windows.  The bug also occurs with larger numbers of selected bookmarks — three, four, five, etc.  So far I have always been able to reproduce this.


Actual results:

Everything is fine until after the drag-and-drop operation.  No Windows shortcut (.URL) files, or any other files, are created in the target folder after releasing the primary mouse button.  There is only a silent failure.  No crash, error message, or alert sound occurs.

It looks like a drag-and-drop operation should work.  When the mouse pointer is moved over a valid target folder in the Explorer window, the cursor changes to indicate that shortcuts will be created if the bookmarks are "dropped" at the current mouse position.


Expected results:

Two Windows shortcut (.URL) files should have been created in the target folder, with the appropriate filenames and shortcut attributes, like what occurs when a single Firefox bookmark is dragged and dropped into an Explorer window.

If Firefox does not support dragging multiple bookmarks like this, the "Unavailable" cursor should be shown instead of the one Explorer uses to indicate shortcut creation.  That way the user will know this doesn't work.
Bug: Red Pocket icon displayed in toolbar without reason
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2023-04-12 20:08:37+00:00
Resolved: 2023-04-13 19:48:23+00:00

The Pocket button in the default toolbar is showing up red whenever I visit  `mail.google.com/*` I initially believed this was because I had accidentally saved this URL to my Pocket saves, but I checked in my cue and that's not the case. I also understand that this is not the expected behaviour even for articles/URLs I have actually saved in the past.

So far, the icon only used to turn red during the process of saving an article and then will revert back to just the outline. 

Flagging this since this apparently inconsistent behaviour it might be confusing to other users.
Bug: ASRouter Targeting doesnt serialize arrays correctly
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2023-04-12 20:29:44+00:00
Resolved: 2023-04-22 14:05:52+00:00

Both [`ASRouterTargeting#getEnvironmentSnapshot`](https://searchfox.org/mozilla-central/rev/ad732108b073742d7324f998c085f459674a6846/browser/components/newtab/lib/ASRouterTargeting.jsm#949) and [`ASRouter#getTargetingParameters`](https://searchfox.org/mozilla-central/rev/ad732108b073742d7324f998c085f459674a6846/browser/components/newtab/lib/ASRouter.jsm#1146) do not serialize arrays correctly. Insead they get serialized as an object with string keys. This breaks testing targeting expressions in ASRouter DevTools as well as any targeting payloads serialized for use with the background message service.