av9ash/GitBugs huggingface dataset:
Bug: Favicons defined in disconnected link elements (in document fragments) will be loaded and used as the tab icon.
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2023-07-13 11:18:55+00:00
Resolved: 2023-09-29 14:05:40+00:00

`XMLHttpRequest` from a page, or subsequent to a process initialed from a page e.g. `sendMessage` to background script to execute `XMLHttpRequest`, affects the tab's favicon display.

- There shouldn't be a need to request favicon on an XHR request
- Even if requested, there shouldn't be a need to apply it to the tab

### Example 1

A local file opened in a tab e.g. `file://..../index.html` used to have a generic favicon
There is no favicon meta in that page.

Subsequent to a HTTP request from that file to `yahoo.com` and now the bookmark shows the yahoo favicon.

### Example 2
As shown in [Somehow userscript interferes with sites' favicon](https://github.com/erosman/support/issues/572), `XMLHttpRequest` causes the favicon to change multiple times.

### Stack Trace for XHR

```
load                          resource:///modules/FaviconLoader.sys.mjs:176:20
load                          resource:///modules/FaviconLoader.sys.mjs:563:70
loadIcons                     resource:///modules/FaviconLoader.sys.mjs:641:26
FaviconLoader/this.iconTask<  resource:///modules/FaviconLoader.sys.mjs:617:18
_runTask                      resource://gre/modules/DeferredTask.sys.mjs:347:18
_timerCallback/<              resource://gre/modules/DeferredTask.sys.mjs:318:20
_timerCallback                resource://gre/modules/DeferredTask.sys.mjs:337:9
_startTimer/callback/<        resource://gre/modules/DeferredTask.sys.mjs:185:18
```
Bug: [Experiment] The "WNP_MOMENTS_15" in not triggered
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-07-13 12:05:45+00:00
Resolved: 2023-07-17 08:30:49+00:00

**[Affected versions]:**
- Firefox Release 111.0.1 - Build ID: 20230321111920
- Firefox Release 115.0.2 - Build ID: 20230710165010 

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

**[Prerequisites]:**
- Have a Firefox profile older than 28 days.
- You are not connected to Firefox Sync with a Firefox account linked to a VPN subscription.
- Have any from the following Firefox locales installed: 'de', 'en-CA', 'en-US', 'fr', 'it'.
- Have the "browser.search.region" pref set to any of the following regions: 'AT', 'BE', 'CA', 'CH', 'DE', 'ES', 'FI', 'FR', 'GB', 'IE', 'IT', 'NL', 'SE', 'US'.
- Have the "Recommend extensions/feature as you browse" options from the "about:preferences" page checked.
- Have the "browser.ping-centre.log" pref set to "true" in the "about:config" page.
- Have the "Browser Console" opened.
- Have the "[user.js](https://drive.google.com/file/d/1XqSiiCuxh4KXnuH3wsNFNYE6RWcC6Dsz/view?usp=sharing)" filed saved to your PC.

**[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 the prerequisites.
3. Restart the browser until the "MOMENTS_PAGE_SET" telemetry ping related to the "WNP_MOMENTS_15" page is displayed in the "Browser Console".
4. Restart the browser again and observe the behavior.

**[Expected result]:**
- The "WNP_MOMENTS_15" page is successfully triggered.
    
**[Actual result]:**
- The "WNP_MOMENTS_15" page is not triggered.

**[Notes]:**
- The "WNP_MOMENTS_15" message from the "about:newtab#asrouter" page appears as blocked after the "MOMENTS_PAGE_SET" telemetry ping was logged and the browser restarted.
- Attached is a screen recording of the issue:
Bug: Unable to add Text or Draw over an added image in a PDF document
Status: NEW
Priority: --
Created: 2023-07-13 13:35:57+00:00
Resolved: 2023-09-22 08:19:05+00:00

**Found in**
* Nightly 117.0a1 (2023-07-12)

**Affected versions**
* Nightly 117.0a1 (2023-07-12)

**Tested platforms**
* Affected platforms: ALl 

**Steps to reproduce**
1. Open a PDF file in Firefox.
2. Click the Add an image button from the PDF toolbar.
3. Select the Text or Draw tool and use it on top of an Added image.

**Expected result**
* The image should deselect and save to the PDF when a different tool is selected.
* The user should be able to Draw or Add text over an added image without saving the entire pdf file and reopening it in Firefox.

**Actual result**
* The Draw or Text tools will not work on top of an added image. The Move cursor will work
**Regression range**
* N/A
Bug: Unable to resize an image added to the PDF if the PDF is rotated and the image spills over a second page
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-07-13 13:53:42+00:00
Resolved: 2023-07-24 07:36:59+00:00

**Found in**
* Nightly 117.0a1 (2023-07-12)

**Affected versions**
* Nightly 117.0a1 (2023-07-12)

**Tested platforms**
* Affected platforms: ALL

**Steps to reproduce**
1. Open a PDF file with multiple pages in Firefox.
2. Rotate the PDF.
3. Click the Add an image button from the PDF toolbar.
4. Place the Image so that its bottom right corner is on a second page.
5. Try to resize the image.

**Expected result**
* The user should be able to resize the image even if the bottom right corner falls on a second page.

**Actual result**
* The part of the Image that spilled on the second page is not recognized by the Tool and the user cannot resize it.
The user would have to move the added image up and then resize it, but if the image is larger than the pdf page he will not be able to resize the image.

**Regression range**
* N/A
Bug: The Added Image preview when moving it is displayed in a different location inside the PDF document
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-07-13 13:58:31+00:00
Resolved: 2023-07-13 16:42:24+00:00

**Found in**
* Nightly 117.0a1 (2023-07-12)

**Affected versions**
* Nightly 117.0a1 (2023-07-12)

**Tested platforms**
* Affected platforms: ALL

**Steps to reproduce**
1. Open a PDF file with multiple pages in Firefox.
2. Click the Add an image button from the PDF toolbar.
3. Move the added image to a different location.

**Expected result**
* The image preview should be displayed next to the Mouse cursor.

**Actual result**
* The Image preview is displayed far away from the Mouse cursor.

**Regression range**
* N/A
Bug: An unexpected error occurred on pinning/unpinning discarded tab
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-07-13 16:36:07+00:00
Resolved: 2023-10-12 14:39:21+00:00

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

Steps to reproduce:

### Pinning discarded tab:
```
(async () => {
  // Create tab
  const tab = await browser.tabs.create({ url: 'https://example.com', active: false })
  // Discard it
  await browser.tabs.discard(tab.id)
  // Pin it
  await browser.tabs.update(tab.id, { pinned: true })
})()
```

### Unpinning discarded tab:
```
(async () => {
  // Create tab
  const tab = await browser.tabs.create({ url: 'https://example.com', active: false })
  // Pin it
  await browser.tabs.update(tab.id, { pinned: true })
  // Discard it
  await browser.tabs.discard(tab.id)
  // Unpin it
  await browser.tabs.update(tab.id, { pinned: false })
})()
```


Actual results:

`await browser.tabs.update` throws an error: `An unexpected error occurred`.

### Output in Browser Console (Pin)
```
 can't access property "isAppTab", aTab.linkedBrowser.browsingContext is null    tabbrowser.js:755
    _notifyPinnedStatus chrome://browser/content/tabbrowser.js:755
    pinTab chrome://browser/content/tabbrowser.js:771
    update chrome://browser/content/parent/ext-tabs.js:934
    result resource://gre/modules/ExtensionParent.sys.mjs:1107
    withCallContextData resource://gre/modules/ExtensionParent.sys.mjs:603
    result resource://gre/modules/ExtensionParent.sys.mjs:1106
    withPendingBrowser resource://gre/modules/ExtensionParent.sys.mjs:613
    result resource://gre/modules/ExtensionParent.sys.mjs:1105
    callAndLog resource://gre/modules/ExtensionParent.sys.mjs:1066
    recvAPICall resource://gre/modules/ExtensionParent.sys.mjs:1104
    AsyncFunctionNext self-hosted:852

```

### Output in Browser Console (Unpin)
```
 can't access property "isAppTab", aTab.linkedBrowser.browsingContext is null    tabbrowser.js:755
    _notifyPinnedStatus chrome://browser/content/tabbrowser.js:755
    unpinTab chrome://browser/content/tabbrowser.js:784
    update chrome://browser/content/parent/ext-tabs.js:936
    result resource://gre/modules/ExtensionParent.sys.mjs:1107
    withCallContextData resource://gre/modules/ExtensionParent.sys.mjs:603
    result resource://gre/modules/ExtensionParent.sys.mjs:1106
    withPendingBrowser resource://gre/modules/ExtensionParent.sys.mjs:613
    result resource://gre/modules/ExtensionParent.sys.mjs:1105
    callAndLog resource://gre/modules/ExtensionParent.sys.mjs:1066
    recvAPICall resource://gre/modules/ExtensionParent.sys.mjs:1104
    AsyncFunctionNext self-hosted:852
```

The actual tab (in tab-bar) is normally pinned/unpinned.


Expected results:

No error is thrown.
Bug: Rich suggestion dissapears when complete
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2023-07-13 17:03:04+00:00
Resolved: 2023-11-20 15:38:13+00:00

If you are typing in a name, "obama" for example, you will see a photo of obama up until you type the last letter "a", at that point while the API still returns a rich suggestion for obama, it gets deduplicated with the heuristic result as they have the same URL (https://www.google.com/search?client=firefox-b-d&q=omaba) 

This is a tricky situation, we expect the hueristic result to come first  and have a stricter timeout for it, the suggestions can often timeout and are always the slowest results to return but it is also quite confusing to have the result dissapear
Bug: file:/// URLs are not truncated in tabs list view
Status: NEW
Priority: P3
Created: 2023-07-13 19:58:10+00:00
Resolved: 2023-07-18 17:23:15+00:00

Steps to reproduce:
1. Open a google doc with a long URL
2. Go to print
3. Go to Firefox view to "Recent browsing" –> "Open tabs"

Expected:
URL is truncated with ellipsis (…)

Actual:
Shows entire URL that breaks into multiple lines 

Please see attached screenshot for reference.
Bug: Built-in PDF viewer renders large page document at low resolution
Status: NEW
Priority: --
Created: 2023-07-13 20:42:19+00:00
Resolved: 2023-08-03 08:44:10+00:00

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

Steps to reproduce:

Open the PDF at https://www.vanshnookenraggen.com/_index/docs/NYC_full_trackmap.pdf in Firefox's built-in PDF viewer and then zoom in to 100% or greater.


Actual results:

The PDF is very pixelated/blurry (image attached) even though it renders flawlessly in other viewers (macOS Preview, Acrobat, Chrome's viewer, etc).


Expected results:

This example PDF contains only vector data (not bitmap), so the PDF viewer should be able to create a cleaner image upon zoom in. In fact, when viewing other PDFs such as https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf after zooming in, the text in the PDF seems to be re-rendered at a higher resolution. It's possible the large canvas size of the problematic file may is part of the problem.
Bug: AccessibleHandler.dll - AccessibleMarshal.dll
Status: NEW
Priority: P5
Created: 2023-07-14 01:50:15+00:00
Resolved: 2023-09-12 18:06:57+00:00

Steps to reproduce:

Run ccleaner on registry then looked at registry to confirm infomation.


Actual results:

Nothing at the moment


Expected results:

Don't know, I only want to report the information observed.
Bug: suggest_sponsor and suggest_non_sponsor are in metrics.yaml but can't happen?
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2023-07-14 08:26:44+00:00
Resolved: 2024-01-19 22:21:48+00:00

These were introduced by https://hg.mozilla.org/mozilla-central/rev/3179b109bcf2 and removed by https://hg.mozilla.org/mozilla-central/rev/02147a101bd9ce16c305aab7e25c0267cdcb0f3d

It looks like they can't happen anymore and thus should be removed from metrics.yaml
We should also somewhere keep a changelog for Data Science when these lists change.

We could use the Commentary field
https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/urlbar_engagement
Bug: Extension import takes longer on some stations even if the imported number of extensions is the same
Status: NEW
Priority: P2
Created: 2023-07-14 10:59:35+00:00
Resolved: 2023-12-21 14:33:41+00:00

**Found in**
* 116.0b5

**Affected versions**
* 117.0a1 (2023-07-13)
* 116.0b5















**Tested platforms**
* Affected platforms: Only some stations are affected - Windows 10x64, macOS 12

**Preconditions**
* browser.migrate.chrome.extensions.enabled:true

**Steps to reproduce**
1. Open the migration window and import extensions.


**Expected result** 
* Extensions are imported fast.


**Actual result**
* Extensions are imported slowly on some stations

**Regression range**
* Will search for one.

**Additional notes**
* Attached profilers below.
* On macOS 10.12 importing 8 out of 14 total extensions takes more than 10 seconds. On a Windows 10x64 machine importing the same 8 out of 14 total extensions takes ~3-4  seconds.
macOS 12 profiler: https://share.firefox.dev/44MU5TV
* On another Windows 10 x64 machine importing 27 extensions takes over 30 seconds. Profiler: https://share.firefox.dev/3PSoQm9
Bug: Updated to 115.02. Nothing shows upon Bookmarks Toolbar and Quick launch links on a new Tab are all gone.
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2023-07-14 13:21:58+00:00
Resolved: 2023-09-07 13:46:42+00:00

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

Steps to reproduce:

Updated Firefox to 115.02


Actual results:

Directly after the update I launched the browser. Toolbar bookmarks are not showing up and the quick launch links that populate on a new tab are gone. Everything still shows up under bookmarks, but the toolbar is blank regardless. Even if I add something new to the toolbar, it doesn't show up. 

The toolbar is NOT hidden. 


Expected results:

Toolbar stuff should show up.
Bug: [Linux] Difficulty in dragging multiple pinned tabs to a new window
Status: NEW
Priority: --
Created: 2023-07-14 13:31:37+00:00
Resolved: 2024-03-13 13:07:14+00:00

**Found in**
* Firefox 116 beta 5

**Affected versions**
* Firefox 115.0.2
* Firefox 116 beta 5
* Nightly 117.0a1

**Tested platforms**
* Affected platforms: Ubuntu 22.04 64-bit
* Unaffected platforms: Win 10 64-bit, macOS 13

**Steps to reproduce**
1. Open multiple tabs
2. Click and hold Ctrl/Cmd keys and select multiple tabs
3. Select "Pin Tabs" via context-menu
4. Click pinned tabs and drag and drop to a new window.
5. Repeat with several unpinned tabs

**Expected result**
* User is able to drag and drop selected Pinned/Unpinned tabs

**Actual result**
* Nothing happens when dragging multiple pinned tabs to a new window
* Unpinned tabs can be sometimes dragged to a new window
* Browser console error: `TypeError: tab is undefined   ext-tabs.js:468:11`

**Regression range**
* I couldn't isolate a regression range, this issue has a rather intermittent appearance
Bug: [Linux] Difficulty in dragging multiple pinned tabs to a new window
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-07-14 13:31:38+00:00
Resolved: 2023-07-17 07:13:26+00:00

**Found in**
* Firefox 116 beta 5

**Affected versions**
* Firefox 115.0.2
* Firefox 116 beta 5
* Nightly 117.0a1

**Tested platforms**
* Affected platforms: Ubuntu 22.04 64-bit
* Unaffected platforms: Win 10 64-bit, macOS 13

**Steps to reproduce**
1. Open multiple tabs
2. Click and hold Ctrl/Cmd keys and select multiple tabs
3. Select "Pin Tabs" via context-menu
4. Click pinned tabs and drag and drop to a new window.
5. Repeat with several unpinned tabs

**Expected result**
* User is able to drag and drop selected Pinned/Unpinned tabs

**Actual result**
* Nothing happens when dragging multiple pinned tabs to a new window
* Unpinned tabs can be sometimes dragged to a new window
* Browser console error: `TypeError: tab is undefined   ext-tabs.js:468:11`

**Regression range**
* I couldn't isolate a regression range, this issue has a rather intermittent appearance
Bug: [Experiment] The “Pin to taskbar Fox Doodle” spotlight from “Treatment C” is triggered when more than 7 bookmarks are saved instead of more than 6, as specified in documentation
Status: RESOLVED
Priority: P1
Resolution: WONTFIX
Created: 2023-07-14 13:33:27+00:00
Resolved: 2023-08-11 13:18:48+00:00

**[Affected versions]:**
- Firefox Release 114.0.2 - Build ID: 20230619081400
- Firefox Release 115.0.2 - Build ID: 20230710165010

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

**[Prerequisites]:**
- Have a Firefox profile, older than 6 hours and younger than 28 days.
- Firefox is not pinned to the taskbar.
- Save the “[user.js](https://drive.google.com/file/d/1RDQA152v-LfXswWmzTIssSrCucI5t3TG/view?usp=sharing)” file to disk.
- Have only the default (5) bookmarks saved.

**[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.
4. Set 2 bookmarks (for a total of 7, including the default bookmarks that are set in Firefox).
5. Restart the browser and observe the behavior.

**[Expected result]:**
- The “Fox Doodle Pin to taskbar” spotlight is displayed.

**[Actual result]:**
- The “Fox Doodle Pin to taskbar” spotlight is NOT displayed.

**[Notes]**
- In the received [documentation](https://mozilla-hub.atlassian.net/browse/QA-2005),  the “Pin to taskbar Fox Doodle” is supposed to be triggered after the user has more than 6 bookmarks saved.
- If 1 more bookmark is saved, the “Pin to taskbar Fox Doodle” will be displayed on the next browser startup.
- Attached a screen recording.
Bug: [Linux] [RTL build] Toolbars menu from Customize window is unstable
Status: NEW
Priority: P3
Created: 2023-07-14 13:49:41+00:00
Resolved: 2023-07-20 15:48:36+00:00

**Note**
This issue was reproduced in `ar` localization only. 

**Found in**
* Firefox 116 beta 5 - ar build

**Affected versions**
* Firefox 115.0.2ar
* Firefox 116 beta 5ar
* Nightly 117.0a1ar

**Tested platforms**
* Affected platforms: Ubuntu 22.04 64-bit
* Unaffected platforms: Win 10 64-bit, macOS 13

**Steps to reproduce**
1. Click on Hamburger menu -> select "More Tools" -> "Customize Toolbar...".
2. From the bottom of the page activate the "Title Bar".
3. Click on "Toolbars" button from the bottom of the page and activate the "Menu Bar" and "Bookmarks Toolbar".
4. Repeat step 3 if necessary.

**Expected result**
* User can easily interact with Toolbars menu.

**Actual result**
* After the first interaction with Toolbar drop-down, the menu flashes and the two options can't be selected.

**Regression range**
* Not a recent regression, I could reproduce this back to Firefox 113.
Bug: Firefox View in a non-private window should never show tabs from a private window
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2023-07-14 15:57:24+00:00
Resolved: 2023-07-19 16:12:57+00:00

Steps to reproduce:

1) Create a new profile with Firefox View enabled and open several tabs and close some of them.
2) Create a private window.
3) Arrange the windows so Firefox View is visible in the non-private window and the private window has focus.
4) Create a new tab in the private window and close it.
5) Look at Firefox View.

Expected:
5) The recently closed tabs list should show the same view as after step 1.

Actual:
5) The closed tabs from the non-private window aren't displayed, and the closed tab from the private window is shown.

