av9ash/GitBugs huggingface dataset:
Bug: firefox quit only keep 3 windows in profile sessionstore.jsonlz4
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-08-17 03:24:52+00:00
Resolved: 2023-04-06 19:18:31+00:00

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

Steps to reproduce:

on firefox dev 104.0b9 (64-bit) and firefox esr 91.12.0esr (64-bit) if you open more than 3 windows and quit firefox without killing it only 3 are saved on quit in the profile directory sessionstore.jsonl4.

As a test case create a new profile with "firefox -no-remote -P  --safe-mode" and then quit firefox. Copy the attached restore.jsonlz4 to the firefox new session profile as sessionstore.jsonlz4 then start "firefox -no-remote -P  --safe-mode". Then click "History" > "Restore previous session" and 4 windows open.
Then quit firefox without killing it. Then start firefox anew "firefox -no-remote -P  --safe-mode" and  click "History" > "Restore previous session". Only 3 windows are restored.

If you saved the profile sessionstore-backups/recovery.jsonlz4 before quitting firefox and then quit firefox, then copy this copy of recovery.jsonlz4 to the profile sessionstore.jsonlz4 then 4 windows are restored when you restore the previous session.
This is confirmed by the fact that killing firefox and then restarting it correctly opens the 4 windows.



Actual results:

Only 3 windows data were saved and then restored on firefox quit.


Expected results:

All the 4 windows opened before I quit firefox should be saved to the profile sessionstore.jsonlz4.
Bug: Update sub-dialog dimensions now that they're based on the sub-dialog's real font size
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2022-08-17 09:38:04+00:00
Resolved: 2022-08-18 21:54:16+00:00

From https://phabricator.services.mozilla.com/D154775#5076141:
> [...]  bug 1784488 regressed font size on dialogs in about:preferences, and is now too big for a relatively small frame. Was that intentional?

I think what's happening here is that stuff like: https://searchfox.org/mozilla-central/rev/f3616b887b8627d8ad841bb1a11138ed658206c5/browser/locales/en-US/browser/preferences/colors.ftl#7-11
... now correctly uses the sub-dialog's font size, rather than the random thing we were doing before. We'll probably have to adjust these `em` values.
Bug: font size of about:certificate and about:studies regressed
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2022-08-17 10:04:47+00:00
Resolved: 2022-09-06 08:55:08+00:00

Bug 1784488 regressed the font size of about:certificate and about:studies. On about:certificate the tab titles are noticeable larger, on about:studies everything is really large now. Tested on macOS 12.5.
Bug: PDF Viewer shows no fields on Page 2 from PDF Document
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2022-08-17 11:21:01+00:00
Resolved: 2022-08-31 00:04:48+00:00

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.134 Safari/537.36

Steps to reproduce:

https://thformular.thueringen.de/thueform/cfs/eject/pdf/4300.pdf?MANDANTID=18&FORMUID=GRST-001-DE-FL


Actual results:

We are the producer of this pdf forms. The user can only fill the first page with your browser.

On Edge, Adobe, Chrome(ium) and Safari the fields on page 2 are visible and can be filled.


Expected results:

The fields on page two should be available and fillable.
Bug: Navigate to tel: links and other non-web content from Firefox Android QR code scanner using redirects
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2022-08-17 12:10:11+00:00
Resolved: 2024-05-30 17:59:44+00:00

I was reading past Firefox advisories and came across https://www.mozilla.org/en-US/security/advisories/mfsa2022-01/#CVE-2022-22749. Unfortunately, this vulnerability isn't public so I'll have to speculate what this is about. My guess is that this vulnerability is about the ability to navigate to tel: links and other external protocols in Firefox Android by scanning a malicious QR code pointing directly to the external protocol link which are all non-web content. However, I find a  way to open a tel: link directly from the QR scanner using redirects

If you scanned a QR code pointing to a external protocol such as tel:1 on Android. You will fail. I speculate that this was what https://www.mozilla.org/en-US/security/advisories/mfsa2022-01/#CVE-2022-22749 was about.

But if you scanned a QR code pointing to a site which redirects to tel:1, such as http://httpbin.org/redirect-to?url=tel:1, you will be redirected to tel:1 and open the Telephone app on Android.

REPRODUCTION STEPS
Tested on Firefox version: 103.2.0 (Latest version)

1. Scan the attached QR code on Firefox Android
Bug: Focusing a selected Firefox View tab with the keyboard in HCM does not show focus outline on top of the selected tab outline
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2022-08-17 12:54:28+00:00
Resolved: 2022-09-30 14:13:21+00:00

