av9ash/GitBugs huggingface dataset:
Bug: There is no way to open previously closed tabs/next-to-last session or last session upon updating Firefox
Status: NEW
Priority: --
Created: 2022-02-10 07:07:54+00:00
Resolved: 2024-02-27 16:52:51+00:00

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

Steps to reproduce:

Exist/be a normal user expecting my browser to behave normally.

Snark remarks aside, I had some tabs open and closed Firefox. Then upon opening Firefox again, it asked me to update. So I did. Then, suddenly, the option to "Restore last browsing session" disappeared so I lost all my open tabs.

And, no, just opening "Recent tabs" doesn't work because I had multiple windows open, so there's no way to restore it.


Actual results:

I lost all my progress in my last session upon updating.
I also always lose my progress in second-/third-/n-to-last sessions.


Expected results:

YOU SHOULD BEHAVE LIKE CHROME!!!!
If I hit Ctrl+Shift+T, you should:
1. Open the previously open (but now closed) tab.
2. If the previous tab was in a window/session, OPEN THAT SESSION.
3. Similar to the above, OPEN PREVIOUS SESSIONS, regardless how many, upon Ctrl+Shift+T.

Note: This happens on all of Linux, Windows, and Mac. I'm just so sick of losing my progress that I happen to be typing this on what I'm using now, so don't let the User-Agent confuse you.
Bug: "Close reader view" (X) doesn't work at first attempt.
Status: RESOLVED
Priority: --
Resolution: INACTIVE
Created: 2022-02-10 10:28:55+00:00
Resolved: 2022-02-10 10:41:41+00:00

Steps to reproduce:

After entering Reader view for a web page, I want to exit it by clicking on "X" ("Close reader view") 


Actual results:

"Close reader view" (X) doesn't work at first attempt: it works only with a 2nd attempt.


Expected results:

"Close reader view" (X) should work at first attempt
Bug: Perma browser/components/tests/browser/browser_browserGlue_upgradeDialog.js | A promise chain failed to handle a rejection: null has no properties - stack: enableTheme@chrome://browser/content/upgradeDialog.js:93:23
Status: RESOLVED
Priority: P5
Resolution: FIXED
Created: 2022-02-10 13:14:55+00:00
Resolved: 2022-03-10 08:31:46+00:00

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

---
```
[task 2022-02-10T11:40:43.748Z] 11:40:43     INFO - TEST-PASS | browser/components/tests/browser/browser_browserGlue_upgradeDialog.js | Incorrectly handling clicks would have triggered exception - true == true - 
[task 2022-02-10T11:40:43.749Z] 11:40:43     INFO - Buffered messages finished
[task 2022-02-10T11:40:43.750Z] 11:40:43     INFO - TEST-UNEXPECTED-FAIL | browser/components/tests/browser/browser_browserGlue_upgradeDialog.js | A promise chain failed to handle a rejection: null has no properties - stack: enableTheme@chrome://browser/content/upgradeDialog.js:93:23
[task 2022-02-10T11:40:43.750Z] 11:40:43     INFO - Rejection date: Thu Feb 10 2022 11:40:43 GMT+0000 (Coordinated Universal Time) - false == true - JS frame :: resource://testing-common/PromiseTestUtils.jsm :: assertNoUncaughtRejections :: line 271
[task 2022-02-10T11:40:43.750Z] 11:40:43     INFO - Stack trace:
[task 2022-02-10T11:40:43.750Z] 11:40:43     INFO - resource://testing-common/PromiseTestUtils.jsm:assertNoUncaughtRejections:271
[task 2022-02-10T11:40:43.750Z] 11:40:43     INFO - chrome://mochikit/content/browser-test.js:handleTask:1017
[task 2022-02-10T11:40:43.752Z] 11:40:43     INFO - Leaving test bound double_click
[task 2022-02-10T11:40:43.753Z] 11:40:43     INFO - Entering test bound theme_change
[task 2022-02-10T11:40:43.754Z] 11:40:43     INFO - Console message: [JavaScript Error: "TypeError: null has no properties" {file: "chrome://browser/content/upgradeDialog.js" line: 93}]
[task 2022-02-10T11:40:43.757Z] 11:40:43     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-02-10T11:40:43.758Z] 11:40:43     INFO - TEST-UNEXPECTED-FAIL | browser/components/tests/browser/browser_browserGlue_upgradeDialog.js | Uncaught exception in test - Theme is active - threw exception: TypeError: theme is null
[task 2022-02-10T11:40:43.759Z] 11:40:43     INFO - Not taking screenshot here: see the one that was previously logged
```
Bug: Global default zoom level set in preferences not working on new home screen
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-02-10 14:53:40+00:00
Resolved: 2022-02-11 13:53:32+00:00

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

