av9ash/GitBugs huggingface dataset:
Bug: Sorting input history using use_count in Adaptive History Autofill and UrlbarProviderInputHistory may be wrong
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-05-20 06:57:29+00:00
Resolved: 2022-06-17 11:59:17+00:00

Currently, [we store input history data as is = case-sensitive](https://searchfox.org/mozilla-central/rev/9f95c41a962c9228f569f8a6b2c30edbb50b65ae/browser/components/urlbar/UrlbarUtils.jsm#884-898). That means if user visits `https://www.mozilla.org/contribute/` by user’s input `m` and visits the same URL by `M` is stored as different record.
As [Adaptive History Autofill](https://searchfox.org/mozilla-central/rev/9f95c41a962c9228f569f8a6b2c30edbb50b65ae/browser/components/urlbar/UrlbarProviderAutofill.jsm#588-604) and [UrlbarProviderInputHistory](https://searchfox.org/mozilla-central/rev/9f95c41a962c9228f569f8a6b2c30edbb50b65ae/browser/components/urlbar/UrlbarProviderInputHistory.jsm#52-73) sort the table with case-insensitive using `use_count`, above `m` and `M` is handled as different data even the URL is same. Therefore, the sorting may be wrong.
Bug: Bookmark with javascript address in folder via 'open all' does not work
Status: NEW
Priority: P5
Created: 2022-05-20 08:14:05+00:00
Resolved: 2024-02-27 17:46:33+00:00

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

Steps to reproduce:

I have created a bookmark whose address is calculated using javascript with dynamic parameters.

Example: 
javascript:(function(){function z(d){d=String(d);d.length<2&&(d="0"+d);return d}var c=new Date,b="";b+=z(c.getDate())+"-"+z(c.getMonth()+1)+"-"+c.getFullYear();location.href="https://www.trauer36.de/traueranzeigen-suche/erscheinungstag-"+b})();

This bookmark is in a subfolder.


Actual results:

If I use this bookmark (alone), it works fine.
If I say: open all bookmarks (of the subfolder), it doesn't work!
It prints out only the javascript code in the address line.


Expected results:

Opening the bookmark via 'open all bookmarks' of a folder should also work in this case in the same way as when (individually) opening the bookmark in the folder.
Bug: [Experiment] The user is wrongly enrolled in the “Download Mobile Regular ECO2204 EN” study even if he is not signed in to Firefox Account
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-05-20 09:33:29+00:00
Resolved: 2022-05-31 08:33:46+00:00

**[Notes]:**
- Also the “Download Firefox mobile browser” spotlight is shown.

**[Affected versions]:**
- Firefox Release 100.0.1 (Build ID: 20220513165813) 

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

**[Prerequisites]:**
- Have the Firefox Release browser, en* locale installed.
- Have the [user.js](https://drive.google.com/file/d/1DBZPX0JAZ24vE8g5GCy1Qh3hOHOoaFsy/view?usp=sharing) file saved on your computer.
- Don’t be signed in to Firefox Sync.
- Have a Firefox profile older than 28 days. (you can copy this [file](https://drive.google.com/file/d/1DBZPX0JAZ24vE8g5GCy1Qh3hOHOoaFsy/view?usp=sharing) on the Firefox profile folder)
- Have user activity of 14-20 days out of the past 28 days.

**[Steps to reproduce]:**
1. Open the Firefox browser with the profile from prerequisites.
2. Navigate to the "about:support" page and open the Profile Folder.
3. Copy and paste the [user.js](https://drive.google.com/file/d/1DBZPX0JAZ24vE8g5GCy1Qh3hOHOoaFsy/view?usp=sharing) file in the folder and restart the browser.
4. Navigate to the “about:studies” page and check the contents of the page.

**[Expected result]:**
- The study is not displayed on the page.

**[Actual result]:**
- The study is marked as active.

**[Additional notes]:**
- Based on the [mana page](https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=162269773) of the experiment, the enrollment shouldn’t occur if the user is not signed in to Firefox Account.
- This issue is reproducible with all the branches.
- Attached is a screen recording of the issue.
Bug: "Take Screenshot" menu for frames should be hidden if the Screenshots is disabled
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2022-05-20 10:25:44+00:00
Resolved: 2022-07-20 07:25:28+00:00

## Steps to reproduce:

1. Set `extensions.screenshots.disabled` to `true` in about:config.
2. Right-click on an iframe.

## Actual results:

The "This Frame" menu includes the "Take Screenshot" menu.

## Expected results:

The "Take Screenshot" menu should be hidden if the Screenshots is disabled.
Bug: minCharsThreshold pref breaks in some adaptive history autofill cases
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-05-20 10:26:19+00:00
Resolved: 2022-05-21 02:41:09+00:00

**Affected versions**
      * Nightly 102.0a1 (2022-05-20)

**Affected platforms**
     
      * Windows
      * Ubuntu 20.04 (not confirmed)
      * Mac 11 (not confirmed)

**Preconditions**
1. user_pref("**browser.urlbar.autoFill.adaptiveHistory.enabled**", true); 
2. user_pref("**browser.urlbar.autoFill.adaptiveHistory.minCharsThreshold**",0);

**Steps to reproduce**
1. Open Firefox.
2. Copy paste an URL: https://www.youtube.com/watch?v=UMPlyR1TT04
3. Input youtube and select the previously pasted URL from FxSuggest -> adaptive hist is generated for youtube SearchString.
4. Once the adaptive history entry is created, open a new tab and input the searchString: youtube, letter by letter.
5. Modify the value of **browser.urlbar.autoFill.adaptiveHistory.minCharsThreshold** to 1, 2, 3, 4

**Expected result**
In order to trigger any adaptive history autofill, the search string the user is typing must be at least this many characters. Its default value is 0, which means there is no threshold.

**Actual result**
The value to trigger adaptive history seems to be the lenght of the SearchString, the minchartreshhold seems to function as a filter for the SearchStrings: e.g for a value of 4, an "you" SearchString user input will be ignored as a valid SearchString match to trigger autofill, but it will trigger after an "yout" has been input, which won't match anymore the SearchString.

**Regression range**
* Isn't necesarily a regression, since the minchartreshhold has been introduced by bug 1769585, but marking as such, since the minCharsTreshold seems to affect the adaptive autofill (based on our understanding of it).

**Note**
1. Regardless of the value set for **browser.urlbar.autoFill.adaptiveHistory.minCharsThreshold**,  the trigger seems to be the lenght of the SearchString
2. If the len(SearchString) is lower than the minCharsThreshold, the adaptive History will trigger after the SearchString is exceeded (before bug 1769585, exceeding the SearchString would continue autofilling the origin).
3. S3 severity for the time being, assuming a high piority will be assigned to figuring the expected behaviors
4. Although best practices would've dictated to split this into several separate bugs, we've chosen not to do so until initial triage and dev. investigation is done
Bug: [Experiment] The "Import" ECO spotlight is not displayed on Firefox profiles with the default number of bookmarks
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-05-20 11:21:43+00:00
Resolved: 2022-07-06 13:10:28+00:00

**[Affected versions]:**
- Firefox Release 100.0.1 - Build ID: 20220513165813

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

**[Prerequisites]:**
- Have a new Firefox profile created.
- Have the "nimbus.debug" pref set to true in the "about:config" page.
- Have another browser (e.g. Chrome) with multiple bookmarks saved.

**[Steps to reproduce]:**
1. Open the Firefox profile from the prerequisites.
2. Navigate to the "about:studies?optin_slug=import-infrequent-eco2204-en&optin_branch=treatment-a&optin_collection=nimbus-preview" URL.
3. Restart the browser and observe the behavior.
4. Go to the browser's "File" menu and select the "Import From Another Browser..." option.
5. Complete the import flow and restart the browser.
6. Observe the behavior.

**[Expected result]:**
Step 3: The "Import" ECO spotlight is displayed.

Step 6: The "Import" ECO spotlight is **NOT** displayed.

**[Actual result]:**
Step 3: The "Import" ECO spotlight is **NOT** displayed.

Step 6: The "Import" ECO spotlight is wrongly displayed after an import bookmarks action was performed.

**[Notes]:**
- According to the [experiment's mana page](https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=162276975) the "Import" ECO should be displayed only if users have the default number of bookmarks in Firefox (5 bookmarks).
- We observed in the message targeting the `totalBookmarksCount > 5` filter and according to this, we will trigger the spotlight only if more than 5 bookmarks are saved.
- Attached a screen recording of the issue.

@Dan, could you please take a look over this?
Bug: [Experiment] The “Get Firefox Mobile” page is not focused after clicking the “Send me a link” button
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-05-20 12:48:40+00:00
Resolved: 2022-05-31 08:31:24+00:00

**[Affected versions]:**
- Firefox Release 100.0.1 (Build ID: 20220513165813) 

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

**[Prerequisites]:**
- Have the Firefox Release browser, en* locale installed.
- Have a new Firefox profile created.
- Have the “nimbus.debug” pref set to true.

**[Steps to reproduce]:**
1. Open the Firefox browser with the profile from prerequisites.
2. Navigate to the ‘about:studies?optin_slug=download-mobile-regular-eco2204-en&optin_branch=treatment-a&optin_collection=nimbus-preview’ URL.
3. Restart the browser.
4. Click the “Send me a link” button from the “Download Firefox Mobile” spotlight.
5. Observe the behavior of the newly opened tab.

**[Expected result]:**
- The opened tab is focused.

**[Actual result]:**
- The “Get Firefox Mobile” page is opened but is not focused.

**[Notes]:**
- Attached is a screen recording of the issue.
Bug: Missing the crash report prompt on Ubuntu 22.04
Status: NEW
Priority: --
Created: 2022-05-20 12:50:15+00:00
Resolved: 2022-05-23 08:54:56+00:00

Affected Versions:
Nightly 102 

Tested on:

Ubuntu 22.04 - Wayland, Intel(R) HD Graphics 630
Ubuntu 22.04 - Wayland, Nvidia GTX 1050

Steps to reproduce:

1. Launch Firefox, open several tabs, wait for pages to load;
2. Open a new tab and type about:crashparent;
3. Click Enter.

Expected Results:
The crash report prompt should be displayed and Firefox is restarted.

Actual Results:
Firefox is closed and nothing is displayed.

Note:

This issue happens on Ubuntu 22.04 - Wayland, Intel(R) HD Graphics 630 every time and is intermittent on Ubuntu 22.04 - Wayland, Nvidia GTX 1050
Bug: [Intermittent] The number of tabs and the websites are not properly restored after forcing a crash and reopening the session from the crash prompt
Status: NEW
Priority: --
Created: 2022-05-20 13:04:47+00:00
Resolved: 2022-08-01 09:07:28+00:00

**[Notes]:**
- After restoring the browsing session using the Mozilla Crash Report dialog, the following error is displayed in the Browser Console:
`BackgroundUpdate: maybeScheduleBackgroundUpdateTask: exiting after uncaught exception in maybeScheduleBackgroundUpdateTask!
Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWinTaskSchedulerService.registerTask]", result: 2147500037, filename: "resource://gre/modules/TaskSchedulerWinImpl.jsm", lineNumber: 51, columnNumber: 0, data: null, stack: "registerTask@resource://gre/modules/TaskSchedulerWinImpl.jsm:51:16\nregisterTask@resource://gre/modules/TaskScheduler.jsm:136:18\n_registerBackgroundUpdateTask@resource://gre/modules/BackgroundUpdate.jsm:287:38\n", location: XPCWrappedNative_NoHelper }`

**[Affected versions]:**
- Firefox RC 100.0.1, Build ID: 20220513165813
- Firefox Beta 101.0b9, Build ID: 20220519220322
- Firefox Nightly 102.0a1, Build ID: 20220520093126

**[Affected platforms]:**
- Windows 11 x64

**[Prerequisites]:**
- Have Firefox installed.

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Open a new tab and click one of the top sites.
3. Repeat step 2 with other top sites.
4. Open a new tab and navigate to the "about:crashparent" page.
5. From the Mozilla Crash Report dialog, click the "Restart Firefox" option.
6. Observe what happens next.

**[Expected result]:**
- The number of tabs opened at steps 2 and 3 are restored and the websites correctly load.

**[Actual result]:**
- A smaller number of tabs are restored with the websites from steps 2 and 3 being replaced by new tabs.

**[Additional notes]:**
- This issue is also reproducible with the “Open previous windows and tabs” checked option on the “about:preferences” page.
- This issue wasn’t noticed on other OSes besides Windows 11.
- [Here](https://drive.google.com/file/d/1pVGrNNfxok4jUQxgBqlzw5FMKrZeeOpt/view?usp=sharing) is a screen recording with the issue.
Bug: Gap on fullscreen videos
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-05-20 17:48:43+00:00
Resolved: 2022-05-20 18:00:52+00:00

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

Steps to reproduce:

Use a 27" monitor with 1080p resolution, Open any video on firefox and switch it to full-screen.
On my 21" it works just fine, It also happens once if i switch back from fullscreen and back again it fixes it, But if i close firefox and open again the gap shows again!


Actual results:

It shows a gap between the video and desktop, showing the wallpaper on the left and top side.


Expected results:

The fullscreen video should fill the whole screen not show a gap between the video and desktop.
Bug: Telemetry for some types of autofill is no longer correctly handled
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-05-20 18:31:44+00:00
Resolved: 2022-08-30 13:46:47+00:00

Bug 1597791 deprecated the `urlbar.picked.autofill` scalar in favor of three new scalars, but there are a few other types of autofill results we forgot about:

* about pages (UrlbarProviderAutofill)
* ~~Search engine domains (UrlbarProviderAutofill)~~ [1]
* Preloaded top sites (UrlbarProviderPreloadedSites)
* ~~Token alias engines (UrlbarProviderTokenAliasEngines)~~ [1]

For example, if you autofill "about:config" and press enter, a couple of errors will be logged:

> urlbar.picked.autofill_undefined - Unknown scalar. 
> Unsupported telemetry type autofill_undefined

We could add a general `autofill_other` fallback, but we should probably add individual types/scalars for all these.

[1] Edit: Actually search engine domain autofill and token alias engine autofill are not currently reported as autofill in telemetry. That's because those results aren't URL results, and [only URL results can be reported as autofill](https://searchfox.org/mozilla-central/rev/8bd5597baef9be63fc4689a69e550d607dc68444/browser/components/urlbar/UrlbarUtils.jsm#1188-1191). That logic goes back a ways and I don't want to litigate it now, so I'll drop these two from this bug.
Bug: The "Add new tab" button does not stay fixed in the tab bar
Status: NEW
Priority: P3
Created: 2022-05-20 19:15:02+00:00
Resolved: 2024-10-11 02:49:39+00:00

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

Steps to reproduce:

Clicked on the "Add new tab" button multiple times and removed tabs.
Added video to show the bug.

I use macOS Monterey on M1. Firefox v. 100.


Actual results:

The "Add new tab" button is not fixed when enough tabs are closed or added.


Expected results:

The "Add new tab" button is supposed to stay fixed in the Tab bar when it's filled with enough tabs and "List all tabs" does not replace it when appears.

Also, when the "List all tabs" button appears, after enough tabs are created, it does not use remained precious free space in the right corner of the tabs bar. 

Thanks!
Bug: Tik-tok likes and comments on comments are broken for some profiles
Status: NEW
Priority: P3
Created: 2022-05-20 20:03:50+00:00
Resolved: 2022-06-08 01:00:10+00:00

This bug is a followup from the investigation into bug 1753874.  Even with the intervention there, with my main profile (but no others so far), on Tik-tok, I cannot like or comment on comments -- likes on comments don't survive page reloads and replies to comments produce a "failed to comment" notification.  I haven't been able to find any pref changes that affected it and troubleshooting mode doesn't help.

Amazingly, [I have been able to test this successfully with mozregression](https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=7bc2dd06085f53993037b4fc78ee651c5afc7671&tochange=1d03336aafcfb8af4e39d61a52ff4983aaa4d007).  We just missed the 1 year window for autoland so the range is kind of big but I believe it can be narrowed further to just the Apr 10, 2021 commits.

I'm currently trying to narrow this window.
Bug: Only use the zap gradient on the setup card and colourway closet expiry blurb in Firefox View with default themes
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2022-05-20 23:48:11+00:00
Resolved: 2022-10-03 14:50:28+00:00

The "zap-gradient" (which gets added to the sync setup card in bug 1770499 - its the purple -> pink -> orange gradient border) clashes terribly with a lot of non-built-in themes. We use a [check for a `:-moz-lwtheme` pseudo](https://searchfox.org/mozilla-central/source/browser/themes/shared/customizableui/panelUI-shared.css#31-33) to fall back to a normal solid color in places like the separator under the FxA main menu item. AFAICT this approach is not currently available for in-content stylesheets & elements however, so we need another solution.
Bug: cant switch tabs/load pages on nightly on OpenBSD
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-05-21 08:12:27+00:00
Resolved: 2022-05-25 08:05:45+00:00

with a new profile and a self built mozilla-central binary, i cant switch tabs or display anything, and stderr shows a continuous stream of:
```
Assertion failure
assert@resource:///modules/AsyncTabSwitcher.jsm:500:36
preActions@resource:///modules/AsyncTabSwitcher.jsm:568:10
handleEvent@resource:///modules/AsyncTabSwitcher.jsm:1089:12
```
note that i havent tried running a binary from m-c since a while, but 101.0b9 (built from ports so with system nss/nspr and some OpenBSD patches) runs fine without issues.

since AsyncTabSwitcher.jsm hasnt changed since a while, im not even sure those error messages can be related to the failure to load pages. I've tried disabling the socket/network process via network.process.enabled=false but that doesnt help.
Bug: Artifacts with VAAPI
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-05-21 09:02:24+00:00
Resolved: 2022-05-21 10:39:55+00:00

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

Steps to reproduce:

Using Nightly 102.0a1 (20220520190447) with Debian sid/unstable with *libva2* 2.14.0-1 and *gnome-shell* 42.1-1 (X session), play a video from YouTube with the plugin *h264ify*.


Actual results:

There is a regression, that video artifacts are shown when using VAAPI. Without VAAPI no artifacts are shown.


Expected results:

No artifacts should be shown.
Bug: Intermittent browser/components/urlbar/tests/browser/browser_closePanelOnClick.js | Test timed out - | Found a tab after previous test timed out: about:robots -
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2022-05-21 09:41:18+00:00
Resolved: 2022-07-25 23:15:41+00:00

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

---
```
[task 2022-05-21T07:51:09.570Z] 07:51:09     INFO - TEST-START | browser/components/urlbar/tests/browser/browser_closePanelOnClick.js
[task 2022-05-21T07:52:39.626Z] 07:52:39     INFO - TEST-INFO | started process screenshot
[task 2022-05-21T07:52:39.823Z] 07:52:39     INFO - TEST-INFO | screenshot: exit 0
[task 2022-05-21T07:52:39.826Z] 07:52:39     INFO - Buffered messages logged at 07:51:09
[task 2022-05-21T07:52:39.826Z] 07:52:39     INFO - Entering test bound 
[task 2022-05-21T07:52:39.827Z] 07:52:39     INFO - Awaiting for the urlbar panel to open
[task 2022-05-21T07:52:39.827Z] 07:52:39     INFO - Urlbar panel opened
[task 2022-05-21T07:52:39.828Z] 07:52:39     INFO - Buffered messages logged at 07:51:10
[task 2022-05-21T07:52:39.828Z] 07:52:39     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_closePanelOnClick.js | Found a valid element: browser - true == true - 
[task 2022-05-21T07:52:39.829Z] 07:52:39     INFO - Awaiting for the urlbar panel to close
[task 2022-05-21T07:52:39.829Z] 07:52:39     INFO - Buffered messages finished
[task 2022-05-21T07:52:39.830Z] 07:52:39     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_closePanelOnClick.js | Test timed out - 
[task 2022-05-21T07:52:39.830Z] 07:52:39     INFO - Urlbar panel closed
[task 2022-05-21T07:52:39.831Z] 07:52:39     INFO - GECKO(2956) | MEMORY STAT | vsize 19406546MB | vsizeMaxContiguous 65762439MB | residentFast 2038MB
[task 2022-05-21T07:52:39.831Z] 07:52:39     INFO - TEST-OK | browser/components/urlbar/tests/browser/browser_closePanelOnClick.js | took 90123ms
[task 2022-05-21T07:52:39.831Z] 07:52:39     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-05-21T07:52:39.832Z] 07:52:39     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_closePanelOnClick.js | Found a tab after previous test timed out: about:robots - 
[task 2022-05-21T07:52:39.832Z] 07:52:39     INFO - checking window state
[task 2022-05-21T07:52:39.832Z] 07:52:39     INFO - TEST-START | browser/components/urlbar/tests/browser/browser_content_opener.js
```