av9ash/GitBugs huggingface dataset:
Bug: The Firefox browser is not set as PDF handler after clicking the “OK” button from the infobar message on Windows 7 and 8.1 oses
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2023-03-13 12:34:51+00:00
Resolved: 2023-03-13 16:36:37+00:00

**[Affected versions]:**
- Firefox Nightly 112.0a1 (Build ID: 20230312211644)

**[Affected Platforms]:**
- Windows 7 x64
- Windows 8.1 x64

**[Prerequisites]:**
- Have the latest Firefox Nightly 112.0a1 build installed and opened.
- Have the “browser.newtabpage.activity-stream.asrouter.devtoolsEnabled” pref set to true in the “about:config” page.
- Have a PDF file saved on your computer.


**[Steps to reproduce]:**
1. Navigate to the “about:messagepreview?json=eyJpZCI6IlNFVF9ERUZBVUxUX1BERl9IQU5ETEVSX1FBIiwidGFyZ2V0aW5nIjoidHJ1ZSIsImdyb3VwcyI6W10sInRyaWdnZXIiOnt9LCJ0ZW1wbGF0ZSI6ImluZm9iYXIiLCJjb250ZW50Ijp7InR5cGUiOiJ0YWIiLCJ0ZXh0IjoiU2V0IEZpcmVmb3ggYXMgeW91ciBkZWZhdWx0IFBERiBIYW5kbGVyIiwiYnV0dG9ucyI6W3sibGFiZWwiOiJPSyIsImFjdGlvbiI6eyJ0eXBlIjoiU0VUX0RFRkFVTFRfUERGX0hBTkRMRVIifX1dfX0=” URL.
2. Click the “OK” button from infobar. 
3. Close Firefox.
4. Verify the default OS PDF handler via Start → Default Apps → Choose default apps by filetype.
5. Open the PDF file from prerequisites.
6. Open the Firefox browser.
7. Open a new tab and click the “Expand tools” button from the top right corner of the page.
8. Evaluate the “isDefaultHandler.pdf” targeting parameter on the “Targeting” section.

**[Expected result]:**
Step 4: The Firefox Nightly is set as a PDF handler.
Step 5: The PDF file opens through the Firefox Nightly browser.
Step 8: The “isDefaultHandler.pdf” targeting parameter is evaluated as true.

**[Actual result]:**
Step 4: The Firefox Nightly is not set as PDF handler.
Step 5: The PDF file is not opened through the Firefox Nightly browser.
Step 8: The “isDefaultHandler.pdf” targeting parameter is evaluated as false.

