av9ash/GitBugs huggingface dataset:
Bug: After adding 6 languages, some button in "Firefox Language Settings" window cannot be displayed fully.
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-04-25 10:21:06+00:00
Resolved: 2022-04-25 10:45:11+00:00

[Affected versions]:
- Firefox Release 99.0.1 (64-bit)
- Firefox Nightly 101.0a1 (2022-04-23) (64-bit)

[Affected Platforms]:
- macOS 10.15.7
- Windows 10 x64

[Steps to reproduce]:
1. Launch Firefox, and access "about preferences".
2. Scroll down to the ”Language“ area.
3. Click on the "Set Alternatives..." Button and then pop up the "Firefox Language Settings" window.
4. Add muliptle languages to the window until 6 languages are added.
5. Observe the "OK", "Cancel" and "Help" Button.

[Expected result]:
- A scroll bar appears next to added languages, allowing the user to scroll through the languages. And "OK", "Cancel" and "Help" Buttons display normally.

[Actual result]:
- These Buttons ("OK", "Cancel" and "Help") move down and cannot be displayed completely. The window needs to be dragged to display the full Buttons.
Bug: test_timer.js uses unknown Services member properties
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-04-25 10:39:51+00:00
Resolved: 2022-05-19 02:54:28+00:00

In test_timer.js there are a [couple of accesses](https://searchfox.org/mozilla-central/rev/13d69189a8abfc5064fe44944550b9b6eb4544f5/toolkit/modules/tests/xpcshell/test_timer.js#44,112) of `Services.mainThreadEventTarget`, however that is not available on `Services` and should probably be `Services.tm.mainThreadEventTarget`.

If this is fixed or not, it does not affect the test passing, which also makes me wonder if the test is actually testing what bug 1384041 intended it to test.
Bug: [linux] new window context menu hotkey can open in tab
Status: UNCONFIRMED
Priority: P3
Created: 2022-04-25 13:29:22+00:00
Resolved: 2022-05-22 20:42:46+00:00

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

Steps to reproduce:

On Linux, quickly performing a Right Click and pressing 'd' for Open in New Window.


Actual results:

Performing quickly can open in new tab instead of a window. I have done this several times for a few nightly releases now (maybe since 99? hard to say).

Does not happen in Private Window but unsure if this is because it is a different hotkey.


Expected results:

Open in New Window consistently every time.


### System Info

- Void Linux 5.17.2
- gtk+-2.24.33_1
- gtk+3-3.24.31_1

I wish I could attach about:support to my user profile on here.

### possibly related

- https://bugzilla.mozilla.org/show_bug.cgi?id=1694992
- https://bugzilla.mozilla.org/show_bug.cgi?id=1748831
Bug: History suggestions should not include multiple sites that only vary by the page hash
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-04-25 18:40:00+00:00
Resolved: 2022-04-26 12:20:25+00:00

See attached screenshot. In this case, I had six suggestions from my history and they all linked to the same document. 1 of the 6 was different based on the path but the other 5 only differ in the location hash. These (essentially) duplicates prevented me from finding other history suggestions that I was looking for.
Bug: JS Load Restrictions Telemetry still has prefcalls.js entries
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-04-25 20:38:52+00:00
Resolved: 2022-05-20 20:11:06+00:00

```
SELECT event_object,
       event_method,
       event_string_value,
       app_version,
       normalized_channel,
       TO_JSON_STRING(event_map_values),
       event_process,
       count(*) AS count_reports,
       count(distinct client_id) as count_distinct_clients
FROM telemetry.events
WHERE event_category = 'security'
  AND event_method = 'javascriptLoad'
  AND submission_date >= '2022-01-1'
  AND (
    --(normalized_channel = 'release' and app_version > '98') or
    (normalized_channel = 'beta' and mozfun.norm.extract_version(app_version, 'major') = 100) or
    (normalized_channel = 'nightly' and app_version = '101.0a1')
    )
GROUP BY event_method,
         event_object,
         event_string_value,
         app_version,
         normalized_channel,
         TO_JSON_STRING(event_map_values),
         event_process
ORDER BY app_version desc, normalized_channel, event_string_value
```

Telemetry shows `prefcalls.js` showing up in Beta (as well as http:// and https:// schemes (and one chrome:// scheme??)

I had hoped that Bug 1759887 might have fixed this (I know it fixed one very unusual corner case) but it seems we are back at the drawing board for how in the world prefcalls.js can show up.  I'll update this bug with my understanding of why this should never happen....
Bug: After pressing Tab key, the menu of sorting logins disappears.
Status: NEW
Priority: P3
Created: 2022-04-26 01:42:42+00:00
Resolved: 2022-04-28 22:10:52+00:00

[Affected versions]:
- Firefox Nightly 101.0a1 (2022-04-23) (64-bit)
- Firefox Release 99.0.1 (64-bit)

[Affected Platforms]:
- macOS 10.15.7
- Windows 10 x64

[Steps to reproduce]:
1. Launch Firefox, and access "about:logins".
2. Click on the "Name(A-Z)" in the upper left corner of the page, and then a menu about sorting logins appears.
3. Press Tab key.

[Expected result]:
-  After Pressing Tab key, the blue box moves down to select an option in the menu.

[Actual result]:
-  After Pressing Tab key, the menu disappears. However, I can press Up and Down keys to select an option.
Bug: Intermittent JavaScript error: resource:///modules/AsyncTabSwitcher.jsm, line 504: Error: Assertion failure
Status: RESOLVED
Priority: P5
Resolution: INVALID
Created: 2022-04-26 02:08:02+00:00
Resolved: 2022-08-29 06:40:34+00:00

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

---
```

```
Bug: Entered Text should be in the search bar.
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2022-04-26 08:50:34+00:00
Resolved: 2022-04-26 11:34:21+00:00

[Affected versions]:
- Firefox Nightly 101.0a1 (2022-04-16) (64-bit)
- Firefox Release 99.0.1 (64-bit)

[Affected Platforms]:
- Windows 10 x64
- macOS 10.15.7

[Steps to reproduce]:
1. Launch Firefox.
2. In a "New Tab", enter some text in the search bar, such as "www.google.com".

[Expected result]:
- The entered text is shown in the search bar or in both the search bar and the address bar.

[Actual result]:
- The entered text is only shown in the top address bar.

[Notes]:
- The search bar in the middle of the New Tab.
Bug: [Prod] The Nimbus-Preview collection does not work anymore as we are unable to enroll in Preview experiments
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-04-26 09:27:27+00:00
Resolved: 2022-05-17 14:21:18+00:00

**[Notes]:**
- This is reproducible with both the PRODUCTION and STAGE PREVIEW.
- Besides force enrollment, we have also tried enrolling in the experiment by generating user IDs for each experiment branch. However, we did not manage to get enrolled in the experiment this way either.
- The following errors are thrown in the Browser Console:
`[Exception... "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIAppStartup.secondsSinceLastOSRestart]"  nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)"  location: "JS frame :: resource:///modules/BrowserGlue.jsm :: _collectStartupConditionsTelemetry :: line 1570"  data: no] BrowserGlue.jsm:1570:9`
`services.settings: main-preview/nimbus-preview Signature failed  InvalidSignatureError: Invalid content signature (main-preview/nimbus-preview) RemoteSettingsClient.jsm:965`
`services.settings: main-preview/nimbus-preview local data was corrupted RemoteSettingsClient.jsm:1000`
`services.settings: main-preview/nimbus-preview Signature verified failed. Retry from scratch RemoteSettingsClient.jsm:674`
`services.settings: main-preview/nimbus-preview Signature failed again InvalidSignatureError: Invalid content signature (main-preview/nimbus-preview) RemoteSettingsClient.jsm:965`
`Invalid content signature (main-preview/nimbus-preview) RemoteSettingsClient.jsm:135`

**[Affected versions]:**
- Firefox RC 100, Build ID: 20220425210429
- Firefox Beta 100.0b, Build ID: 20220421201645

**[Affected platforms]:**
- Windows 10 x64
- macOS 11.6.5
- Ubuntu 20.04 x64

**[Prerequisites]:**
- Have a new Nimbus experiment created and launched to preview.
- Have the `nimbus.debug` pref set to `true`.
- Change `messaging-system.rsexperimentloader.collection_id` to `nimbus-preview` value.

**[Steps to reproduce]:**
1. Open the browser with the profile from prerequisites.
2. Paste the force enrollment link from the recipe in a new tab.
3. Press the “Enter” key and observe what happens next.

**[Expected result]:**
- You are enrolled in the experiment.

**[Actual result]:**
- The `Could not find experiment slug <slug name> in collection nimbus-preview` error is displayed in the “about:studies” page.

**[Additional notes]:**
- [Here](https://drive.google.com/file/d/1MCPtYgTbXZyOZBZn06SlHhob_EERkfUh/view?usp=sharing) is a screen recording with the issue.
Bug: Firefox sometimes temporarily "freezes" when opening a new tab and writing into the location bar
Status: RESOLVED
Priority: P2
Resolution: INVALID
Created: 2022-04-26 10:31:42+00:00
Resolved: 2022-06-17 11:48:49+00:00

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

Steps to reproduce:

Context:
- I am using Firefox Developer Edition Version 100.0b9 (64-bit).
- My system is Windows 11.
- I have multiple tabs open.
- I am logged into my Firefox account for syncing.
- It makes no difference whether I am using Firefox in troubleshooting mode or not.
- This bug resurfaced even after a fresh install of Windows on my machine (during which I formatted the harddrive).

What did I do?
1. I open a new tab (usually by hitting Ctrl+T). A new tab opens and the location bar is auto-focused.
2. I start typing.

This is where Firefox sometimes seems to freeze to some extent (I will present more details in "What happened?").

From here on out, I can take three paths, each resulting in a different outcome:

(A) I complete typing my query and hit Enter right away.

(B) I wait for Firefox to catch up before completing my query and hitting Enter.

(C) I move my mouse before completing my query and hitting Enter.


Actual results:

After going through steps 1 and 2 as descriped above, sometimes (usually about every 10th to 20th attempt, sometimes much more often - I could not identify a pattern) the following occurs:

After a random amount of characters entered (usually 1-3) into the location bar, all further characters will not be displayed. Also no suggestions will be shown below the location bar.

(A) If I nevertheless complete my query and hit Enter right away, Firefox will remain frozen for a few seconds (I'd say 2-20), and then execute my query using only those (usually 1-3) characters that were displayed in the location bar. Usually this takes me to a website I have frequently visited in the past starting with those letters.

In other words: Firefox seems to just "forget" all characters entered after the freeze starts, then autocomplete the few characters I entered before the freeze and then take my Enter as a confirmation of the suggested autocompletion (which I never saw).

(B) If I decide to wait for Firefox to catch up, I'll have to wait for about 2-20 seconds. I know Firefox has caught up when suddenly suggestions appear below the location bar. I can then proceed to enter and submit my query without problem.

(C) This is the strangest thing: As soon as I move my mouse the tiniest bit the freeze ends immediately and I can proceed entering and submitting my query. I have tested this about 10-20 times now, waiting different amounts of time before moving the mouse to make sure it is actually the mouse movement triggering Firefox to wake up. I am now sure of it.


Expected results:

Firefox should not freeze mid-entering my query into the location bar.
Bug: application/pdf files are not downloaded when an anchor has the "download" attribute and a blob: URL as href
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-04-26 12:06:47+00:00
Resolved: 2022-04-29 13:08:05+00:00

Steps to reproduce:

1. Fetched a pdf file
2. created an object URL and set it as an anchor href
3. set the anchor download attribute
4. clicked the anchor

<!doctype html>
<html lang="en">
<head>
    <title>test</title>
</head>
<body>
</body>
<script>
    fetch("/file.pdf").then(r => r.blob()).then((blob) => {
        const a = document.createElement('a');
        a.href = URL.createObjectURL(blob);
        a.download = 'foo'
        a.innerHTML = "clickme"
        document.body.appendChild(a);
    });
</script>
</html>



Actual results:

The file is not downloaded and is opened in the same tab instead. This does not happen when the type of the file is different from "application/pdf".


Expected results:

The file should be downloaded with the name "foo" and not opened in the same tab.
Bug: [Experiment] A validation error is displayed in the "Browser Console" when trying to enroll in the "Covered Regular ECO2204" experiment
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-04-26 13:37:56+00:00
Resolved: 2022-06-21 15:22:55+00:00

**[Affected versions]:**
- Firefox Beta 100.0 - Build ID: 20220425210429

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

**[Prerequisites]:**
- Have a Firefox en-* locale build installed.
- Have a Firefox profile older than 28 days
- Firefox is NOT pinned to the taskbar/dock.
- Have the "[user.js](https://drive.google.com/file/d/1lkXdSxtWiT23CMv9WecT72y_UM3V0cXI/view?usp=sharing)" file saved to your PC.

**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to the profile folder and paste the "user.js" file from the prerequisites.
3. Restart the browser and focus the "Browser Console".
4. Observe the displayed errors.

**[Expected result]:**
- No error is displayed and you are successfully enrolled in the experiment.

**[Actual result]:**
- A validation error is displayed and you are NOT enrolled in the experiment.

**[Notes]:**
- This issue is not reproducible if a force enrollment is performed instead of a natural one.
- Attached a screenshot of the error.
Bug: checkPinCurrentAppToTaskbar is used on the main thread and does blocking I/O
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2022-04-26 13:56:06+00:00
Resolved: 2022-05-10 20:05:07+00:00

The comment on the `checkPinCurrentAppToTaskbar` API says "NOTE: This method probably shouldn't be used on the main thread, it performs blocking disk I/O." https://searchfox.org/mozilla-central/rev/0249c123e74640ed91edeabba00649ef4d929372/browser/components/shell/nsIWindowsShellService.idl#92-93,97

But BHR data shows that this is being called from `get doesAppNeedPin activity-stream/lib/ASRouterTargeting.jsm:664 `, and it represents a bit more than 0.5% of the total hang time for Nightly. This code was added in bug 1730497.
Bug: [Experiment] The "ECO" spotlight would be displayed even if Firefox is already pinned to the taskbar/dock
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-04-26 13:57:30+00:00
Resolved: 2022-05-03 08:49:19+00:00

**[Notes]:**
- Unfortunately we cannot validate this scenario since we are blocked by bug 1766430, however, we observed that the `doesAppNeedPin` attribute is missing from the full targeting experssion.

**[Affected versions]:**
- Firefox Beta 100.0 - Build ID: 20220425210429

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

**[Prerequisites]:**
- Have a Firefox en-* locale build installed.
- Have Firefox pinned to the taskbar/dock.
- Have the "[user.js](https://drive.google.com/file/d/1lkXdSxtWiT23CMv9WecT72y_UM3V0cXI/view?usp=sharing)" file saved to your PC.

**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to the profile folder and paste the "user.js" file from the prerequisites.
3. Restart the browser and observe the behavior.

**[Expected result]:**
- The "ECO" spotlight is **NOT** displayed.

**[Actual result]:**
- The ECO spotlight is displayed even if Firefox is pinned to the taskbar/dock.

**[Notes]:**
- Attached a screenshot with the targeting expression.
Bug: When pressing Tab key in the "Settings - Autoplay" window of "about:preferences#privacy", the blue selection box may disappear.
Status: NEW
Priority: P3
Created: 2022-04-26 14:02:07+00:00
Resolved: 2022-08-16 10:32:01+00:00

[Affected versions]:
- Firefox Nightly 101.0a1 (2022-04-23) (64-bit)
- Firefox Release 99.0.1 (64-bit)

[Affected Platforms]:
- Windows 10 x64
- macOS 10.15.7

[Steps to reproduce]:
1. Launch Firefox, and access "about:preferences#privacy".
2. Scroll down to the "Permissions" section
3. Click on "Settings...' Button of "Autoplay" and pop up the "Settings - Autoplay" window.
4. Press Tab Key, then a blue selection box will move and select clickable UI.
5. Press Tab Key multiple times, until the blue selection box select "X" (Close Button) of "Settings - Autoplay" window. 
6. Press Tab Key once again.

[Expected result]:
- The blue box select select another clickable UI, such as the drop-down menu next to "Default for all websites". 

[Actual result]:
- The blue box disappear, until press Tab key once again.

[Notes]:
- The same situation exists for many similar windows, such as "Settings - Lociation Permissions" window, "Allowed Websites - Pop-ups" window, and so on.
Bug: Bookmarks menu seperator context menu needs too precise mouse click
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2022-04-26 15:52:52+00:00
Resolved: 2023-07-09 02:10:10+00:00

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

Steps to reproduce:

1. open the bookmarks menu
2. right click onto a separator line between to submenus


Actual results:

One of two menus pops up:

- If I clicked exactly, pixel-precisely with the mouse pointer tip onto the separation line, the context menu for the separator appears. This is useful e.g. to delete a separator.

- If I clicked at least by one pixel above or below the line, the context menu of the submenu above or below the separator appears.


Expected results:

When right-clicking close to the separator line (outside of the "grey areas" of the items above and below), the separator's menu should pop up.

Note that the "Manage bookmarks" and "Bookmarks sidebar" features allow to work around this issue. Right-clicking onto a separator there is no game of skill like directly in the bookmarks menu.
Bug: Intermittent browser/components/search/test/browser/browser_contentContextMenu.js | application terminated with exit code 6
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2022-04-26 16:52:36+00:00
Resolved: 2022-04-26 17:11:16+00:00

**Filed by:** dmosedale [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=375834903&repo=try
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/B4K_MSNCSX-nNxam6M-GBw/runs/0/artifacts/public/logs/live_backing.log

---
```

```
Bug: Intermittent browser/components/search/test/browser/browser_contentContextMenu.js | application terminated with exit code 6
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2022-04-26 16:52:38+00:00
Resolved: 2022-04-26 17:11:13+00:00

**Filed by:** dmosedale [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=375834903&repo=try
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/B4K_MSNCSX-nNxam6M-GBw/runs/0/artifacts/public/logs/live_backing.log

---
```

```
Bug: Intermittent browser/base/content/test/contextMenu/browser_view_image.js | application terminated with exit code 6
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2022-04-26 17:58:50+00:00
Resolved: 2022-04-27 09:27:08+00:00

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

---
```

```
Bug: Intermittent browser/base/content/test/contextMenu/browser_view_image.js | application terminated with exit code 6
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2022-04-26 17:58:53+00:00
Resolved: 2022-04-27 09:27:13+00:00

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

---
```

```
Bug: Logins list may show two gray blocks.
Status: NEW
Priority: P3
Created: 2022-04-27 01:27:10+00:00
Resolved: 2022-04-28 15:51:51+00:00

[Affected versions]:
- Firefox Nightly 101.0a1 (2022-04-23) (64-bit)
- Firefox Release 99.0.1 (64-bit)

[Affected Platforms]:
- Windows 10 x64
- macOS 10.15.7

[Prerequisites]:
The Firefox account have saved more than 4 logins.


[Steps to reproduce]:
1. Launch Firefox, and access "about:logins".
2. Click on the first saved login. 
3. Press 'Down' key multiple times（more than 3 times）, then a gray color block moves down, which represent the option will be selected.
4. Click on the second saved login.
5. Press 'Down' key once again.


[Expected result]:
- There are only one gray color block in logins list.

[Actual result]:
- There are two gray color blocks in logins list. 

[Notes]:
- When there are two gray color blocks, I don't know when I click Enter key, whcih login will be selected.
Bug: The autofilled Firefox password can be seen, after the firefox account has been signout.
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-04-27 02:19:51+00:00
Resolved: 2022-05-02 00:32:26+00:00

[Affected versions]:
- Firefox Nightly 101.0a1 (2022-04-16) (64-bit)
- Firefox Release 99.0.1 (64-bit)

[Affected Platforms]:
- Windows 10 x64

[Prerequisites]:
- Firefox is already logged into an account and save the Firefox login information(user name and password) in the account.

[Steps to reproduce]:
1. Launch Firefox.
2. Click on the button with three horizontal lines in the upper left corner to open the "Application Menu".
3. Click on your account (your email address).
4. Click on "Sign out..." Button.
5. After the account signs out, close Firefox.
6. Launch Firefox again.
7. Click on "Sign in" Button, then the sign page appear. The password is autofilled.
8. Click the white area next to the password or click a key in password, such as Left or Right Key.

[Expected result]:
- The password is cannot be seen.

[Actual result]:
- There is a eye button appearing next to the password. After clicking the eye button, we can see the password.

[Notes]:
- The number of black dots representing the hidden password is also the same as the password length, which means other can easily know the length of my password.
Bug: csp is disabled but working
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-04-27 07:18:05+00:00
Resolved: 2022-04-27 07:23:31+00:00

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

Steps to reproduce:

update firefox from v97 to v99.
my js script is not working, it's a xhr requests.  about:
        var xhr = new XMLHttpRequest();
        var url = "http://example..."
        xhr.open('GET', url, false);
        xhr.onload = function () {
            // 请求结束后,在此处写处理代码
        };
        xhr.send(null);
        var response = xhr.response
        return JSON.parse(response)

 


Actual results:

error:
#Uncaught DOMException: A network error occurred.
#Content Security Policy: 页面设置阻止读取位于 http://..的一项资源("connect-src")。


Expected results:

In firefox v97 about:config, I change the "security.csp.enable" from ture to false. The script is working. But in firefox v99, The script run error either the "security.csp.enable" is true or false.