Web site error at https://www.carcovers.com/

[Hugo Oberstein]

Hello, This is a fresh install (5 minutes use) of Pale Moon 33.8.0, 32 bit, without any add-ons, nor configuration changes. I hope I did this correctly. Thank you for looking into this.

Here is a problem with the "car covers" web site.
https://www.carcovers.com/

An error message appeared with a mostly blank screen:
" Application error: a client-side exception has occurred (see the browser console for more information). "

System Information:

Code: Select all

OS Name	Microsoft Windows 7 Professional
Version	6.1.7601 Service Pack 1 Build 7601
OS Manufacturer	Microsoft Corporation
System Type	x64-based PC
Processor	Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz, 3401 Mhz, 4 Core(s), 4 Logical Processor(s)
Installed Physical Memory (RAM)	8.00 GB

Browser Console output:

Code: Select all

Error sending WebSocket message: DOMException [InvalidStateError: "An attempt was made to use an object that is not, or is no longer, usable"
code: 11
nsresult: 0x8053000b
location: https://dashboard.heatmap.com/preprocessor.min.js?sid=3226:168]  
preprocessor.min.js:168:352
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIInterfaceRequestor.getInterface]  
network-monitor.js:298
RangeError: invalid value narrowSymbol for option currencyDisplay
Stack trace:
A@https://www.carcovers.com/_next/static/chunks/8641-68aa3cca53cefe19.js:1:28903
rk@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:40024
oB@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:116932
i5@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:95093
i6/<@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:94915
i6@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:94922
iq@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:92568
iH@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:92006
M@https://www.carcovers.com/_next/static/chunks/4109-6e22ac79b8226e14.js:25:1665
  
4109-6e22ac79b8226e14.js:1:3565
Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Stack trace:
oB@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:118250
i5@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:95093
i6/<@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:94915
i6@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:94922
iq@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:92568
iH@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:92006
M@https://www.carcovers.com/_next/static/chunks/4109-6e22ac79b8226e14.js:25:1665
  