**[Notes]:**
- This issue is not reproducible when manually setting the Firefox Browser as PDF handler through the OS settings.
- We’ve noticed a schema validation error in the Browser Console when the infobar shows on all Windows versions. The error can be found here: [link](https://drive.google.com/file/d/1jwmjy7pwbGjyIL0fRz16EzHIQd9EJeN0/view?usp=share_link).
- Attached is a screen recording of the issue.
Bug: The link of the third Sponsored tile is displayed first in the Address Bar results drop down
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-03-13 12:58:53+00:00
Resolved: 2023-03-24 13:50:20+00:00

**[Affected versions]:**
- Firefox Nightly 112.0a1 - Build ID: 20230309093044

**[Affected Platforms]:**
- Windows 10 x64
- macOS 12.4
- Linux Ubuntu 20.04 x64

**[Prerequisites]:**
- Have a VPN client connected to a US server (for users located outside US).
- Have the `nimbus.debug` pref set to `true`.

**[Steps to reproduce]:**
1. Open the browser from the prerequisites.
2. Copy and paste the following link in a new tab: 
`about:studies?optin_slug=showing-3rd-sponsored-tile-on-the-newtab-page&optin_branch=treatment&optin_collection=nimbus-preview`
3. Open a new tab.
4. Click inside the Address Bar.
5. Observe the Top Sites from the drop down.

**[Expected result]:**
- Only the default Top Sites are displayed.

**[Actual result]:**
- The link of the third Sponsored tile is displayed first in the results drop down.

**[Notes]:**
- Attached is a screenshot of the issue.
Bug: 20.78% welcome fcp (OSX) regression on Fri March 3 2023
Status: RESOLVED
Priority: P1
Resolution: WONTFIX
Created: 2023-03-13 13:43:50+00:00
Resolved: 2023-03-16 20:20:24+00:00

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

### Regressions:

| **Ratio** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)** |  **Performance Profiles** | 
|--|--|--|--|--|--| 
| [21%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,3932983,1,13)  | [welcome](https://firefox-source-docs.mozilla.org/testing/perfdocs/raptor.html#welcome-c) fcp | macosx1015-64-shippable-qr | cold fission webrender | [80.52](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/G7HjXEhLTkynZbXVtGwv5w/runs/0/artifacts/public/test_info/browsertime-results.tgz) -> [97.25](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/f5Mhcu_6RhW5AZbXdP82DQ/runs/0/artifacts/public/test_info/browsertime-results.tgz) | [Before](https://profiler.firefox.com/from-url/https%3A%2F%2Ffirefox-ci-tc.services.mozilla.com%2Fapi%2Fqueue%2Fv1%2Ftask%2FG7HjXEhLTkynZbXVtGwv5w%2Fruns%2F0%2Fartifacts%2Fpublic%2Ftest_info%2Fprofile_welcome.zip)/[After](https://profiler.firefox.com/from-url/https%3A%2F%2Ffirefox-ci-tc.services.mozilla.com%2Fapi%2Fqueue%2Fv1%2Ftask%2Ff5Mhcu_6RhW5AZbXdP82DQ%2Fruns%2F0%2Fartifacts%2Fpublic%2Ftest_info%2Fprofile_welcome.zip) |


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

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

For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
Bug: Perma toolkit/components/translations/tests/browser/browser_about_translations.js | Uncaught exception in test bound test_about_translations_language_identification - when Gecko 112 merges to Beta on 2023-03-13
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2023-03-13 15:05:21+00:00
Resolved: 2023-05-22 21:19:09+00:00

[Tracking Requested - why for this release]:

[Central-as-Beta simulation](https://treeherder.mozilla.org/jobs?repo=try&selectedTaskRun=cmKgmZm_SU2a1vXXN_M19A.0&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&revision=a137b11dc8dd38ba3b11bc6fb6c84b26e7aad2ee)

[How to run these simulations](https://wiki.mozilla.org/Sheriffing/How_To/Beta_simulations#TRUNK_AS_LATE_BETA)

[Failure log](https://treeherder.mozilla.org/logviewer?job_id=408700740&repo=try&lineNumber=6053)

Log snippet:
```
[task 2023-03-13T14:12:34.982Z] 14:12:34     INFO - TEST-PASS | toolkit/components/translations/tests/browser/browser_about_translations.js | The fromSelect starting value is "detect" - "detect" == "detect" - 
[task 2023-03-13T14:12:34.982Z] 14:12:34     INFO - Console message: [JavaScript Error: "Error: An error occured in the AboutTranslations actor."]
[task 2023-03-13T14:12:34.983Z] 14:12:34     INFO - Console message: [JavaScript Error: "Error: An error occured in the AboutTranslations actor."]
[task 2023-03-13T14:12:34.983Z] 14:12:34     INFO - Buffered messages finished
[task 2023-03-13T14:12:34.984Z] 14:12:34     INFO - TEST-UNEXPECTED-FAIL | toolkit/components/translations/tests/browser/browser_about_translations.js | Uncaught exception in test bound test_about_translations_language_identification - Waiting for placeholder text to be visible." - timed out after 50 tries.
[task 2023-03-13T14:12:34.984Z] 14:12:34     INFO - Leaving test bound test_about_translations_language_identification
[task 2023-03-13T14:12:34.985Z] 14:12:34     INFO - GECKO(20567) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2023-03-13T14:12:34.985Z] 14:12:34     INFO - GECKO(20567) | MEMORY STAT heapAllocated not supported in this build configuration.
[task 2023-03-13T14:12:34.986Z] 14:12:34     INFO - GECKO(20567) | MEMORY STAT | vsize 130551339MB | residentFast 1178MB
[task 2023-03-13T14:12:34.986Z] 14:12:34     INFO - TEST-OK | toolkit/components/translations/tests/browser/browser_about_translations.js | took 14292ms
[task 2023-03-13T14:12:34.987Z] 14:12:34     INFO - Not taking screenshot here: see the one that was previously logged
[task 2023-03-13T14:12:34.987Z] 14:12:34     INFO - TEST-UNEXPECTED-FAIL | toolkit/components/translations/tests/browser/browser_about_translations.js | Found an unexpected tab at the end of test run: about:translations - 
[task 2023-03-13T14:12:34.988Z] 14:12:34     INFO - checking window state
```
Bug: Dialog prompt extremely long
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-03-13 15:15:41+00:00
Resolved: 2023-03-13 15:54:47+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0
Bug: [Fx View] Switch recently closed items back from role="link" to role="button"
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-03-13 15:30:01+00:00
Resolved: 2023-03-15 06:43:19+00:00

With the addition of the Dismiss button for Recently closed tabs in Firefox View (bug 1787945), we switched from using role="button" to role="link" for the actionable area of the list item. In a recent update to make recently closed tabs be template driven (bug 1801204), we switched from a span with role="link" to an actual anchor tag.

There was a lot of previous discussion on why we should be using a role of button here rather than link that can be found [here](https://docs.google.com/document/d/1iBKT534dHrq7b7NUkdHs9Cno6i0V9KQ--8YxbWckc2A/edit#), but essentially this is because they don’t quite behave like links (if you click on a closed tab in the list, it will open into a new tab and will be removed from the list). We also didn’t want to have to introduce other link-based behavior.

Expected behavior:
Recently closed tabs in Fx View should have a role of "button" and should not have typical link options when right clicked.

Actual behavior:
Recently closed tabs in Fx View are currently treated as links in Nightly and have alternate link opening options when right clicked. When selecting those alternate link opening options from the context menu, the item is not removed from the list.
Bug: middle click on previous/next buttons should open tab in the background.
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2023-03-13 17:13:31+00:00
Resolved: 2023-03-29 11:29:20+00:00

Steps to reproduce:

I middle click (or ctrl+click) on the previous ← (or next →) button.





Actual results:

The page is opened in a new tab in the foreground.


Expected results:

The page should be opened in a new tab in the background. 

The current tab should keep the focus, as it does when middle-clicking on a link.
Bug: Moving Close button left stopped working
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2023-03-13 17:14:16+00:00
Resolved: 2023-03-14 17:13:32+00:00

Moving the tab close button to the left using a userChrome.css file was working perfectly, but no longer works in 112.0a1 (2023-03-12) as per this: https://support.mozilla.org/en-US/questions/1157451
Bug: Console errors when trending searches enabled.
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-03-13 17:28:23+00:00
Resolved: 2024-05-13 15:32:57+00:00

as commented at https://bugzilla.mozilla.org/show_bug.cgi?id=1820043#c4, they dont eem to break anything but I have also seen them.
Bug: Check whether the view is opening when recording telemetry
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-03-13 23:55:49+00:00
Resolved: 2023-03-23 10:46:31+00:00

This is a follow-up of bug 1817208.
In this bug, we will fix https://bugzilla.mozilla.org/show_bug.cgi?id=1817208#c2 case.

(In reply to Marco Bonardo [:mak] from comment #2)
> Another case is typing a search, pressing ESC to close the results panel, then confirm the search with Enter, should return `input_field` as selected_result, instead it returns `unknown`.
> Also why is selected_result not empty if there's no selected result? unknown should only be used when there is a selected result but we can't recognize it, maybe there's a catch-all setting to unknown even if there isn't a selected result.
Bug: JavaScript error: resource://services-settings/Utils.jsm, line 237: TypeError: NetworkError: Network request failed
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-03-14 07:51:41+00:00
Resolved: 2023-11-06 10:13:15+00:00

This failure can be seen in various test jobs as driven by Marionette. It always happens during shutdown of Firefox and it looks like that some resource is fetched even with the application shutting down.

https://treeherder.mozilla.org/logviewer?job_id=408692341&repo=try&lineNumber=122036-122037

```
[task 2023-03-13T14:09:43.770Z] 14:09:43     INFO - PID 6160 | console.error: (new TypeError("NetworkError: Network request failed", "resource://services-settings/Utils.jsm", 237))
[task 2023-03-13T14:09:43.786Z] 14:09:43     INFO - PID 6160 | JavaScript error: resource://services-settings/Utils.jsm, line 237: TypeError: NetworkError: Network request failed
```
Bug: [Experiment] The “Device migration” screen is wrongly shown before the “Choose Your Language” one
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2023-03-14 13:00:35+00:00
Resolved: 2023-03-15 11:19:41+00:00

**[Affected versions]:**
- Firefox Release 111.0 (Build ID: 20230309232128)

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

**[Prerequisites]:**
- Have the Firefox Release 111 build installed and opened.
- Have set a different OS language than Firefox.
- Have the “nimbus.debug” pref set to true in the “about:config” page.


**[Steps to reproduce]:**
1. Force enroll in the Treatment B branch of the experiment using the following link: about:studies?optin_slug=device-migration-new-user-onboarding-pt-2&optin_branch=treatment-b&optin_collection=nimbus-preview
2. navigate to the "about:welcome" page and click the “Skip this step” button from the first screen.
3. Observe what happens.

**[Expected result]:**
- The “Choose Your Language” screen is displayed.

**[Actual result]:**
- The “Device Migration” screen is displayed.

**[Notes]:**
- Based on [Figma](https://www.figma.com/file/c83OEio9DhCQKuabx2tIEl/NUO-Experiments-2023?node-id=2%3A376&t=UrSiCJKtdKPdsyMm-0), the “Device Migration” screen should be displayed after the “Choose Your Language” one.
- This issue is also reproducible in the Treatment A branch of the experiment.
- It is also reproducible when naturally enrolling in the experiment.
- Attached is a screen recording of the issue.
Bug: Cannot close last tab of window
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2023-03-14 13:03:55+00:00
Resolved: 2023-05-26 12:38:24+00:00

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

Steps to reproduce:

In a window with only one open tab, I try to close the tab, by clicking on the × symbol, or by selecting to close the tab in the context menu of the tab title, or by entering Ctrl+W.


Actual results:

No effect


Expected results:

The window closes
Bug: `DOMException: Could not parse path (null): NS_ERROR_FILE_UNRECOGNIZED_PATH` errors in the Browser console when opening the Import Wizard window
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2023-03-14 14:01:21+00:00
Resolved: 2023-05-04 13:20:11+00:00

**Found in**
* 113.0a1 (20230314010803)


**Affected versions**
* 113.0a1 (20230314010803)
* 112.0b1




**Tested platforms**
* Affected platforms: Ubuntu 20.04, Windows 10x64, macOS 12
* Unaffected platforms: none




**Steps to reproduce**
1. Open Firefox > App Menu > History > Manage History.
2. Click on Import data and Backpup > Import Data From Another Browser.
3. Observe the browser console.


**Expected result**
* No errors are displayed.

**Actual result**
* Multiple `DOMException: Could not parse path (null): NS_ERROR_FILE_UNRECOGNIZED_PATH` errors.

**Regression range**
*  Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=604ac36df40777fb5c5bd4309038955b7c672b72&tochange=45df0c21ab3161cd3b6eb6adbb2b54ef244ec65c 



**Additional notes**
* Attached a screenshot.
* I am not aware if any functionality is affected. The import works as expected.
Bug: Confirming the current URL (to reload it) reports selected_result as unknown
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2023-03-14 14:14:21+00:00
Resolved: 2023-03-24 11:07:29+00:00

I've noticed a lot of selected_result = unknown cases in the data, where most of the times results are top sites.
This is compatible with the user focusing the urlbar and confirming the current url to reload the page.
I think we should use input_field in this case.
Bug: URL bar dropdown intervention card divider has rounded ends
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-03-14 14:18:58+00:00
Resolved: 2023-03-17 09:24:47+00:00

**Found in**
* 112.0b1 (2023-03-13)

**Affected versions**
* 112.0b1 (2023-03-13)

**Tested platforms**

* macOS 12
* Ubuntu 22
* Windows 10.64

**Affected platforms**

* macOS 12
* Ubuntu 22
* Windows 10.64

**Steps to reproduce**

1. Open Firefox and focus the Address Bar.
2. Type "refresh firefox" (or anything else which triggers the intervention card) in the Address Bar.
3. Observe the "Intervention Card".

**Expected result**

* The intervention card is displayed with its divider ends straight.


**Actual result**

* The intervention card is displayed with its divider ends rounded.



**Regression range**

* First bad: 95efc81f5d0da6252772c8a344388de3df68001e

* Last good: 6b9c280f186bdf9338b45df9047465b80008c33d

* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d26d38af0d2a11c2c469d614f38a291f36b5542b&tochange=95efc81f5d0da6252772c8a344388de3df68001e

* Potentially regressed by:
Bug 1801297

**Additional notes**

* In Private browsing with "Light" theme enabled, the bottom divider line is not visible and straight.
Bug: The Sponsored tile via Pocket disappear after dismissing the Amazon Sponsored tile
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2023-03-14 14:37:27+00:00
Resolved: 2023-03-24 13:54:38+00:00

**[Affected Versions]:**
- Firefox Nightly 113.0a1 (Build ID: 20230314094139)
- Firefox Beta 112.0b1 (Build ID: 20230313211718)

**[Affected Platforms]:**
- Windows 10 x64;
- Mac OS 12.4;
- Linux Mint 20;

**[Prerequisites]:**
- Have a new Firefox profile.
- Have a VPN client connected to a US server (for users located outside US).
- Have the nimbus.debug pref set to true.

**[Steps to reproduce]:**
1. Open the browser from the prerequisites.
2. Copy and paste the following link in a new tab: [Link](about:studies?optin_slug=showing-3rd-sponsored-tile-on-the-newtab-page&optin_branch=treatment&optin_collection=nimbus-preview)
4. Open a new tab.
5. Dismiss the Amazon Sponsored Tile from the first position.
6. Observe the Sponsored tile via Pocket.

**[Expected result]:**
- The Sponsored tile via Pocket is correctly displayed in the third position.

**[Actual result]:**
- The Sponsored tile via Pocket disappear.

**[Notes]:**
- The Sponsored tile via Pocket re-appears after a browser restart.
- Attached is a recording of the issue.
Bug: The forth non-sponsored tile cannot be dismissed if it’s the last remaining one
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2023-03-14 15:42:19+00:00
Resolved: 2023-03-29 19:58:14+00:00

**[Affected versions]:**
- Firefox Nightly 113.0a1 - Build ID: 20230314094139
- Firefox Beta 112.0b1 - Build ID: 20230313211718

**[Affected Platforms]:**
- Windows 10 x64
- macOS 12.4
- Linux Ubuntu 20.04 x64

**[Prerequisites]:**
- Have a VPN client connected to an US server (for people located outside US).
- Have the `nimbus.debug` pref set to `true`.

**[Steps to reproduce]:**
1. Open the browser from the prerequisites.
2. Copy and paste the following link in a new tab: 
`about:studies?optin_slug=showing-3rd-sponsored-tile-on-the-newtab-page&optin_branch=treatment&optin_collection=nimbus-preview`
3. Open a new tab.
4. Dismiss all the non-sponsored tiles and observe what happens next.

**[Expected result]:**
- All the non-sponsored tiles are dismissed and no longer displayed.

**[Actual result]:**
- The last non-sponsored tile which took the forth spot cannot be dismissed.

**[Notes]:**
- The non-sponsored tile gets dismissed when only dismissing a sponsored tile.
- [Here](https://drive.google.com/file/d/1A7TpMjd4jCDhIeb9FnsTmQOM5nKQgg9K/view?usp=sharing) is a screen recording of the issue.
Bug: Weird side bar appears and transitions away on startup randomly
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2023-03-15 02:20:21+00:00
Resolved: 2023-06-29 07:47:04+00:00

Steps to reproduce:

Every 10th time or so when I start firefox up, a weird side bar to the right appears and then transitions away. It's so random I can't exactly video record it, but I have noticed it a couple dozen times so far in the past 2 years.

It just did it today on a laptop that is synced to my firefox account that I haven't used in a while.  Maybe that is what triggers it?

Running 107.0 here.
Bug: firefox procedure entry point _CxxFrameHandler4 could not be located in the dynamic link library msvcp140.dll failed to load
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2023-03-15 04:15:31+00:00
Resolved: 2023-03-21 16:11:53+00:00

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

Steps to reproduce:

Re-installed a freshly downloaded "Firefox Installer.exe", copied it to laptop, then ran it.
I did this after uninstalling Mozilla Firefox from control panel and erasing the Firefox folder in "Program Files".
The error re-appeared.


Actual results:

The error was somewhat confusing causing me to question whether it was wrong information in a ".inf" file or was it the .dll missing or was it needing to be registered.
I opened a command prompt moved into the Firefox folder and tried to register the .dll with regsvr32.exe. It returned an error the .dll could not be located. I ran it again to be certain.
With the command still open, I right clicked the msvcp140.dll and copied it into the Windows\System32 Folder, when asked to over write the existing file, I chose Yes. At first it showed the file was open by another program. I closed the error report popup message and tried again. This time it copied successfully. I clicked the quick launch icon in the taskbar, a Firefox browser window opened with a warning that I could corrupt the information in "user profiles"with an older version of Firefox and asked f I wished to create a new profile. I chose yes. A new tab opened up and showed a link for "more help" at a Mozilla URL, I clicked the link and was happy to see that the browser worked as it should.
It reverted to
File Version 110.0.0.1.8458
Product version 110.0.1
and worked again
After filling out this report, when I went to click "Help about" a pop up telling me I needed to restart for the update to finish. Fortunately the folder was still open and right click, the details on the Firefox.exe icon I found the replacement version.
After the update it is now File Version 110.0.0.1.8468.


Expected results:

 The problem prior to the fix was no link would be followed, it just stayed put. I could not open "about:config" or addon's or any other normal navigation.
This was after clearing DNS with IP Config, checking Windows Defender Firewall permissions, both inbound and outbound. Nothing was preventing Firefox's ability to "Run". I checked Services, Internet protocols, observed activities in Task Manager, both processes and performance, verified Avira was not blocking anything.
 Nothing wrong. No new programs added or uninstalled, it just stopped working. It transitioned perfectly from Windows 10 to Windows 11 and had worked for several months, then it just stopped.
So, I thought I would put this up in case anyone else runs into the problem of not being able to go anywhere. It's like the car starts up, you drop it in gear but you don't go anywhere, as if your tires are glued to the pavement!!!😄
Don