Page 1 of 1

community.ui.com

Posted: 2022-05-10, 17:35
by KSAKS
Cannot load https://community.ui.com/ in Palemoon. Testing in clean portable Palemoon and I'm getting there just "A new version of community is available" window. Brave browser works fine.

Code: Select all

Timestamp: 10.5.2022 19:31:08
Warning: Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive.

Timestamp: 10.5.2022 19:31:09
Error: Content Security Policy: The page’s settings blocked the loading of a resource at self (“script-src https://community.ui.com https://maps.googleapis.com https://www.google-analytics.com 'sha256-4BFdsqEQeXRS5dX7nyt55zqAfGO3vO4bflffGMD5T50=' https://www.googletagmanager.com https://cdn.cookielaw.org https://geolocation.onetrust.com https://translate.googleapis.com https://static.airtable.com https://web.delighted.com https://d2yyd1h5u9mauk.cloudfront.net”). Source: call to eval() or related function blocked by CSP.
Source File: https://community.ui.com/js/6948.f1f900b1.js
Line: 2
Source Code:
call to eval() or related function blocked by CSP

Timestamp: 10.5.2022 19:31:09
Error: SyntaxError: expected expression, got '?'
Source File: https://community.ui.com/js/app.17cce4a5.chunk.js
Line: 1, Column: 548
Source Code:
ssign({releaseGroups:(null==n?void 0:n.publicReleaseGroups)??[]},{children:e.children}),void 0)},void 0);class g extends

Timestamp: 10.5.2022 19:33:11
Error: Error: 
Source File: https://community.ui.com/js/main.5a382cff.js
Line: 2243

Re: community.ui.com

Posted: 2022-05-10, 18:00
by Moonchild

Code: Select all

Error: SyntaxError: expected expression, got '?'
This would likely be the issue, which points to the site using a "nullish coalescing operator" in JavaScript and new addition to the language.
We don't support that new operator (yet).

Re: community.ui.com

Posted: 2022-05-10, 18:03
by KSAKS
Thanks for reply. Are there any possible workarounds for this? Or I need to wait until this will be supported in Palemoon?

Re: community.ui.com

Posted: 2022-05-10, 18:16
by Moonchild
There are no easy workarounds for this, aside from convincing the webmaster to be more browser-agnostic, at least until we have support for it.