Steps to reproduce:

Call for a new tab (command-T, defaults to home screen as set in preferences).


Actual results:

Home screen appears at 100% zoom level - not user defined zoom level (in this case) of 150%. "100%" appears at the far right of the search/address bar. Clicking "100%" zooms the home screen to 150%. 


Expected results:

New tab for home screen should appear at global zoom level (in this case 150%) set in preferences. This was the behavior in previous versions.
Bug: Opening a link to a page that has no title in a new tab shows an incorrect title in the tab
Status: NEW
Priority: --
Created: 2022-02-10 17:29:08+00:00
Resolved: 2023-09-06 11:29:19+00:00

1. Go to Google and search for "linux md time to add disk to raid6"
2. The first result is a page on www.ewams.net, middle click on it.
3. The page opens in a new tab but I see "google.com/url?......" as the tab title. This is the url to the link clicked which presumably redirects to the actual site.

The page itself has no title (it contains an empty title tag) so the tab title should be "ewams.net/..." and that is indeed what you get when normal clicking on the link.
Bug: Firefox in Linux. Linux locale is en_IE - IRELAND. Spell check language is English ( US ) but should be English ( British )
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-02-10 18:41:37+00:00
Resolved: 2022-02-11 07:20:54+00:00

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

Steps to reproduce:

PRETTY_NAME="Ubuntu 20.04.3 LTS". Firefox 96 in Linux. OS Locale setting is LANG=en_IE.UTF-8.

My son wants to do English homework online. He is Irish and we use British English here in Ireland not US English. Son wants to use the word "colour" ( correct British spelling ), in the Seesaw web app textarea input, you can see the screenshot.


Actual results:

Spell check corrects "colour" to "color" 


Expected results:

Correct spelling in Ireland is the British English "colour"
Bug: Intermittent browser/base/content/test/about/browser_aboutHome_search_telemetry.js | Uncaught exception in test - undefined - timed out after 50 tries.
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2022-02-11 04:35:52+00:00
Resolved: 2022-07-25 23:05:21+00:00

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

---
```
INFO - TEST-START | browser/base/content/test/about/browser_aboutHome_search_telemetry.js
[task 2022-02-11T03:10:21.823Z] 03:10:21     INFO - TEST-INFO | started process screentopng
[task 2022-02-11T03:10:22.538Z] 03:10:22     INFO - TEST-INFO | screentopng: exit 0
[task 2022-02-11T03:10:22.539Z] 03:10:22     INFO - Buffered messages logged at 03:10:16
[task 2022-02-11T03:10:22.539Z] 03:10:22     INFO - Entering test bound 
[task 2022-02-11T03:10:22.539Z] 03:10:22     INFO - Check that performing a search fires a search event and records to Telemetry.
[task 2022-02-11T03:10:22.540Z] 03:10:22     INFO - Buffered messages finished
[task 2022-02-11T03:10:22.541Z] 03:10:22     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/about/browser_aboutHome_search_telemetry.js | Uncaught exception in test - undefined - timed out after 50 tries.
[task 2022-02-11T03:10:22.541Z] 03:10:22     INFO - Leaving test bound 
[task 2022-02-11T03:10:22.541Z] 03:10:22     INFO - GECKO(2320) | MEMORY STAT | vsize 11419MB | residentFast 468MB | heapAllocated 212MB
[task 2022-02-11T03:10:22.542Z] 03:10:22     INFO - TEST-OK | browser/base/content/test/about/browser_aboutHome_search_telemetry.js | took 5618ms
[task 2022-02-11T03:10:22.547Z] 03:10:22     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-02-11T03:10:22.548Z] 03:10:22     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/about/browser_aboutHome_search_telemetry.js | Found an unexpected tab at the end of test run: about:home - 
[task 2022-02-11T03:10:22.549Z] 03:10:22     INFO - checking window state
[task 2022-02-11T03:10:22.550Z] 03:10:22     INFO - GECKO(2320) | JavaScript error: resource:///actors/ContentSearchParent.jsm, line 664: TypeError: can't access property "addEventListener", browser is null
[task 2022-02-11T03:10:22.551Z] 03:10:22     INFO - GECKO(2320) | JavaScript error: resource:///actors/ContentSearchParent.jsm, line 664: TypeError: can't access property "addEventListener", browser is null
[task 2022-02-11T03:10:22.552Z] 03:10:22     INFO - TEST-START | browser/base/content/test/about/browser_aboutNetError.js
```
Bug: Intermittent browser/components/aboutlogins/tests/browser/browser_sessionRestore.js | Uncaught exception in test - Waiting for login to be displayed in page - threw exception: TypeError: can't access property "_loginGuidsSortedOrder", loginList is null
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2022-02-11 08:22:55+00:00
Resolved: 2022-07-13 13:12:01+00:00

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