When Firefox View is active in the Dark OS theme (both on macOS HCM/“increase contrast” and without it), the FxView tab does not show focus outline when focused with keyboard. 

Expected: when focused with keyboard, the default FxView outline is visible
Bug: Firefox View focus order
Status: RESOLVED
Priority: P2
Resolution: DUPLICATE
Created: 2022-08-17 12:58:27+00:00
Resolved: 2022-08-24 15:55:52+00:00

The current focus order is not logical, as it jumps from the main area under Tab pickup (Get Firefox mobile > X close) to the right panel Independent voices (Try colorways button) and then back to the main area (Recently closed ^ collapse panel). 

Expected: Focus moves left-to-right top-to-bottom (for LTR languages such as English), so it would be: Get Firefox mobile > X > Recently closed ^ > Try colorways
Bug: Cannot save pages as text files even when "Text Files" is selected
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-08-17 13:21:18+00:00
Resolved: 2022-09-03 15:30:26+00:00

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

Steps to reproduce:

Steps to reproduce:

When saving a page as file, no matter what type of file is chosen among those offered (HTML, Text), the extension and the type of file produced is always html. 

Steps:

From the page you want to save:
Select menu Edit->Save Page As
Select in the "Format" dropdown "Text Files"
A file will be saved.


Actual results:

The saved file will always have the extension html (rather than txt) and the file itself is formatted as html..


Expected results:

The saved file should have the extension txt,  and the file itself is formatted as txt.
Bug: Perma newtab TEST-UNEXPECTED-FAIL sasslint | content-src/styles/_feature-callout.scss(38, 1): Space expected between blocks (empty-line-between-blocks)
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-08-17 13:37:01+00:00
Resolved: 2022-08-22 06:33:48+00:00

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

---
```
[task 2022-08-17T11:03:06.681Z] Finished in 13.659 secs / 3.081 secs @ 11:03:05 GMT+0000 (Coordinated Universal Time)
[task 2022-08-17T11:03:06.681Z] 
[task 2022-08-17T11:03:06.681Z] SUMMARY:
[task 2022-08-17T11:03:06.681Z] ✔ 2952 tests completed
[task 2022-08-17T11:03:06.681Z] 
[task 2022-08-17T11:03:06.681Z] -----karma stdout above this line---
[task 2022-08-17T11:03:06.681Z] TEST START | zipCodeCoverage
[task 2022-08-17T11:03:06.681Z] zipCodeCoverage log output:    adding: lcov.info (deflated 75%)
[task 2022-08-17T11:03:06.681Z] 
[task 2022-08-17T11:03:06.681Z] TEST START | sasslint
[task 2022-08-17T11:03:06.681Z] TEST-UNEXPECTED-FAIL sasslint | content-src/styles/_feature-callout.scss(38, 1): Space expected between blocks (empty-line-between-blocks)
[task 2022-08-17T11:03:06.681Z] {
[task 2022-08-17T11:03:06.681Z]   checkBundles: true,
[task 2022-08-17T11:03:06.681Z]   karma: true,
[task 2022-08-17T11:03:06.681Z]   zipCodeCoverage: true,
[task 2022-08-17T11:03:06.681Z]   sasslint: false
[task 2022-08-17T11:03:06.681Z] }
[task 2022-08-17T11:03:06.681Z] CODE 1
[taskcluster 2022-08-17 11:03:07.114Z] === Task Finished ===
[taskcluster 2022-08-17 11:03:07.115Z] Unsuccessful task run with exit code: 1 completed in 171.866 seconds
```
Bug: Firefox View VoiceOver screenreader - collapse control
Status: RESOLVED
Priority: P2
Resolution: WORKSFORME
Created: 2022-08-17 13:53:34+00:00
Resolved: 2022-09-08 17:56:44+00:00

The expand/collapse control of the Tab pickup is unlabeled and is announced as button. 

Expected: Tab pickup, button, expanded
Bug: Firefox View VoiceOver screenreader - collapse control - accordion
Status: RESOLVED
Priority: P2
Resolution: WORKSFORME
Created: 2022-08-17 13:57:39+00:00
Resolved: 2022-09-08 17:57:34+00:00

The expand/collapse control of the Tab pickup does not announce its state (by default and on change). 