In other words, the private URL and private tab tile from the private window has leaked into non-private Firefox window.

If you start using tabs in the non-private window Firefox View will revert to showing tabs from that window. If you then go to the private window and create and close more tabs the closed tab list from the private window return to Firefox View.
Bug: Bookmark stars are misaligned when browser.urlbar.richSuggestions.featureGate is set to true
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2023-07-14 17:29:33+00:00
Resolved: 2023-08-18 14:33:14+00:00

Tested on 117.0a1 (2023-07-13) BuildID 20230713214846.

STR:

1. Type `mozilla` in the address bar.
2. Note the position of all bookmark stars relative to the favicon for each result.

Expected Behavior:

Bookmark stars for bookmarked sites should be located at the bottom right of favicons.

Actual Behavior:
Bookmark stars for bookmarked sites are misaligned.

Mozregression returned

Last good revision: 8bed6ab81a11bda3f3d3a4e4d9239f901d899a6d
First bad revision: 37def70ef36929a490fabd36a7b31c31c2bbbe66
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=8bed6ab81a11bda3f3d3a4e4d9239f901d899a6d&tochange=37def70ef36929a490fabd36a7b31c31c2bbbe66

Setting `browser.urlbar.richSuggestions.featureGate`  to `false` immediately resolves the issue on Linux, and after a restart on Windows.