---
```

```
Bug: Intermittent [tier 2] browser/components/sessionstore/test/browser_sessionStoreContainer.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. -
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2022-02-11 09:40:08+00:00
Resolved: 2022-03-08 17:03:45+00:00

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

---
```
[task 2022-02-11T09:04:36.971Z] 09:04:36     INFO - TEST-PASS | browser/components/sessionstore/test/browser_sessionStoreContainer.js | session restore should have each container's cookie - 
[task 2022-02-11T09:04:36.974Z] 09:04:36     INFO - Leaving test bound test
[task 2022-02-11T09:04:36.977Z] 09:04:36     INFO - Buffered messages finished
[task 2022-02-11T09:04:36.981Z] 09:04:36     INFO - TEST-UNEXPECTED-FAIL | browser/components/sessionstore/test/browser_sessionStoreContainer.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - 
[task 2022-02-11T09:04:36.984Z] 09:04:36     INFO - GECKO(5064) | MEMORY STAT | vsize 2120960MB | vsizeMaxContiguous 66488538MB | residentFast 396MB | heapAllocated 112MB
[task 2022-02-11T09:04:36.989Z] 09:04:36     INFO - TEST-OK | browser/components/sessionstore/test/browser_sessionStoreContainer.js | took 46601ms
```
Bug: Page url in address bar doesn't change when navigating to another page with history api
Status: NEW
Priority: P3
Created: 2022-02-11 09:41:34+00:00
Resolved: 2024-08-23 09:44:50+00:00

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

Steps to reproduce:

Open any video on youtube.com. Click on address bar and edit the address in any way (e.g. delete a character at the end of the address). After that, without pressing enter or anything, click on a thumbnail for another video.


Actual results:

Another video opened, but the url in the address bar hasn't changed (it's just as it was after editing it). After navigating to any number of other videos, the address stays the same as you left it after editing.


Expected results:

The address should have changed to reflect the new video url.
Bug: Disable JS Load Restrictins if autoadmin.global_config_url is set
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-02-11 15:24:57+00:00
Resolved: 2022-04-25 20:38:52+00:00

`autoadmin.global_config_url` is a pref I didn't know about until now that allows you to load an autoconfig script from the network.

This is probably (maybe?) whats causing entries in the JS Load Telemetry - if `general.config.filename` is false but `autoadmin.global_config_url` is true; we will not disable the security checks.

We should also check the follow prefs to disable the security checks:
 - autoadmin.global_config_url
 - autoadmin.failover_to_cached  (this will cause a failover to a hardcoded `failover.jsc` file in the profile directory)
Bug: Dismissing the search engine removal infobar by interaction creates a dotted line around the newtab page
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-02-11 16:17:20+00:00
Resolved: 2022-02-21 13:48:29+00:00

**Affected versions**
* Fx98.0b3

**Affected platforms**
* Windows 10
* Ubuntu 20.04

**Steps to reproduce**
1. Launch Firefox.
2. Trigger the search engine removal infobar. (steps in bug 1754454 can be used).
3. Click the 'OK' button on the infobar.

**Expected result**
* Infobar is dismissed without issues.

**Actual result**
* A dotted white line appears around the newtab page content.

**Additional notes**
* The issues doesn't occur on macOS.
* The issue also occurs by clicking the 'x' button on the infobar.
Bug: Pinned tab margin problem at many tabs
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-02-12 11:20:05+00:00
Resolved: 2022-02-24 15:09:34+00:00

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

