av9ash/GitBugs huggingface dataset:
Bug: The “Tab Pickup” callout message from the “Continuous Onboarding” tour is not displayed on the “Firefox View” page unless the page is refreshed
Status: RESOLVED
Priority: P2
Resolution: WONTFIX
Created: 2022-12-14 16:58:39+00:00
Resolved: 2023-01-09 14:30:54+00:00

**[Affected versions]:**
- Firefox Nightly 110.0a1 - Build ID: 20221214033416
- Firefox Beta 109.0b2 - Build ID: 20221213185929
- Firefox Release 108.0 - Build ID: 20221208122842

**[Affected Platforms]:**
- Windows 10x64
- macOS 12.6
- Linux Mint 20.2x64

**[Prerequisites]:**
- Have a new Firefox profile created and opened.

**[Steps to reproduce]:**
1. Navigate to the "Firefox view" page.
2. Click the "See how it works" button from the “Welcome Spotlight”.
3. Click the "Next" button from the "Hop between devices with tab pickup" callout message.
4. Click the "Next" button from the "Get back your closed tabs in a snap" callout message.
5. Click the "Got it" button from the "Add a splash of color" callout message.
6. Close the browser and change the system time to 1 day in the future.
7. Reopen the browser with the same profile and navigate to the “Firefox View” page.
8. Switch to another opened tab and click again the "Firefox View" icon.
9. Observe the behavior.

**[Expected result]:**
 - The “Tab Pickup” callout message from the “Continuous Onboarding” tour is successfully displayed on the “Firefox View” page.

**[Actual result]:**
- The “Tab Pickup” callout message from the “Continuous Onboarding” tour is NOT displayed on the “Firefox View” page.

