av9ash/GitBugs huggingface dataset:
Bug: Tab drag action gets canceled and tabs move to their original positions when dropping slightly outside of the tab strip
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2025-01-31 15:53:12+00:00
Resolved: 2025-01-31 18:15:52+00:00

STR:
1. Open a bunch of tabs.
2. Add some of these tabs to a multiselection (but not the left-most or right-most tabs).
3. Drag the multiselection to the start or end of the tab strip.

Expected result:
The tabs drop into the tab strip at the selected location.

Actual result:
The tabs reset to the location they were in before the drag began.
Bug: Opening a page by clicking again on a tab opens the cache content instead of the current content even when online.
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2025-01-31 16:10:34+00:00
Resolved: 2025-02-04 14:54:52+00:00

Steps to reproduce:

I checked it in Firefox 134.0.1 Snap (and in Firefox current ESR even if less completely tested).
I use Lubuntu 22.04 OS.
I only tell about this problem today but I see it since years I think.
I also add that I had personnally told about other cache issues, and this one might be tied in with them idk (or to other ones from other users).
(https://bugzilla.mozilla.org/show_bug.cgi?id=1899226)[When offline, cached web pages often not displaying while present in cache]. 
And (https://bugzilla.mozilla.org/show_bug.cgi?id=1937331)["Cookies and Site Data" in about:preferences#privacy don't show directly real count] (maybe?).
I chose https://stackoverflow.com/questions as an example of a page that has quick enough modifications (every 1 or 2 minutes) to help the test, but it can happen with many or every web pages.

1/ In a window, I open https://stackoverflow.com/questions in **tab1**, and go to another page or say an empty page in **tab2**, and restart Firefox.
2/ In **about:preferences#general**, have **Startup > [x] Open previous windows and tabs** checked.
3/ Always staying online, restart FF. It will open on **tab2**.
4/ Open **tab1** by clicking on it. Memorize the page state by e.g. the 2 last users who have posted an issue.
5/ Reload the page (the first post should be xx secs or 1 min old, so do it in less than ~15 seconds to avoid adding minutes to this time, which could make you think that the minutes added after reload are normal, while they are not).


Actual results:

After reload, you will see the users are lower in the page, with time of their post e.g. 4 min ago (if you had opened this page 4 min ago before FF restart).
This means FF has displayed the cache page, even when you were online.
I checked with my settings+addons, and in Troubleshoot Mode.


Expected results:

Open directly the current version of a page when a tab is clicked when online.

A case when opening is correct.
Close https://stackoverflow.com/questions tab, restart FF, open it by simply **right-click > Paste and Go** https://stackoverflow.com/questions in the omnibar of an empty tab.
There you will have directly the current page version.
Bug: Opening a page by clicking again on a tab opens the cache content instead of the current content even when online.
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2025-01-31 16:16:07+00:00
Resolved: 2025-02-03 14:43:14+00:00

Steps to reproduce:

I checked it in Firefox 134.0.1 Snap (and in Firefox current ESR even if less completely tested).
I use Lubuntu 22.04 OS.
I only tell about this problem today but I see it since years I think.
I also add that I had personnally told about other cache issues, and this one might be tied in with them idk (or to other ones from other users).
[https://bugzilla.mozilla.org/show_bug.cgi?id=1899226](When offline, cached web pages often not displaying while present in cache).
And [https://bugzilla.mozilla.org/show_bug.cgi?id=1937331]("Cookies and Site Data" in about:preferences#privacy don't show directly real count) (maybe?).
I chose https://stackoverflow.com/questions as an example of a page that has quick enough modifications (every 1 or 2 minutes) to help the test, but it can happen with many or every web pages.

1/ In a window, I open https://stackoverflow.com/questions in **tab1**, and go to another page or say an empty page in **tab2**, and restart Firefox.
2/ In **about:preferences#general**, have **Startup > [x] Open previous windows and tabs** checked.
3/ Always staying online, restart FF. It will open on **tab2**.
4/ Open **tab1** by clicking on it. Memorize the page state by e.g. the 2 last users who have posted an issue.
5/ Reload the page (the first post should be xx secs or 1 min old, so do it in less than ~15 seconds to avoid adding minutes to this time, which could make you think that the minutes added after reload are normal, while they are not).


Actual results:

After reload, you will see the users are lower in the page, with time of their post e.g. 4 min ago (if you had opened this page 4 min ago before FF restart).
This means FF has displayed the cache page, even when you were online.
I checked with my settings+addons, and in Troubleshoot Mode.


Expected results:

Open directly the current version of a page when a tab is clicked when online.

A case when opening is correct.
Close https://stackoverflow.com/questions tab, restart FF, open it by simply **right-click > Paste and Go** https://stackoverflow.com/questions in the omnibar of an empty tab.
There you will have directly the current page version.
Bug: Opening a page by clicking on an unloaded tab loads the cache version instead of the current version even when online.
Status: UNCONFIRMED
Priority: --
Created: 2025-01-31 16:21:04+00:00
Resolved: 2025-02-18 07:52:01+00:00

Steps to reproduce:

I checked it in Firefox 134.0.1 Snap (and in Firefox current ESR even if less completely tested).
I use Lubuntu 22.04 OS.
I only tell about this problem today but I see it since years I think.
I also add that I had personnally told about other cache issues, and this one might be tied in with them idk (or to other ones from other users).
**When offline, cached web pages often not displaying while present in cache** https://bugzilla.mozilla.org/show_bug.cgi?id=1899226.
And **"Cookies and Site Data" in about:preferences#privacy don't show directly real count** https://bugzilla.mozilla.org/show_bug.cgi?id=1937331 (maybe?).
I chose https://stackoverflow.com/questions as an example of a page that has quick enough modifications (every 1 or 2 minutes) to help the test, but it can happen with many or every web pages.

1/ In a window, I open https://stackoverflow.com/questions in **tab1**, and go to another page or say an empty page in **tab2**, and restart Firefox.
2/ In **about:preferences#general**, have **Startup > [x] Open previous windows and tabs** checked.
3/ Always staying online, restart FF. It will open on **tab2**.
4/ Open **tab1** by clicking on it. Memorize the page state by e.g. the 2 last users who have posted an issue.
5/ Reload the page (the first post should be xx secs or 1 min old, so do it in less than ~15 seconds to avoid adding minutes to this time, which could make you think that the minutes added after reload are normal, while they are not).


Actual results:

After reload, you will see the users are lower in the page, with time of their post e.g. 4 min ago (if you had opened this page 4 min ago before FF restart).
This means FF has displayed the cache page, even when you were online.
I checked with my settings+addons, and in Troubleshoot Mode.


Expected results:

Open directly the current version of a page when a tab is clicked when online.

A case when opening is correct.
Close https://stackoverflow.com/questions tab, restart FF, open it by simply **right-click > Paste and Go** https://stackoverflow.com/questions in the omnibar of an empty tab.
There you will have directly the current page version.
Bug: Sidebar button stops functioning in windows where the sidebar was hidden, when changing the Sidebar button setting between show/hide and expand/collapse
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2025-01-31 19:14:05+00:00
Resolved: 2025-02-13 17:46:27+00:00

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

Steps to reproduce:

In about:config, toggle sidebar.revamp and sidebar.verticalTabs to true to enable vertical tabs in the sidebar.

Open two Firefox windows. In window A, set the sidebar behaviour to show and hide, then hide the sidebar. In window B, show the sidebar, then set the sidebar behaviour to expand and collapse. In window A, click the sidebar button.


Actual results:

The icon for the sidebar button updates (as though the sidebar state changed) but the sidebar doesn't change state and remains hidden.


Expected results:

The sidebar should appear, rather than remain hidden. It could appear collapsed or expanded, either seems reasonable.
Bug: tab group of two tabs and left one selected: Ctrl+T opens new tab to the left but should be to the right (browser.tabs.insertAfterCurrent = true)
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2025-01-31 20:20:29+00:00
Resolved: 2025-02-06 14:42:22+00:00

Firefox 136.0a1 20250131051218 on Windows 10

1. In an existing window with some tabs, a tab in the middle of the visible tab strip got dragged to the tab left to it and a tab group created.
2. The left tab was active.
3. Ctrl+T had been pressed.

Actual result: New tab opened to the left
Expected result: New tab to the right (in my opinion as part of the tab group between the left and right tab of the group but that is likely out of scope here).
Bug: pressing Ctrl+T while a tab in a tab group is active should create a new tab in the same tab group if browser.tabs.insertAfterCurrent is set to true (open tab next to current one)
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2025-01-31 21:52:29+00:00
Resolved: 2025-02-17 14:53:04+00:00

Firefox 136.0a1 20250131152909 on Windows 10

Pressing Ctrl+T while a tab in a tab group is active should create a new tab in the same tab group if the preference browser.tabs.insertAfterCurrent is set to true (= open tab next to current one).
Bug: Sidebar button DOM structure depends on sidebar.revamp but does not update when the pref changes
Status: NEW
Priority: P2
Created: 2025-02-01 14:33:47+00:00
Resolved: 2025-02-06 17:48:36+00:00

On closer inspection, I think the fix in bug 1944627 is only treating one symptom of a more general problem.

[This code](https://searchfox.org/mozilla-central/rev/551493ea32fe6678134a2450794e6fb4d42c6adb/browser/components/customizableui/CustomizableWidgets.sys.mjs#298-313) creates the button differently depending on `sidebar.revamp`.

However, nothing updates the button if the pref changes once the button exists. The result is that the DOM structure of the button is not "correct" for the current setting of the pref (either has the observer bits when it shouldn't or doesn't have them when it should).

Although we could try to manipulate the already-created button in response to the pref in order to fix this, I suspect it would make more sense to remove the "old" `observes` mechanism entirely and replace it with updates based on `SidebarState` or similar, as that is what the new code is doing anyway and it would make the rest of the code easier to reason about and more consistent. We should then be able to get rid of `onCreated` entirely (setting `overflows: false` can be done directly on the widget properties, and the other call should probably happen after the button has been added to the DOM somewhere - then we can stop passing the button as an argument and we would not run into bug 1939639 / bug 1923326 a third time...).
Bug: test_fog_usage_reporting.py and test_fog_user_activity are failing on windows 11 upgrade
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2025-02-01 17:47:45+00:00
Resolved: 2025-02-11 15:24:42+00:00

I have a [try push](https://treeherder.mozilla.org/jobs?repo=try&resultStatus=testfailed%2Cbusted%2Cexception%2Csuccess%2Cusercancel%2Crunning%2Cpending%2Crunnable&tier=1%2C2%2C3&searchStr=telemetry&revision=1fbd015b5d493b7830a3cf7852ea99d2cbe6dade) with telemetry-tests-client running on the newer version of windows11.

I have a perma failure on opt and debug (not asan or ccov):
```
[task 2025-02-01T16:09:34.167Z] 16:09:34     INFO - fog_ping_server pings_handler received 'events' ping
[task 2025-02-01T16:09:34.206Z] 16:09:34     INFO - pingserver pings_handler received 'main' ping with reason 'shutdown'
[task 2025-02-01T16:09:34.212Z] 16:09:34     INFO - pingserver pings_handler received 'bhr' ping
[task 2025-02-01T16:09:34.245Z] 16:09:34     INFO - fog_ping_server pings_handler received 'baseline' ping
[task 2025-02-01T16:09:53.757Z] 16:09:53     INFO - pingserver pings_handler received 'main' ping with reason 'environment-change'
[task 2025-02-01T16:10:34.528Z] 16:10:34     INFO - TEST-UNEXPECTED-FAIL | telemetry/marionette/tests/client/test_fog_usage_reporting.py TestUsageReporting.test_deletion_request | AssertionError: Error waiting for ping: Timed out after 60.1 seconds
[task 2025-02-01T16:10:34.528Z] 16:10:34     INFO - Traceback (most recent call last):
[task 2025-02-01T16:10:34.528Z] 16:10:34     INFO -   File "D:\task_173842376601090\build\venv\Lib\site-packages\marionette_harness\marionette_test\testcases.py", line 198, in run
[task 2025-02-01T16:10:34.528Z] 16:10:34     INFO -     testMethod()
[task 2025-02-01T16:10:34.528Z] 16:10:34     INFO -   File "D:\task_173842376601090\build\tests\telemetry\marionette\tests\client\test_fog_usage_reporting.py", line 41, in test_deletion_request
[task 2025-02-01T16:10:34.528Z] 16:10:34     INFO -     ping1 = self.wait_for_ping(
[task 2025-02-01T16:10:34.528Z] 16:10:34     INFO -             ^^^^^^^^^^^^^^^^^^^
[task 2025-02-01T16:10:34.528Z] 16:10:34     INFO -   File "D:\task_173842376601090\build\venv\Lib\site-packages\telemetry_harness\testcase.py", line 141, in wait_for_ping
[task 2025-02-01T16:10:34.528Z] 16:10:34     INFO -     [ping] = self.wait_for_pings(
[task 2025-02-01T16:10:34.528Z] 16:10:34     INFO -              ^^^^^^^^^^^^^^^^^^^^
[task 2025-02-01T16:10:34.528Z] 16:10:34     INFO -   File "D:\task_173842376601090\build\venv\Lib\site-packages\telemetry_harness\testcase.py", line 133, in wait_for_pings
[task 2025-02-01T16:10:34.528Z] 16:10:34     INFO -     self.fail("Error waiting for ping: {}".format(e))
[task 2025-02-01T16:10:34.528Z] 16:10:34     INFO - TEST-INFO took 68413ms
[task 2025-02-01T16:10:34.625Z] 16:10:34     INFO -  IO Completion Port unexpectedly closed
```

I can disable the test, but there might be a reasonable fix for this.
Bug: Firefox appears to be blocking Browser Guard updates
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2025-02-02 10:40:23+00:00
Resolved: 2025-02-04 13:37:17+00:00

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

Steps to reproduce:

Checked the version of Browser Guard in Firefox


Actual results:

It appears stuck at version 2.6.27.


Expected results:

Ideally, the newer versions 3.x.x should be allowed to be installed in Firefox.
Reason For requirement:
Other browsers (Chrome, Edge) have version 3.0.11, and this is less prone to blocking the EASYLIST anti-tracking tool. Note: I have seen several sites that will fail to work with login or newsletter sign-up due to failure of reCaptcha code, because EASYLIST gets blocked, and appears to be used/needed in the scripted path for the reCaptcha output for human user checks. MalwareBytes tells be that Mozilla is blocking updates to 3.x.x of the Browser Guard, and as a frustrated user (fed up of having to unblock EASYLIST in the UI), I would like to know why.
Bug: Erroneous warning message
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2025-02-02 10:55:04+00:00
Resolved: 2025-02-03 08:06:00+00:00

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

Steps to reproduce:

Pasted code into the console.


Actual results:

Nothing gets pasted. Useless hurdle, "type 'allow paste' to be able to paste text" comes up, even though I indicated my intention to paste by trying to paste.


Expected results:

Text I tried to paste gets pasted without useless interruption.
Bug: Address bar autocomplete not working properly after update
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2025-02-02 13:17:28+00:00
Resolved: 2025-02-06 19:17:39+00:00

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

Steps to reproduce:

I updated my Linux system (Fedora Asahi Remix 40) through the system settings.


Actual results:

The address bar autocomplete suggestions are no longer showing up properly. The option to show search suggestions from the address is activated.


Expected results:

For example, when typing 're' in the address bar, 'reddit.com' from my bookmarks doesn't appear, so I can't just hit enter to visit the website. I don't have this problem on Firefox 133.0 (64-bit) on Windows 10.
Bug: Default page - icons for pinned pages are blurry
Status: UNCONFIRMED
Priority: --
Created: 2025-02-02 14:03:52+00:00
Resolved: 2025-02-19 12:12:44+00:00

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

Steps to reproduce:

Set Spotify to pinned page. Noticed Spotify logo is blurry 


Actual results:

There seems to be no way to make the logo higher resolution. Pretty sure this is just the site's favicon. 


Expected results:

Favicon in pinned site on default page should not be blurry/low resolution
Bug: Opening an .opml file enters infinite loop of opening tabs
Status: UNCONFIRMED
Priority: --
Created: 2025-02-02 21:16:30+00:00
Resolved: 2025-02-19 12:33:18+00:00

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

Steps to reproduce:

Open the attached .opml file with firefox.
I run firefox on Debian 12 under firejail sandbox

commands:
apt install firejail
firejail firefox

I am using default firejail profile for firefox, which in principle restricts user's access to only the Download folder, among other things. Apparently, using firejail disables default sandboxing and uses it instead.

My firefox verision according to the settings page is:
115.12.0esr


Actual results:

https://vimeo.com/1052823278/548425986a
https://vimeo.com/1052823294/9d451adfc1

When the attached file is opened, firefox enters a loop constantly creating a new tab trying to open the file.


Expected results:

I am not sure, but not this.
Bug: After clicking on "New Tab to Right" the address bar isn't focused when the new tab is blank
Status: UNCONFIRMED
Priority: P3
Created: 2025-02-03 00:02:44+00:00
Resolved: 2025-02-03 16:54:39+00:00

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

Steps to reproduce:

1. Right click on a tab.
2. The menu opens.
3. Click on "New Tab to Right".


Actual results:

The address bar isn’t focused when a new tab is opened using the + button.

This negatively impacts the user experience because users, accustomed to clicking the + button, expect to start typing the URL or search term immediately, and this behavior is not as expected.

Screen recording attached.


Expected results:

The address bar should be focused.
Bug: Ctrl+Enter keyboard shortcut in the address bar no longer adds "www." and ".com" to the address bar string on macOS
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2025-02-03 07:28:21+00:00
Resolved: 2025-02-27 13:22:05+00:00

[Tracking Requested - why for this release]:

This bug is a regression in Fx 136 from bug 1936928.

@ Emilio, I bisected this regression to this pushlog for your fix for focused element bug 1936928:

https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=870b0e5248c394c7606a55c939b064c6cdc46d4f&tochange=7290a2bc3b327fffed7abe4886a24057f935f73b

### Steps to reproduce

1. On macOS, click to focus the address bar. (I'm using macOS 15.2 Sequoia)
2. Enter `example` in the address bar.
3. Press `Ctrl` + `Enter`.

### Expected behavior

The address bar should expand `example` to `https://www.example.com/` and navigate to the website.

### Actual behavior

`Ctrl` + `Enter` opens the address bar's context menu and does not expand `example` to `https://www.example.com/`.
Bug: The address bar flickers when changing or hovering between normal and touch density modes in the Customize toolbar
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2025-02-03 10:44:31+00:00
Resolved: 2025-02-13 14:01:13+00:00

**Found in**
* 136.0a1 (2025-02-02)


**Affected versions**
* 136.0a1 (2025-02-02)
* 135.0
* 134.0.2





**Tested platforms**
* Affected platforms:  Windows 10x64, Ubuntu 24
* Unaffected platforms: macOS 12 (does not have the density option)


**Steps to reproduce**
1. Open Customize Toolbar
2. Change/ Hover between normal and touch modes.


****Expected result****
* The Address bar does not flicker.

**Actual result**
* Address bar flickers.

**Regression range**
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=13537ae67079d33202b6570bb5a61d4ee652fecb&tochange=aa2b4302bdccdbfd659158479d68c4f377237e6c 

**Additional notes**
* Attached a screen recording.
Bug: Error in landscape PDF visualization
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2025-02-03 12:01:27+00:00
Resolved: 2025-02-03 12:58:38+00:00

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

Steps to reproduce:

I opened a scanned landscape PDF (A4)


Actual results:

The PDF was displayed rotated 90deg and stretched to fill. Screenshots attatched.


Expected results:

Mozilla should display landscape PDF as is without stretching and rotating. Screenshots attatched.
Bug: 6.18% pdfpaint issue11518.pdf (OSX) regression on Tue January 28 2025
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2025-02-03 12:13:03+00:00
Resolved: 2025-02-14 04:33:30+00:00

Perfherder has detected a talos performance regression from push [f733b673b2ad392a6634ec6bb7c7e807ebee9f0f](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=f733b673b2ad392a6634ec6bb7c7e807ebee9f0f). As author of one of the patches included in that push, we need your help to address this regression.

### Regressions:

| **Ratio** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)** |  
|--|--|--|--|--| 
| [6%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,301397,1,1)  | [pdfpaint](https://firefox-source-docs.mozilla.org/testing/perfdocs/talos.html#pdfpaint) issue11518.pdf | macosx1470-64-shippable | e10s fission stylo webrender-sw | 5,676.30 -> 6,026.84 | 
### Improvements:

| **Ratio** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)** |  
|--|--|--|--|--| 
| [7%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,128298,1,1)  | [pdfpaint](https://firefox-source-docs.mozilla.org/testing/perfdocs/talos.html#pdfpaint) issue4648.pdf | windows11-64-shippable-qr | e10s fission stylo webrender-sw | 294.44 -> 274.00 | 


Details of the alert can be found in the [alert summary](https://treeherder.mozilla.org/perfherder/alerts?id=43544), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the patch(es) may be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/).

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.

You can run all of these tests on try with `./mach try perf --alert 43544`

The following [documentation link](https://firefox-source-docs.mozilla.org/testing/perfdocs/mach-try-perf.html#running-alert-tests) provides more information about this command.

For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).

If you have any questions, please do not hesitate to reach out to fbilt@mozilla.com.