Expected: Tab pickup, button, expanded and Tab pickup, button, collapsed (accordion design pattern and its expected behavior - https://www.w3.org/WAI/ARIA/apg/patterns/accordion/)
Bug: [Colorway Closet] Set role="presentation" on colorway illustrations
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2022-08-17 14:34:34+00:00
Resolved: 2022-08-18 21:54:20+00:00

Feedback from a11y on the new assets:
> [...] Also, I think this was noted in the a11y review but: the images should be marked as presentational to hide them from screen reader users. Right now they just come up as empty images.
Bug: Firefox View Colorway images
Status: RESOLVED
Priority: P1
Resolution: DUPLICATE
Created: 2022-08-17 14:45:34+00:00
Resolved: 2022-08-17 14:48:55+00:00

Image of the right panel has no textual alternative and is announced as Image. 

Expected: Images should either marked as decorative and not announced in read all mode (cannot be focused with a screen reader with Ctrl+Option+Arrow navigation) 

OR 

Descriptive alternative text is provided, i.e. "Hand with a pencil, prism in a shape of a pyramid, profile photo of a woman of color" or something that would help users with low vision, without vision, or with cognitive difficulties to get the same feelings as sighted users are expected to get with this graphic.
Bug: Firefox View VoiceOver screenreader - Tab selected state is not announced
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2022-08-17 14:49:45+00:00
Resolved: 2023-06-02 15:23:36+00:00

The Firefox View control on the tab bar does not announce its pressed/active state while visually it’s communicated to a user.
Bug: Firefox View - Logo and page title shouldn't be inside <nav> as there's no navigation; make logo presentational
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2022-08-17 14:55:21+00:00
Resolved: 2023-06-02 15:23:36+00:00

Firefox View includes a Fx logo but it’s not announced to a user. It could be exposed to assistive technology as one element (logo and text) as Firefox View logo
Bug: Screenshots component should respect "Always ask you where to save files"
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2022-08-17 17:21:58+00:00
Resolved: 2023-12-22 12:41:56+00:00

The component currently doesn't respect the value of "Always ask you where to save files" in settings. We should open the downloads panel if it is checked
Bug: navigator.gpu.getPreferredCanvasFormat is not a function
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-08-17 22:09:56+00:00
Resolved: 2022-08-17 22:23:53+00:00

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

Steps to reproduce:

Open "https://austin-eng.com/webgpu-samples/samples/helloTriangle".


Actual results:

navigator.gpu.getPreferredCanvasFormat is not a function


Expected results:

the getPreferredCanvasFormat should be available.
https://gpuweb.github.io/gpuweb/#gpu-interface
Bug: Firefox View - need a test to verify we can access and activate tab pickup items using the keyboard
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2022-08-17 23:14:50+00:00
Resolved: 2023-06-02 15:23:36+00:00

Items under the Tab pickup section are not able to be activated by keyboard (space/enter). Recently closed items are only able to be activated with "Enter" (just wanted to verify this was intentional)

Expected:
Items in both sections should be activated by keyboard
Bug: Firefox View disclosure buttons in HCM
Status: RESOLVED
Priority: P1
Resolution: WORKSFORME
Created: 2022-08-17 23:24:43+00:00
Resolved: 2022-09-08 17:56:06+00:00

Disclosure button icons disappear on hover with Windows HCM black active, reduce their contrast on macOS with increased contrast enabled. They should invert their styling on both platforms.
Bug: Navigating a tab to a non-syncable URL doesn't remove the old tab from the synced tabs list
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2022-08-17 23:53:55+00:00
Resolved: 2022-08-18 15:48:03+00:00

STR:
* Open a tab, "sync now", note that other devices see the tab as being opened.
* Select the "home" button, "sync now"

Expected:
* The old tab is no longer in the list of open tabs.

Actual:
* The old tab remains until the tab navigates somewhere else or some other action causes the tab list to be updated.

The problem is that the tab is now on `about:home` and [here](https://searchfox.org/mozilla-central/rev/f3616b887b8627d8ad841bb1a11138ed658206c5/services/sync/modules/engines/tabs.js#553) we ignore the notification because we know that `about:home` isn't going to be synced. However, this prevents us from syncing the new tab list which no longer includes the old tab.

I think this is relatively low impact - the updated tab list is likely to be synced "soon", so this state will be transient and short-lived.
Bug: after update to 103.02, all bookmarks were lost 10 yars or more worth!
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-08-18 02:00:52+00:00
Resolved: 2022-08-29 12:48:36+00:00

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

Steps to reproduce:

automatic Firefox update on 8/16


Actual results:

ALL bookmarks and pinned windows lost


Expected results:

should NOT HAVE been removed by update
Bug: Saved tabs are not saved but forgotten
Status: UNCONFIRMED
Priority: --
Created: 2022-08-18 08:41:00+00:00
Resolved: 2022-10-12 11:16:38+00:00

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

Steps to reproduce:

Close firefox with several tabs open (once over 50, recently less than 15), private window first, then the main FF window, then shut down computer


Actual results:

After the restart, a new session was opened and all my tabs were forgotten. This is the second time at least that this happened. It did only happen since 1 month or so. For years this was hardly a problem. Maybe this has to do with a quick but regular shutdown of the computer after FF was closed.
Win 7, FF 103


Expected results:

Show again the previous tabs of the last session (yes, the setting is enabled).
Also the option to restore the last x sessions would be helpful, maybe on the new-tab-screen.
Bug: The "os.environment.is_taskbar_pinned_private" scalar is set to "false" even if the "Pin Private Window" shortcut is pinned to the taskbar
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-08-18 13:41:46+00:00
Resolved: 2022-08-19 13:39:58+00:00

**[Notes]:**
- This issue might affect the "Pin Private Window" modal from the MR Onboarding flow for the existing users as the modal is displayed even if the "Private Window" shortcut is already pinned to the taskbar.

**[Affected versions]:**
- Firefox Nightly 105.0a1 - Build ID: 20220612185901

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

**[Prerequisites]:**
- Have the following prefs in the "about:config" page:
  - "nimbus.debug" pref set to "true".
  - "browser.promo.pin.enabled" set to "true"
- Have the "Remote Settings Devtools" add-on installed from [here](https://github.com/mozilla-extensions/remote-settings-devtools/releases).

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Click the "Remote Settings Devtools" tollbar button from the right part of the toolbar.
3. Switch the environment to "Stage" and restart the browser.
4. Navigate to the "about:studies?optin_slug=cmuresandesktop-nimbus-exploration-080522&optin_branch=treatment-a&optin_collection=nimbus-preview" URL.
5. Open a "Private Window" and click the "Pin to taskbar" button.
6. Restart the browser and navigate to the "about:telemetry" page.
7. Search for the "os.environment.is_taskbar_pinned_private" scalar and observe the value.

**[Expected result]:**
- The value of the "os.environment.is_taskbar_pinned_private" scalar is set to "true".

**[Actual result]:**
- The value of the "os.environment.is_taskbar_pinned_private" scalar is set to "false".

**[Regression window]:**
- Considering that this issue is not reproducible on Firefox Beta 104 using the Mozregression tool I have managed to find the following regression window:
Last good revision: 113593df627273c8e66f58bf735c38ad7e937f38
First bad revision: 23d27ffb8a811e38a46621aa06044ff3acaac2b9
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=113593df627273c8e66f58bf735c38ad7e937f38&tochange=23d27ffb8a811e38a46621aa06044ff3acaac2b9

From the pushlog it seems that Bug 1761291 might have caused this regression.

@Ben could you please take a look over this?

**[Additional Notes]:**
- The "os.environment.is_taskbar_pinned" is correctly recorded for the normal browsing shortcut.
- Attached a screen recording of the issue.
Bug: Port bug 1722314 (JNLP) to 102 ESR.
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2022-08-18 14:37:21+00:00
Resolved: 2022-08-22 14:18:41+00:00

I've been trying to get JNLP launching via policy in bug 1779018, but we're running out of time and we discovered another issue that requires deeper changes.

So before we force 91 to 102 ESR, I'm going to put the custom JNLP code back.
Bug: [Colorway-Closet] Contents of Colorways modal move around at small responsive size
Status: RESOLVED
Priority: P2
Resolution: WORKSFORME
Created: 2022-08-18 15:14:34+00:00
Resolved: 2022-09-09 09:08:13+00:00

Affected version: 105.0a1 (2022-08-16)

When user shrinks browser, contents of the modal jump around when switching between colorways. Please see attached video for reference
Bug: Right clicking disabled on Colorways Modal
Status: RESOLVED
Priority: P2
Resolution: WONTFIX
Created: 2022-08-18 15:17:43+00:00
Resolved: 2022-08-19 16:03:51+00:00

Affected version: 105.0a1 (2022-08-16)

When user right clicks over Colorways modal, nothing happens
Bug: The follow-on searches generating ads have telemetry pings that are listed with unknown SAP
Status: NEW
Priority: P2
Created: 2022-08-18 15:33:24+00:00
Resolved: 2025-01-30 17:24:47+00:00

**Found in**
* Fx105.0a1

**Affected versions**
* Fx 105.0a1
* Fx 104.0 RC
* Fx 102.2 ESR

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

**Preconditions**
Have the browser.search.region set to US.

**Steps to reproduce**
1. Launch Firefox.
2. Type in address bar 'iphone'.
3. In the resulted search page, modify your search phrase by adding ' 13'. (doesn't really matter what you add as long as the resulting search contains adds).
4. Click on a displayed add.
5. Verify the 'withads' and 'adclicks' telemetry pings in the telemetry raw json.

**Expected result**
* The SAP for the withads and adclicks telemetry pings are correctly recorded.

**Actual result**
* The SAP for both withads and adclicks telemetry pings are recorded as unknown.
```
            "browser.search.withads.unknown": {
              "google:tagged-follow-on": 1
```
```
            "browser.search.adclicks.unknown": {
              "google:tagged-follow-on": 1
```

**Regression range**
* This is not a regression. Have managed to reproduce it all the way back to the introduction of the new SAP telemetry pings for ads.

**Additional notes**
* Same issue occurs for Bing.
* For DDG, even though we don't have follow-on searches, the SAP on the edited search is listed as unknown.
```
            "browser.search.withads.unknown": {
              "duckduckgo:tagged": 1
```
Bug: Remove extra space from below Tab Pickup when it is collapsed
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2022-08-18 17:32:22+00:00
Resolved: 2022-09-22 12:57:22+00:00

When you collapse the Tab Pickup section on Fx-View, there is too much vertical space between it and the Recently Closed section below.
Bug: firefox quit in some cases restores only one window and the others in the session are as closed windows
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-08-18 18:39:57+00:00
Resolved: 2023-09-07 10:31:31+00:00

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

Steps to reproduce:

on firefox dev 104.0b9 (64-bit) if cop the attached recovery.jsonlz4 of my test session to a profile directory as sessionstore.jsonl4 ( ie more than 4 windows, one with 3 tabs) then start "firefox --no-remote -P <profile> --safe-mode", then quit firefox without killing it, then restart firefox, only 1 window is restored. The others are saved as closed windows. I have to go to "History" > "Recently closed windows" and open them back one by one.


Actual results:

Only one window is restored (always the one with the tabs it seems).


Expected results:

The four windows are restored even on the second firefox startup.
Bug: close button on left
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-08-18 19:42:03+00:00
Resolved: 2022-08-18 19:51:24+00:00

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

Steps to reproduce:

OPenedd the browser and created tabs.


Actual results:

Tabs opened with close button on right.


Expected results:

On a Mac, the close buttons on tabs should be on the left.
This is a Mac standard.
It has been that way from the beginning.
Bug: stop snoozing (especially file URI) tabs
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-08-19 02:35:39+00:00
Resolved: 2022-08-19 02:59:30+00:00

Months ago I set browser.tabs.unloadOnLowMemory false, but you won't stop snoozing/reloading tabs (I have 64GB RAM with sufficient left) especially file URIs ('file:///home/user/file').  There's zero reason a user's own static file tabs should ever be snoozed/realoaded.
Bug: Slow rendering and opening of certain PDF types
Status: RESOLVED
Priority: P3
Resolution: WORKSFORME
Created: 2022-08-19 06:50:58+00:00
Resolved: 2024-05-02 16:48:19+00:00

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

Steps to reproduce:

I have opened following PDF in Firefox 102:
https://porteus-kiosk.org/public/files/slow_rendering.pdf


Actual results:

It takes over 5 seconds to render and open the PDF in Firefox 102 and 103 on my PC.


Expected results:

Firefox 101 and earlier opes this particular PDF in about 1 second.
Regression must have happened in development between Firefox 101 and 102.

I have confirmed the issue under the Linux and Windows systems.

Other PDF types (containing e.g. text) are not affected. 
I guess the problem is related to rendering of many lines which are included in this particular PDF type.

Please let me know in case I could help with resolving the problem (additional testing, etc).
Bug: new tab not working after crashing
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-08-19 06:54:00+00:00
Resolved: 2023-06-05 17:04:08+00:00

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

Steps to reproduce:

I clicked a link and opened a new tab and fire fox crashed and sent no crash report.  
Notes: I had a bunch of tabs open.  And I am on Fedora.


Actual results:

The new tab no longer shows the shortcuts.


Expected results:

When ever opening the new tabs the shortcuts should have worked.

I also changed themes and that did not fix the problem