Steps to reproduce:

1. Create many pinned tabs
2. Create many general tabs (Need to tab scroll mode)
3. Restart


Actual results:

Symptoms overlapping with background pinned tabs appear.
I think it seems that the `margin-inline-start` calculation seems to have problems.


Expected results:

The size must be calculated correctly.
Bug: some tabs don't update prefers-color-scheme with system theme change
Status: UNCONFIRMED
Priority: --
Created: 2022-02-12 12:39:33+00:00
Resolved: 2023-10-03 04:44:55+00:00

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

Steps to reproduce:

Change the OS from dark theme to light theme. This bug does not always occur; it seems to be random. It affects both Windows and macOS.


Actual results:

The contents of some tabs stay in dark mode, with `window.matchMedia("(prefers-color-scheme: dark)").matches` evaluating to `true`, while other tabs in the same window correctly switch to light mode. Refreshing a tab where this issue occurs does not fix it, but navigating to a different webpage does.


Expected results:

All tabs should apply system theme changes consistently.
Bug: System theme 89+
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-02-12 16:35:17+00:00
Resolved: 2022-03-11 15:38:09+00:00

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:97.0) Gecko/20100101 Firefox/97.0
Bug: Windows 11 issue with Firefox full-screen mode -- top of browser is truncated so you have to use hot-key to change to "restore down".
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-02-12 18:18:57+00:00
Resolved: 2022-02-13 17:48:01+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.82 Safari/537.36

Steps to reproduce:

Open firefox. 


Actual results:

Full-screen mode was default.
Could not see top part of browser at all.
Had to hit F11 on keyboard to go to non-fullscreen mode.


Expected results:

Should be able to see full view of browser in fullscreen mode.

User agent string: db7e2313f77748e28c177bac79896127
Bug: OOM | small while memory is available
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-02-13 05:09:17+00:00
Resolved: 2022-08-07 00:36:35+00:00

I got these reports from one of users. Do you have idea what causes this?

https://crash-stats.mozilla.org/report/index/3d759b2d-f818-443f-b995-561ec0220210
https://crash-stats.mozilla.org/report/index/d596b4a9-8cc4-498e-977c-f02d40220210
https://crash-stats.mozilla.org/report/index/3bcce90b-d27c-402c-b31a-e0dcc0220210
https://crash-stats.mozilla.org/report/index/6ad9dad9-0447-42da-8aeb-7009a0220210
https://crash-stats.mozilla.org/report/index/b3a89a24-af6f-473c-a754-fa0d00220210
Bug: Some pdf have some text which is outside of a page.
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-02-13 17:58:11+00:00
Resolved: 2022-03-22 08:17:43+00:00

STR:
 - Open the pdf in https://bugzilla.mozilla.org/show_bug.cgi?id=916883#c4.
 - Search for "win aisle".

There are 6 occurrences when there are only 3 in Acrobat.
Bug: WebExtensions: Content scripts sometimes load in the wrong order on restored tabs, causing errors
Status: NEW
Priority: --
Created: 2022-02-13 21:01:03+00:00
Resolved: 2022-02-28 12:11:42+00:00

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

Steps to reproduce:

1. Load the attached example addon into Firefox
2. Open https://www.example.com in a new tab
3. Close the tab you just opened
4. Restore the tab you just closed by pressing Ctrl+Shift+T
5. Look at the console


Actual results:

The content scripts are being run in the wrong order after restoring the tab, so scripts that require jQuery fail (since jQuery is not defined before they run).

Note that this was the most minimal reproducible example I was able to create. If I replace jQuery with another script the error doesn't happen.

Bug #1492772 might be somewhat related to this bug


Expected results:

The content scripts should run in the right order (from top to bottom), and no script should have failed to run.
Bug: [macOS] Opening the library produces a pile of "Attempt to override an existing message" fluent errors from browserSets.ftl and textActions.ftl
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2022-02-13 22:07:44+00:00
Resolved: 2022-11-22 21:53:08+00:00

As in summary. I haven't checked when this started, but it's been in beta for a while; I didn't get around to filing it before, so I expect 97 at least is affected; it may be yet older.
Bug: message_pump_libevent.cc:113:5: error: profiler_thread_wake was not declared in this scope; did you mean ProfilerThreadId?
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-02-14 08:31:06+00:00
Resolved: 2022-02-19 19:05:26+00:00

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