4109-6e22ac79b8226e14.js:1:3565
Use of removeAttributeNode() is deprecated. Use removeAttribute() instead.  
96c8d384-de4000a4633721c9.js:9:81246
[GORGIAS-CHAT] Loading chat 01GYCCS6DKC5E5RSA7JY0T4Y7S...  
gorgias-chat-bundle-loader.js:1:996
Not a Shopify page or Shopify object not available  
preprocessor.min.js:210:455
Shopify object not available - skipping Shopify privacy checks  
preprocessor.min.js:1:456
Car Covers analytics was initialized.  
analytics.js:1:294576
 [Heatmap] Initializing recording system (instance #1)  
heatmap-light.min.js:1:387
 [Heatmap] Recording system initialized (instance #1) with HTTP transport (HTTP default)  
heatmap-light.min.js:109:209
 [Heatmap] Initializing recording system (instance #1)  
heatmap-light.min.js:1:387
 [Heatmap] Recording system initialized (instance #1) with HTTP transport (HTTP default)  
heatmap-light.min.js:109:209
Content Security Policy: Couldn’t process unknown directive ‘report-to’  
(unknown)
Error sending WebSocket message: DOMException [InvalidStateError: "An attempt was made to use an object that is not, or is no longer, usable"
code: 11
nsresult: 0x8053000b
location: https://dashboard.heatmap.com/preprocessor.min.js?sid=3226:168]  
preprocessor.min.js:168:352

Developer Web Console output:

Code: Select all

Use of removeAttributeNode() is deprecated. Use removeAttribute() instead.  
96c8d384-de4000a4633721c9.js:9:81246
RangeError: invalid value narrowSymbol for option currencyDisplay
Stack trace:
A@https://www.carcovers.com/_next/static/chunks/8641-68aa3cca53cefe19.js:1:28903
rk@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:40024
oB@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:116932
i5@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:95093
i6/<@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:94915
i6@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:94922
iq@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:92568
iH@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:92006
M@https://www.carcovers.com/_next/static/chunks/4109-6e22ac79b8226e14.js:25:1665
  
4109-6e22ac79b8226e14.js:1:3565
Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Stack trace:
oB@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:118250
i5@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:95093
i6/<@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:94915
i6@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:94922
iq@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:92568
iH@https://www.carcovers.com/_next/static/chunks/96c8d384-de4000a4633721c9.js:9:92006
M@https://www.carcovers.com/_next/static/chunks/4109-6e22ac79b8226e14.js:25:1665
  
4109-6e22ac79b8226e14.js:1:3565
[GORGIAS-CHAT] Loading chat 01GYCCS6DKC5E5RSA7JY0T4Y7S...  
gorgias-chat-bundle-loader.js:1:996
Not a Shopify page or Shopify object not available  
preprocessor.min.js:210:455
Shopify object not available - skipping Shopify privacy checks  
preprocessor.min.js:1:456
Car Covers analytics was initialized.  
analytics.js:1:294576
 [Heatmap] Initializing recording system (instance #1)  
heatmap-light.min.js:1:387
 [Heatmap] Recording system initialized (instance #1) with HTTP transport (HTTP default)  
heatmap-light.min.js:109:209
 [Heatmap] Initializing recording system (instance #1)  
heatmap-light.min.js:1:387
 [Heatmap] Recording system initialized (instance #1) with HTTP transport (HTTP default)  
heatmap-light.min.js:109:209
Error sending WebSocket message: DOMException [InvalidStateError: "An attempt was made to use an object that is not, or is no longer, usable"
code: 11
nsresult: 0x8053000b
location: https://dashboard.heatmap.com/preprocessor.min.js?sid=3226:168]  
preprocessor.min.js:168:352

[vannilla]

https://developer.mozilla.org/en-US/doc ... mberFormat
The narrowSymbol option is not supported by UXP, it seems.

[adoxa]

Here's a Modify HTTP Response filter to just stick with the dollar sign.

Code: Select all

[["www.carcovers.com",["/chunks.*\\.js$/",["\"\".concat(new Intl.NumberFormat(void 0,{style:\"currency\",currency:t,currencyDisplay:\"narrowSymbol\"}).format(parseFloat(s)))","\"$\".concat(s)"]]]]

[Hugo Oberstein]

Hello, This is a continuation of a problem with the site carcovers.com. This is a fresh install (5 minutes use) of Pale Moon 33.8.1.2, 32 bit, on Windows 7 SP1 64bit, without any add-ons, nor configuration changes to Pale Moon.

The web page tries to start, and for a few seconds has the page, then the error message appeared on a white screen: "Application error: a client-side exception has occurred (see the browser console for more information)."

Thank you Vanilla and Adoxa for the info. However I feel a brand new install of a browser should display a website without any add-ons. If it does not, then either the website has a error or the browser does. I post this in hopes that it will be investigated. If the problem is certain codes used on the website that Pale Moon cannot handle, and this is known and will be dealt with in the future, that is OK by me. As long as MoonChild and his fine developers know about it, I can wait for a future fix. (Ironically I can get to the site with an old ESR version of Firefox.)

As a complement, on another PC running PM 33.8.1.2 it appears to be one of the "smoothest" running Pale Moon versions so far. Good job.

Thank you for any help or information.

[moonbat]

This is a fresh install

What you need is a fresh profile, not a fresh install. Open the about:profiles page in a new tab and from there you can create a separate empty profile for testing purposes. Just launch that profile in a new browser instance to test problematic websites so that you can rule out any settings changes or addons that caused the problem. Reinstalling the browser will simply result in using whatever profile was last in use,if that was your regular one then all your addons and modified preferences would still apply.

[Hugo Oberstein]

Hello Moonbat,

Thank you for responding.

Moonbat said: "What you need is a fresh profile ... Reinstalling the browser will simply result in using whatever profile was last in use"

This is not a re-install of Pale Moon. This is a special test computer with Windows 7, that -never- had Pale Moon installed on it. This install is a fresh install without any previous Pale Moon history or settings so it is a fresh profile.

[Moonchild]

However I feel a brand new install of a browser should display a website without any add-ons. If it does not, then either the website has a error or the browser does.

I think this is they key issue here, not the profile.

If a website uses something the browser doesn't support, then there can be display issues. Normally this isn't a problem, but if the website then, on top, uses some kind of javascript framework to create its site, then, depending on how the framework handles something unsupported, it can completely kill site display. This is a problem with some modern websites because the framework devs assume every browser has the exact same feature set or they explicitly only develop for a very small handful of specific browsers and don't care about being agnostic or providing fallback.

What the suggested add-on does is work around this by changing some key parts of the website "on the wire" so the framework code is tweaked and it no longer just collapses like the house of cards it is when encountering something minor like in this case support for a very specific internationalization function for currency display. In effect it's "fixing the website to work on more browsers". The modern web just sometimes needs these kinds of workarounds unless you are on the dominant browser on the market (Google Chrome).

You can try to answer your question who's ultimately to blame here, but all that will likely do is polarize yourself one way or another and otherwise not be very helpful. That energy is probably better spent installing the add-on and making the site work with the suggested filter (and maybe let carcovers know their website is unusable in your preferred browser). It's shortcomings on both sides, IMHO. The browser for not supporting the 100% of the full set of features websites might ask for (which is a whole discussion on its own how we got there, to begin with...) and also the website for using a system that shuts down display entirely when encountering a minor visual display error (while the browser can otherwise display and work with the site just fine!)...

So your choice is to either use the suggested workaround with the add-on, use Google Chrome (or one of its clones), or use a different website for your needs than carcovers.com.

[Hugo Oberstein]

Hello Moonchild,

Thank you for commenting. I am always honored when the head man chimes in.

I understand what you mean about the building of websites and how many only focus on the largest percentage share of browser market. I also feel it is wrong of them to not "fall back" to more common approaches. It is actually improper website programming with bad error correction.

As I have learned decades ago, it is always best to have at least 2 browsers, and I usually have 3, on my main computer. As mentioned previously I could get to the site with an old Firefox ESR so I did make it to see what I wanted.

Thank you for all you and your developers do.