**[Notes]:**
- I managed to trigger the “Tab Pickup” callout message only by refreshing the “Firefox View” page.
- Attaching [here](https://drive.google.com/file/d/1zCRD8E2vlN26K982v5Y1YAN-1-n85eGj/view?usp=sharing) a screen recording of the issue.
Bug: WebMIDI requestMIDIAccess throws an exception immediately if a user has previously chosen "Never allow"
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-12-14 18:40:04+00:00
Resolved: 2022-12-14 18:59:56+00:00

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

Steps to reproduce:

Go to a site that uses WebMIDI and wait for the site permission addon prompt.  Choose "Never allow."  Reload the page.


Actual results:

Console output shows that on the second time loading the page, requestMIDIAccess throws an exception within 500ms.  The exception is "DOMException: WebMIDI requires a site permission add-on to activate."


Expected results:

requestMIDIAccess should not immediately throw the exception in order to mitigate fingerprinting attempts.  It should have a delay similar to 3-13 second random delay that happens if no MIDI devices are detected after calling requestMIDIAccess.
Bug: Screenshot Quick Action should be enabled on about: pages when screenshots component is enabled
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-12-14 21:34:40+00:00
Resolved: 2023-02-16 09:09:15+00:00

The new screenshots component is able to screenshot about: pages and Quick Actions should reflect that. There is an existing function [shouldScreenshotsButtonBeDisabled](https://searchfox.org/mozilla-central/rev/17aeb39742eba71e0936ae44a51a54197100166d/browser/base/content/browser.js#705-715) we can use to set the screenshot Quick Action enabled state.
Bug: Intermittent TV browser/components/customizableui/test/browser_widget_animation.js | Uncaught exception in test - InvalidStateError: XULPopupElement.activateItem: Menu is closed
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2022-12-15 07:02:17+00:00
Resolved: 2023-01-10 17:05:46+00:00

**Filed by:** csabou [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=399706641&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Pf37s1HNR9GFVt1LHHXrUQ/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Pf37s1HNR9GFVt1LHHXrUQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---
```
[task 2022-12-15T05:07:22.842Z] 05:07:22     INFO - TEST-START | browser/components/customizableui/test/browser_widget_animation.js
[task 2022-12-15T05:07:23.082Z] 05:07:23     INFO - TEST-INFO | started process screentopng
[task 2022-12-15T05:07:23.236Z] 05:07:23     INFO - TEST-INFO | screentopng: exit 0
[task 2022-12-15T05:07:23.236Z] 05:07:23     INFO - Buffered messages logged at 05:07:22
[task 2022-12-15T05:07:23.236Z] 05:07:23     INFO - Entering test bound 
[task 2022-12-15T05:07:23.236Z] 05:07:23     INFO - Buffered messages finished
[task 2022-12-15T05:07:23.236Z] 05:07:23     INFO - TEST-UNEXPECTED-FAIL | browser/components/customizableui/test/browser_widget_animation.js | Uncaught exception in test - InvalidStateError: XULPopupElement.activateItem: Menu is closed
[task 2022-12-15T05:07:23.237Z] 05:07:23     INFO - Stack trace:
[task 2022-12-15T05:07:23.237Z] 05:07:23     INFO - @chrome://mochitests/content/browser/browser/components/customizableui/test/browser_widget_animation.js:73:15
[task 2022-12-15T05:07:23.238Z] 05:07:23     INFO - Leaving test bound 
[task 2022-12-15T05:07:23.804Z] 05:07:23     INFO - GECKO(9394) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2022-12-15T05:07:23.806Z] 05:07:23     INFO - GECKO(9394) | MEMORY STAT | vsize 11652MB | residentFast 492MB | heapAllocated 253MB
[task 2022-12-15T05:07:23.810Z] 05:07:23     INFO - TEST-OK | browser/components/customizableui/test/browser_widget_animation.js | took 967ms
[task 2022-12-15T05:07:23.889Z] 05:07:23     INFO - checking window state
[task 2022-12-15T05:07:23.908Z] 05:07:23     INFO - GECKO(9394) | Completed ShutdownLeaks collections in process 9394
[task 2022-12-15T05:07:23.909Z] 05:07:23     INFO - TEST-START | Shutdown
```
Bug: start parameter in ol elements are ignored
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-12-15 10:00:41+00:00
Resolved: 2022-12-15 10:21:48+00:00

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

Steps to reproduce:

The start parameter of the Ordered List element is ignored.

If you add start="5" to the sample of the page:
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ol

<ol start"5">
  <li>Mix flour, baking powder, sugar, and salt.</li>
  <li>In another bowl, mix eggs, milk, and oil.</li>
  <li>Stir both mixtures together.</li>
  <li>Fill muffin tray 3/4 full.</li>
  <li>Bake for 20 minutes.</li>
</ol>


Actual results:

The numbering still start at 1:

    1. Mix flour, baking powder, sugar, and salt.
    2. In another bowl, mix eggs, milk, and oil.
    3. Stir both mixtures together.
    4. Fill muffin tray 3/4 full.
    5. Bake for 20 minutes.



Expected results:

The numbering must start at the value indicated in the start parameter:

    5. Mix flour, baking powder, sugar, and salt.
    6. In another bowl, mix eggs, milk, and oil.
    7. Stir both mixtures together.
    8. Fill muffin tray 3/4 full.
    9. Bake for 20 minutes.
Bug: Translation through Google does not work on Firefox ESR
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-12-15 11:28:44+00:00
Resolved: 2023-01-05 03:05:41+00:00

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

Steps to reproduce:

I wanted to have pages translated in Google Translate, which is also embedded in HomePages.



Actual results:

This does not work with the ESR version!


Expected results:

About the URL
https://translate.google.com/?hl=de
should have been translated
Bug: Default search engine may be reset when upgrading to 108 if profile was previously copied
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-12-15 12:05:23+00:00
Resolved: 2022-12-16 16:33:58+00:00

STR

1. Use a Firefox version prior to 108
1. Set the default engine to an application provided one that is not the default engine.
1. Shutdown Firefox.
1. Create a new profile, and copy the `search.json.mozlz4` file into that profile.
  * Note: [SUMO suggests](https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles#firefox:win8:fx107) to copy the profile when moving to a new computer.
  * Users may also simply copy the file to copy their search settings.
1. Startup Firefox with the new profile.
1. Upgrade Firefox to version 108.

Expected Results

=> The default search engine set in step 2 is retained.

Actual Results

=> The default search engine is reset to the application default (typically Google).
Bug: browser.tabs.tabmanager.enabled preference is not respected if the tab manager / "List all tabs" button is moved from its default position
Status: NEW
Priority: --
Created: 2022-12-15 16:32:36+00:00
Resolved: 2024-10-04 08:07:30+00:00

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

Steps to reproduce:

1. Create new firefox profile.
2. Right click toolbar, select "Customise Toolbar..."
3. Move "List all tabs" button from the right to the left of the tabs bar
4. Change preference browser.tabs.tabmanager.enabled from true to false
5. Quit, then reopen, firefox


Actual results:

The "List all tabs" button is still visible.

Information from another user (also 108.0):
Sidenote: moving the tabmanagement icon back to its original position ... instantly hides/removes it ... without having to restart the browser. Kind of seems like not the icon but some kind of container is actually removed via the config setting... that would kind of explain why it doesn't have any effect when it has been re-positioned.


Expected results:

The "List all tabs" button should not be visible.
Bug: [Window/MacOS] Investigate Voice Over issues for window modals
Status: NEW
Priority: P3
Created: 2022-12-15 17:07:48+00:00
Resolved: 2023-01-10 16:48:15+00:00

From [Emily's feedback on the invoke window modal patch](https://phabricator.services.mozilla.com/D162904)

On both Windows and MacOS, the screen reader is not reading the content as expected.

- On Windows the h2 (subtitle) doesn't get consistently read 
- On MacOS the modal's primary button gets focus and the screen reader skips the rest of the content on the first screen. (Hitting "skip this step" prompts the reader to read all the modal content on the second screen, maybe having to do with triggering a reload.)
Bug: Save to pocket asks to login every time . Login state is not saved. As a result, save to pocket does not work.
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-12-15 17:37:40+00:00
Resolved: 2023-01-11 14:53:05+00:00

+++ This bug was initially created as a clone of Bug #1475758 +++

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

Steps to reproduce:

Open a website in nightly and press save to pocket.


Actual results:

Asks to login after having previously successfully logged in


Expected results:

Should have saved after first login
Bug: Firefox 109 consistently crashes
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-12-15 18:02:55+00:00
Resolved: 2023-01-20 13:41:36+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.6.1 Safari/605.1.15

Steps to reproduce:

Repeatedly ran Firefox 109.0


Actual results:

The browser always crashed. And when I tried Firefox 108.0, it refused to use my Profile. So all passwords and at least a decade of bookmarks are there (I looked at Library/Application Support/Firefox in a terminal.


Expected results:

Hey, 109 SHOULD work guys. I get automatic updates for beta versions. I do have a Time Machine backup of older versions. That's where I found my Firefox 108.
Bug: Fix styling for the Screenshots "cancel" overlay button in windows HCM
Status: NEW
Priority: P2
Created: 2022-12-15 20:14:35+00:00
Resolved: 2023-10-11 09:39:56+00:00

STR: 
- toggle the `screenshots.browser.component.enabled` pref to true in about:config
- Enable high contrast mode in windows settings
- Use ctrl+shift+s or toolbar button to show the Screenshots UI and select an element or region of the page using the drag handles

ER: 
- The "Cancel" button the middle of the screen should be using high-contrast background and text colors from the Windows' HCM theme

AR: 
- The "Cancel" button text is invisible
Bug: Firefox Nightly-Bookmarks-Dropdown when hover over "other Bookmarks" it collapses instead of opens to right and all other bookmarks cannot be seen in dropdown. Restart of FF Nightly fixes it.
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-12-16 00:09:30+00:00
Resolved: 2022-12-22 17:24:18+00:00

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

Steps to reproduce:

Bookmark dropdown button in toolbar. Hover over Other bookmarks causes other bookmarks to collapse instead of cascading to the right and all other bookmarks cannot be accessed.


Actual results:

Cannot access all bookmark folders from dropdown button in toolbar after hovering over or clicking Other Bookmarks.


Expected results:

Able to access all bookmark folders from dropdown button in toolbar.
I have gone as far back as 2022-12-14-16-24-11 and the issue is still present. I even cleaned out all bookmarks in the other bookmarks folder, to no avail.
Bug: Remove EARLY_BETA_OR_EARLIER use from DLL Blocklist Code
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2022-12-16 02:12:10+00:00
Resolved: 2023-01-27 14:53:41+00:00

In [DLLBlockList.cpp IsDependentModule()](https://searchfox.org/mozilla-central/rev/b4de9fa6fe3fb425129093c3deb1dae0686f7a2b/browser/app/winlauncher/freestanding/DllBlocklist.cpp#263), we use `#if defined(EARLY_BETA_OR_EARLIER)`. We should not use EARLY_BETA_OR_EARLIER for blocking code because we want Beta to be a viable test for compatibility with Release. It's confusing for 3rd parties to have changes like this on some Beta builds, but not all. We should either ship that code, limit it to Nightly, or remove it.
Bug: Page and source showing as hieroglyphs on 108.0.2
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-12-16 09:29:31+00:00
Resolved: 2022-12-28 18:55:08+00:00

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

Steps to reproduce:

With firefox version 108.0.2 visit https://www.bonusfinder.co/wp-admin


Actual results:

page and source code is all hieroglyphs


Expected results:

wordpress login in shown on page and html in source code
(just a note: firefox version 108.0 opens up this page fine)
Bug: [Experiment] Users on Windows 7 are not enrolled in the "Device migration - Existing users ECO2212 EN" experiment.
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-12-16 11:21:31+00:00
Resolved: 2022-12-19 15:41:52+00:00

**[Notes]:**
- I have observed that in the [experiment’s targeting expression](https://experimenter.services.mozilla.com/nimbus/device-migration-existing-users-eco2212-en) we have the `os.windowsVersion >= 7` parameter, however, it seems that the browser targets the NT version which is `6.1` for Windows 7. 
- I have evaluated the `os.windowsVersion` parameter in the "ASRouter" page using `6.1` instead of `7` and the result was `true`.

**[Affected versions]:**
- Firefox Release 108.0 - Build ID: 20221208122842

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

**[Prerequisites]:**
- Have a Firefox en-* locale installed.
- Have a Firefox profile older than 28 days.
- Have the "[user.js](https://drive.google.com/file/d/1rwitzXBXx4x32Q5_kp8Jmzk7J2dym6-p/view?usp=share_link)" file saved to disk.

**[Steps to reproduce]:**
1. Navigate to the profile folder from prerequisites and paste the "user.js" file.
2. Open the browser using the profile from the prerequisites.
3. Navigate to the "about:studies" page and observe the listed experiments.

**[Expected result]:**
- The "Device migration - Existing users ECO2212 EN" experiment is displayed.
    
**[Actual result]:**
- The "Device migration - Existing users ECO2212 EN" experiment is **NOT** displayed.

**[Additional Notes]:**
- Also a message from the "RSloader" saying that the "device-migration-existing-users-eco2212-en did not match due to targeting" is displayed in the "Browser Console".
- This issue is not reproducible on Windows 10 and Windows 11.
- This issue is reproducible on all Firefox Versions targeted by the experiment.
- Attached is a screen recording of the issue:
Bug: [Experiment] A validation error is displayed in the "Browser Console" when trying to enroll in the "Device migration - Existing users ECO2212 EN" experiment on Firefox 100 to 104 versions
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-12-16 13:13:41+00:00
Resolved: 2023-03-10 14:58:39+00:00

**[Notes]:**
- The following error is displayed in the "Browser Console":
 `Experiment device-migration-existing-users-eco2212-en branch 0 feature spotlight does not validate: [
  {
    "instanceLocation": "#",
    "keyword": "required",
    "keywordLocation": "#/required",
    "error": "Instance does not have required property \"groups\"."
  }
]` .

**[Affected versions]:**
- Firefox Release  100.0.2 - Build ID: 20220519220738
- Firefox Release  101.0.1 - Build ID: 20220608170832
- Firefox Release  102.0.1 - Build ID: 20220705093820
- Firefox Release  103.0.2 - Build ID: 20220808125904

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

**[Prerequisites]:**
- Have a Firefox en-* locale installed.
- Have a Firefox profile older than 28 days.
- Have the "[user.js](https://drive.google.com/file/d/1rwitzXBXx4x32Q5_kp8Jmzk7J2dym6-p/view?usp=share_link)" file saved to disk.

**[Steps to reproduce]:**
1. Navigate to the profile folder from prerequisites and paste the "user.js" file.
2. Open the browser using the profile from the prerequisites.
3. Navigate to the "about:studies" page and observe the listed experiments.

**[Expected result]:**
- The "Device migration - Existing users ECO2212 EN" experiment is displayed.
    
**[Actual result]:**
- The "Device migration - Existing users ECO2212 EN" experiment is **NOT** displayed.

**[Additional Notes]:**
- This issue is no longer reproducible on Firefox 104 and above versions.
- Attached is a screen recording of the issue:
Bug: Installation of Asan Nightly on W11 Failed - clang_rt.asan_dynamic-x86_64.dll Not found
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-12-16 13:49:44+00:00
Resolved: 2022-12-17 04:00:15+00:00

User Agent: Mozilla/5.0 (Linux; Android 10; VOG-L29) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Mobile Safari/537.36

Steps to reproduce:

Installed a fresh and clean Windows 11 with nö security or similar Settings.
Downloaded newest Nightly of asan and get the Error, so i cant Start and use Asan.


Actual results:

Asan night is not starting. Its crashes with id 0xc0000142
Bug: Inconsistent search term persistence: sometimes it persists to a page linked off a SERP, sometimes it doesn't
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-12-16 14:19:43+00:00
Resolved: 2022-12-16 18:47:29+00:00

I might not have STR for this, but I was looking at Bigquery documentation and did the following:

1) Search for "bigquery window functions" by selecting the top history result from the awesomebar (I've looked at this a lot)
2) The search term persists on the SERP.
3) Select the top result
4) The search term continues to persist while I visit https://cloud.google.com/bigquery/docs/reference/standard-sql/window-function-calls and throughout navigations on that page (to anchors like "Referencing a Named Window" and to other locations like via "Contact Us")
    - Now, These docs appear to actually be a SPA given its internal loading bar (and atrocious loading times. Why must it make me long for java sdk docs in their frameset glory) so maybe this isn't actually navigation.

But now it won't reproduce : ( If I do the same thing over again, it doesn't happen.
Bug: Some versions including Firefox ESR do not upload properly to Firefox Sync
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-12-16 15:00:12+00:00
Resolved: 2022-12-16 16:22:15+00:00

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

Steps to reproduce:

1. Log in to your Firefox account.
2. Enable Firefox Sync and synchronize.
3. Check if the information (open tabs, etc.) from Firefox ESR is synchronized from other terminals.


Actual results:

Data syncing from Firefox ESR is not happening and an error log is created when looking at about:sync-log.
Rapid Release Firefox does not have this problem.


Expected results:

Data is synchronized from the Firefox ESR, and I can check the tabs etc. that are open in Firefox ESR from other devices.
Bug: [Regression] accesskey turned into non-uniform letter case
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-12-16 19:35:30+00:00
Resolved: 2023-12-11 15:23:31+00:00

In multiple locales, the context menu's access key is show as "Label (key)" deal with the letter is not in the translation, and the key should always be uppercase. In recent versions, this has become based on the original character, which is ugly to users. It affects the zh-CN, zh-TW, ja, etc.

STR:
1. Start the affected locale version. e.g. https://ftp.mozilla.org/pub/firefox/releases/109.0b3/win64/zh-CN/Firefox%20Setup%20109.0b3.exe, or app: firefox-l10n in mozregression.
2. Check the context menu items on tab, tabs bar, links, images, etc.


Actual results:
See the screenshot, the accesskey case is mixed.


Regression window:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=efbd04cb07486419679cf588ba6095f7ef9edef6&tochange=f85cd6ba1889c83b01c97d47a337caac6dcc1d8f
The https://hg.mozilla.org/mozilla-central/rev/9da892f98d1bdff624efca7bd698b0142d136a71 is suspect.
Bug: New "Open with" menu item for PDFs on macOS does not support "Always open with"
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-12-16 19:45:50+00:00
Resolved: 2023-03-09 18:27:04+00:00

Steps to reproduce:

Version: 109.0b3
Build ID: 20221215185833

https://bugzilla.mozilla.org/show_bug.cgi?id=1683278

^ the above issue was recently fixed (thanks!!) and is scheduled for Firefox 109. I have wanted this for a long time, so I downloaded the 109 beta to test it.

The fix works verbatim (on macOS, you can right-click in Finder and "Open with" → Firefox Developer Edition). HOWEVER, if you try to instead do this:

1. Use Finder to navigate to folder containing PDF file
2. Right-click, "Open with" → "Other..."
3. Check "Always Open With"
4. Select "Firefox Developer Edition.app" → Open

then I get an error from macOS


Actual results:

I see a popup from macOS saying "<your file name>.pdf cannot be opened because it is from an unidentified developer. macOS cannot verify that this app is free from malware. Firefox Developer Edition downloaded this file today at 10:58 AM."

This is odd, because the PDF file itself shouldn't be the thing that needs to be code-signed—Firefox Developer Edition is code-signed, but the error message mentions the PDF file.


Expected results:

Using the "Always Open With" checkbox should allow changing the default file handler for PDF files.
Bug: Addons don't work on new tab page anymore
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-12-16 21:06:38+00:00
Resolved: 2022-12-16 21:14:58+00:00

Since Firefox 108, it seems that the mouse gestures addon doesn't work on the new tab page anymore, when the new tab page is set to be an empty page.
This is a regression from Firefox 107.
Bug: Problems with custom new tab
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2022-12-17 05:15:46+00:00
Resolved: 2022-12-21 17:44:36+00:00

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

Steps to reproduce:

1. Install this add-on https://addons.mozilla.org/en-US/firefox/addon/infinity-new-tab-pro-firefox/
2. It would automatically set this as default custom new tab,
3. Close and reopen Firefox,
4. Go back to home settings and look to “New tabs” section.


Actual results:

It reverts back to Firefox home.


Expected results:

The custom new tab should stay.