Steps to reproduce:

Solaris build fails with:
```
14:49.86 /builds/psumbera/mozilla-central-build/obj-x86_64-pc-solaris2.11/dist/include/nsIFrame.h:410:8: note: mozilla::FrameProperties::PropertyType<mozilla::SmallValueHol der<mozilla::FrameBidiData> > {aka struct mozilla::FrameBidiData} declared here
14:49.86   410 | struct FrameBidiData {
14:49.86       |        ^~~~~~~~~~~~~
14:53.53 In file included from Unified_cpp_ipc_chromium0.cpp:83:
14:53.53 /builds/psumbera/mozilla-central-build/ipc/chromium/src/base/message_pump_libevent.cc: In static member function static void base::MessagePumpLibevent::OnWakeup(in t, short int, void*):
14:53.53 /builds/psumbera/mozilla-central-build/ipc/chromium/src/base/message_pump_libevent.cc:113:5: error: profiler_thread_wake was not declared in this scope; did you mean ProfilerThreadId?
14:53.53   113 |     profiler_thread_wake();
14:53.53       |     ^~~~~~~~~~~~~~~~~~~~
14:53.53       |     ProfilerThreadId
..
```
The first bad revision is:
changeset:   607483:eaeaf7286193
parent:      607480:46048399bf0f
user:        Gabriele Svelto <gsvelto@mozilla.com>
date:        Fri Feb 11 05:31:21 2022 -0800
description:
	Bug 1748643 - Do not process MIDI runnables after shutdown r=padenot
Bug: Event listener: inconsistent capture before bubble
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-02-14 10:53:39+00:00
Resolved: 2022-02-14 11:13:01+00:00

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

Steps to reproduce:

I have visited this page (also attached):
https://webreflection.github.io/issue/dom/capture-before-bubble/

I have observed the console after clicking those buttons, as explained in the source code.


Actual results:

Chrome and Safari always trigger capture phase events **before** bubble phase, no matter if capture events are added after the bubble one.

It is stated in this 13yo issue that this is expected:
https://bugzilla.mozilla.org/show_bug.cgi?id=523376

However, Firefox is the only one that doesn't guarantee that capturing happens before bubbling, which is also the expected order for developers, as capturing happens before.


Expected results:

Every browser should log capture before bubble, or every browser should be consistent. As developer expectations are the one both Chrome and Safari provide, I believe Firefox should align in here to avoid surprises.
Bug: Whatsapp Web not isolated on container
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-02-14 14:04:24+00:00
Resolved: 2022-02-16 11:39:13+00:00

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

Steps to reproduce:

1) Open a new container tab (such as "Facebook").
2) Load https://web.whatsapp.com
3) Scan the QR code to login
4) After you are logged in to whatsapp web, close the tab
5) Open a new tab in a different container (such as "Personal")
6) Load https://web.whatsapp.com


Actual results:

You are still logged in to whatsapp, even though you are using a different container than the one you used to log in.


Expected results:

You should not be logged in to whatsapp on a different container, i.e. the QR code should appear, prompting you to log in.
Bug: Intermittent browser/base/content/test/tabMediaIndicator/browser_mediaPlayback_mute.js | Test timed out -
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2022-02-14 16:20:12+00:00
Resolved: 2022-07-26 00:12:00+00:00

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

---
```

```
Bug: Version 97.0 don't open JNLP files
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-02-14 21:15:30+00:00
Resolved: 2022-03-10 14:28:08+00:00

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

Steps to reproduce:

The last FF version ignore the option "Open with java web start" for JNLP files. 


Actual results:

The browser always shows "save file" dialog for jnlp files. Others users report the same bug.


Expected results:

JNLP files shoud be start, the previous FF version work fine
Bug: downloads not cleared on exit
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-02-14 22:49:07+00:00
Resolved: 2022-02-15 16:37:31+00:00

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

Steps to reproduce:

Downloaded multiple jpgs, exited and restarted FF.  The blue download icon remained on the toolbar with the previous session downloads listed.  This wasn't happening on earlier versions.


Actual results:

Downloaded different jpgs, exited and restarted FF.  The download icon still appeared in blue on the toolbar and it showed downloads from the previous session.


Expected results:

Upon restarting FF, the download icon should not have appeared in the toolbar until after a download was initiated.