catppuccin
Chess.com Pieces not loading
Is there an existing issue outlining your problem?
- [x] I am using the latest version of the provided userstyle.
- [x] I have searched the existing issues and they do not solve my problem.
What userstyles are you seeing the problem on?
lbl:chess.com
Describe your problem.
The pieces don't load, I tried changing my theme to default but still no....
Attach screenshots.
No response
What browser(s) are you seeing the problem on?
Firefox 136.0
Any additional comments?
No response
Cannot reproduce on Firefox 137. Are you sure you are on the latest version of the userstyle? Make sure to run the updates in Stylus.
Cannot reproduce on Firefox 137. Are you sure you are on the latest version of the userstyle? Make sure to run the updates in Stylus.
I uninstalled and reinstalled the style but still no....
Do you see any console errors if you open the developer tools panel?
The pieces load for a second then dissappear and console has this
Uncaught (in promise)
error { target: script, isTrusted: true, srcElement: script, eventPhase: 0, bubbles: false, cancelable: false, returnValue: true, defaultPrevented: false, composed: false, timeStamp: 1335, … }
I'm having the same issue with the same error message in the console.
Running Firefox 141.0.3 on Linux and just updated to the latest version of the userstyle.
Cannot reproduce on 142.0b7 or 139.0.
with the same error message in the console.
The error message @thekushdhingra shows is seemingly unrelated. It's from Chess.com and I get it while the pieces still load correctly.
Can you try disabling all other browser extensions and seeing if that fixes the problem? If it does, try enabling one extension at a time until it stops working again - then tell us what that extension is and we can figure out why it is breaking this functionality.
Can you try disabling all other browser extensions and seeing if that fixes the problem?
I disabled all other extensions, but the issue persists. Logging out and clearing the cache does temporarily fix it, but the problem returns as soon as I log back in. This is kinda problematic because most features are tied to a premium account. So being logged in isn't really optional.