Ask me anything!
Have a question you always wanted to ask Moonchild but never did? Now's your chance!
From 2026-03-08 to 2026-03-15 I'll be open to
any question by the community, after which I'll provide answers.
Go here to participate:
https://forum.palemoon.org/viewtopic.php?f=66&t=33222
For support with specific websites
Moderator: trava90
Forum rules
Please
always mention the name/domain of the website in question in your topic title.
Please one website per topic thread (to help keep things organized). While behavior on different sites might at first glance seem similar, they are not necessarily caused by the same.
Please try to include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:
- Clear any current output
- Navigate or refresh the page in question
- Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.
-
Harkonnen
- Moon lover

- Posts: 94
- Joined: 2014-11-04, 12:27
- Location: Kiev, Ukraine
Post
by Harkonnen » 2026-01-31, 21:59
Go to
https://yasno.ua/my, see a blank page that says "Application error: a client-side exception has occurred while loading yasno.ua (see the browser console for more infor"
Error console outputs this
Code: Select all
Timestamp: 31/01/26 23:56:43
Warning: Content Security Policy: Ignoring “'unsafe-inline'” within script-src: nonce-source or hash-source specified
Timestamp: 31/01/26 23:56:43
Warning: Content Security Policy: Couldn’t process unknown directive ‘require-trusted-types-for’
Timestamp: 31/01/26 23:56:44
Warning: Use of removeAttributeNode() is deprecated. Use removeAttribute() instead.
Source File: https://yasno.ua/_next/static/chunks/4bd1b696-182b6b13bdad92e3.js
Line: 1
Timestamp: 31/01/26 23:56:46
Error: TypeError: m is null
Source File: https://yasno.ua/supportChat/static/js/main.f4217dfa.js
Line: 1
-
vannilla
- Moon Magic practitioner

- Posts: 2536
- Joined: 2018-05-05, 13:29
Post
by vannilla » 2026-01-31, 22:38
Not much to do here. Whatever is causing this error has been hidden by other code.
If you really need to access the site you should use a different browser, otherwise you can try getting in touch with their dev team and ask them to test a debug build of the code with Pale Moon. It takes longer to communicate your intent than to run the test, if they can't fix it I suppose that's it but checking what's going on takes nothing.
-
adoxa
- Astronaut

- Posts: 601
- Joined: 2019-03-16, 13:26
- Location: Qld, Aus.
Post
by adoxa » 2026-02-01, 00:20
It's another instance of Next.js using "x:/" as a base URL, unsupported by UXP. Here's a
Modify HTTP Response filter to replace it.
Code: Select all
[["yasno.ua",["/webpack-.*\\.js$/",["x:/","http://x/"]]]]