JavaScript-error: Problem open page with Firefox 114.0.1 (64-Bit)

[TomGPoint]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[noxone]

Hi, sorry, I would need some more information for this ;)

Even is I filter for Firefox I can only see two security related bugs, that I still need to handle. Could you please add some more detail to this issue?

[TomGPoint]

Hi , sorry , a bit lag of time because im on work . Here ist what the Error debugger says when you open the page: An error occurred with these details: - Exception: `[Exception... "File error: Not found" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: https://regex-generator.olafneumann.org/regex-generator.js?commitId=eab10fbb3bfe2dcf1605f316a21d715e9128d4fd :: <TOP_LEVEL> :: line 1" data: no]` - Commit ID: `eab10fbb3bfe2dcf1605f316a21d715e9128d4fd` - UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0 - Vendor: - Language: de - Platform: Win32 - CPU: Windows NT 10.0; Win64; x64 - TouchPoints: 0 - Plugins: - PDF Viewer - Chrome PDF Viewer - Chromium PDF Viewer - Microsoft Edge PDF Viewer - WebKit built-in PDF - StackTrace: Li: [Exception... "File error: Not found" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: https://regex-generator.olafneumann.org/regex-generator.js?commitId=eab10fbb3bfe2dcf1605f316a21d715e9128d4fd :: <TOP_LEVEL> :: line 1" data: no] Js@ https://regex-generator.olafneumann.org/regex-generator.js?commitId=eab10fbb3bfe2dcf1605f316a21d715e9128d4fd:1:107683 Li@ https://regex-generator.olafneumann.org/regex-generator.js?commitId=eab10fbb3bfe2dcf1605f316a21d715e9128d4fd:1:537257 ji@ https://regex-generator.olafneumann.org/regex-generator.js?commitId=eab10fbb3bfe2dcf1605f316a21d715e9128d4fd:1:536757 And that ist what I can see If I press F11 Uncaught NS_ERROR_FILE_NOT_FOUND: <anonymous> LocalStorageSettings.kt:35 <anonymous> LocalStorageSettings.kt:36 <anonymous> LocalStorageSettings.kt:58 Bs LocalStorageSettings.kt:26 Ps ApplicationSettings.kt:6 zs regex-generator.js:1 va LanguageAccordionCard.kt:57 $a api.kt:56 yl P6LanguageDisplay.kt:28 oa RGView.kt:44 ea RGController.kt:20 Ni RegexGenerator.kt:30 Ni RegexGenerator.kt:23 Bi RegexGenerator.kt:16 regex-generator.js:1 <https://regex-generator.olafneumann.org/regex-generator.js?commitId=eab10fbb3bfe2dcf1605f316a21d715e9128d4fd> Hope this can help you. Am Di., 20. Juni 2023 um 10:19 Uhr schrieb Olaf Neumann < ***@***.***>:

…

Hi, sorry, I would need some more information for this ;) Even is I filter for Firefox I can only see two security related bugs, that I still need to handle. Could you please add some more detail to this issue? — Reply to this email directly, view it on GitHub <#407 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANPWOA4YJC7LXLSHCUBGNILXMFMHPANCNFSM6AAAAAAZMZGCZI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[TomGPoint]

Here a hint of the unloaded file

<script type="text/javascript" src="**regex-generator.js**?commitId=eab10fbb3bfe2dcf1605f316a21d715e9128d4fd"></script>

[noxone]

Hm, ok. When does it appear? Right when opening the page? Or later when you want to do something?

[noxone]

Indeed... the Coffee stuff creates errors... that's a pitty.
SO I will probably just remove it.

[TomGPoint]

Hi Olaf , sorry for the late response.
I've realized that It has something to do with company intern FF configuration. The problem never appeared with chrome. And with an FF clean install the problem disappeared also.
I could now use your tool and it works excellent.

Sorry for the inconvenience !

[noxone]

Thank you for the update. I will then close this issue.