`mozregression --pref browser.urlbar.richSuggestions.featureGate:true --bad 116` returned

Last good revision: 27a022ccd011a0d52e64fe813bbc54d17c869597
First bad revision: cdcf9d894d0573d249e80dbf465226cd134caa68
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=27a022ccd011a0d52e64fe813bbc54d17c869597&tochange=cdcf9d894d0573d249e80dbf465226cd134caa68
Bug: ASRouter devtools "modify" method fails if message doesn't have groups property
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2023-07-14 21:38:55+00:00
Resolved: 2023-07-18 21:54:28+00:00

When testing feature callouts from the devtools, I noticed that it throws if the message you input lacks a `groups` property. You have to add `"groups": []` to get it to show. We should figure out why that is and get rid of the requirement, since messages don't actually need to have a `groups` property. Taking the existing feature callout messages and plugging them into the devtools fails because of this. So we should definitely make sure that all existing messages in tree that work correctly in production will also work from the devtools.
Bug: 'Recently Closed Tabs' is missing 'Reopen all Tabs' entry
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-07-16 10:10:48+00:00
Resolved: 2023-08-29 22:01:31+00:00

str:
1. open a second tab
2. close it again
3. press alt and go to history-> recently closed tabs. notice 'reopen all tabs' is missing below the seperator
4. go to hamburger menu -> history -> recently closed tabs. notice 'reopen all tabs' is missing at the very bottom

error in browser console after step 3:
```
Key key_undoCloseTab of menuitem Wikipedia could not be found menu.js:295:21
    accelText chrome://global/content/elements/menu.js:295
    _computeAccelTextFromKeyIfNeeded chrome://global/content/elements/menu.js:300
    render chrome://global/content/elements/menu.js:327
    connectedCallback chrome://global/content/elements/menu.js:343
    populateUndoSubmenu chrome://browser/content/browser-places.js:644
    onpopupshowing chrome://browser/content/browser.xhtml:1
```

i've done a bisection and landed on this pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=14f6c2036ea433f941cbf87dd29e7ef5f1add1a7&tochange=aa4368bfb81a757e2ae5488aca4791a532b566f1 which suggests that this regression was introduced with Bug 1819675.