Your network blocks the Lichess assets!

lichess.org
Donate

Invisible rooks and knights on Firefox?

running firefox 143.0 64-bit on windows 11 pro build 26100.6584 on a dell laptop andam not facing issues

running firefox 143.0 64-bit on windows 11 pro build 26100.6584 on a dell laptop andam not facing issues

on fedora 43 plasma 6.4.4 and firefox 143.0.1 (flatpak) the board still empty.

on fedora 43 plasma 6.4.4 and firefox 143.0.1 (flatpak) the board still empty.

Happened again just now

143.0 (64-bit)

Windows 10 (64-bit)

Nvidia GTX Titan X

Happened again just now 143.0 (64-bit) Windows 10 (64-bit) Nvidia GTX Titan X

Some oponent pieces were invisible in my last bullet game.
143.0.1 (64-bit)
Windows 10 (64-bit)
Radeon RX 570 Series

Some oponent pieces were invisible in my last bullet game. 143.0.1 (64-bit) Windows 10 (64-bit) Radeon RX 570 Series

Just started a game playing as white all default settings for pieces and board. My rooks were invisible (graphic) but movable no problem. I just tried to keep track of where they were and the game played completely normally.

Firefox 143.0.1 (64-bit)
Windows 10 LTSB (64 bit)
GPU is a Radeon RX580 8GB

I tried a ctrl+F5 after having moved the rooks a few times and they remained invisible.

Thanks for your help.

Also, here is the output from my browser console in the game:

Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'unsafe-eval' 'nonce-l5bsHWFuDaK1RAmPzjPUw8ne' 'self' https://lichess1.org”. Consider using a hash ('sha256-ZswfTY7H35rbv8WC7NXBoiC7WNu86vSzCDChNWwZZDM=') or a nonce. utils.js:42:10

An AudioContext was prevented from starting automatically. It must be created or resumed after a user gesture on the page. site.QOYLW43W.js:4:9997

Lichess is open source! See https://lichess.org/source site.QOYLW43W.js:3:1183

The resource at “https://lichess1.org/assets/hashed/lichess.cd11aef7.woff2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. lnlIs2U1pN6J

The resource at “https://lichess1.org/assets/hashed/noto-sans-latin.086bfcad.woff2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. lnlIs2U1pN6J

The resource at “https://lichess1.org/assets/hashed/lichess-chess.02d5eb8f.woff2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. lnlIs2U1pN6J

The resource at “https://lichess1.org/assets/hashed/ic.87d2f16a.png” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. lnlIs2U1pN6J

And here is the output of lichess.org/#debug

Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0
Cores: 8, Touch: false 0, Screen: 1920x1080, Page lang: en-US, Browser lang: en-CA, Engine: null, Threads: null, Blindfold: false, Pieces: icpieces

Just started a game playing as white all default settings for pieces and board. My rooks were invisible (graphic) but movable no problem. I just tried to keep track of where they were and the game played completely normally. Firefox 143.0.1 (64-bit) Windows 10 LTSB (64 bit) GPU is a Radeon RX580 8GB I tried a ctrl+F5 after having moved the rooks a few times and they remained invisible. Thanks for your help. Also, here is the output from my browser console in the game: Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'unsafe-eval' 'nonce-l5bsHWFuDaK1RAmPzjPUw8ne' 'self' https://lichess1.org”. Consider using a hash ('sha256-ZswfTY7H35rbv8WC7NXBoiC7WNu86vSzCDChNWwZZDM=') or a nonce. utils.js:42:10 An AudioContext was prevented from starting automatically. It must be created or resumed after a user gesture on the page. site.QOYLW43W.js:4:9997 Lichess is open source! See https://lichess.org/source site.QOYLW43W.js:3:1183 The resource at “https://lichess1.org/assets/hashed/lichess.cd11aef7.woff2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. lnlIs2U1pN6J The resource at “https://lichess1.org/assets/hashed/noto-sans-latin.086bfcad.woff2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. lnlIs2U1pN6J The resource at “https://lichess1.org/assets/hashed/lichess-chess.02d5eb8f.woff2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. lnlIs2U1pN6J The resource at “https://lichess1.org/assets/hashed/ic.87d2f16a.png” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. lnlIs2U1pN6J And here is the output of lichess.org/#debug Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0 Cores: 8, Touch: false 0, Screen: 1920x1080, Page lang: en-US, Browser lang: en-CA, Engine: null, Threads: null, Blindfold: false, Pieces: icpieces

I did some more testing and found the resolution for my issue, hoping this helps anyone else or the devs to understand. On Firefox I had the "Privacy Badger" extension enabled. Once I disabled it for lichess, then ctrl+f5 to refresh and the rooks reappeared instantly.

I did some more testing and found the resolution for my issue, hoping this helps anyone else or the devs to understand. On Firefox I had the "Privacy Badger" extension enabled. Once I disabled it for lichess, then ctrl+f5 to refresh and the rooks reappeared instantly.

@HawkingFeynman said in #37:

Screenshot:
then why did you start the game? 2 rooks odds glitch!

@HawkingFeynman said in #37: > Screenshot: then why did you start the game? 2 rooks odds glitch!

Bruh it's just a 2000 ELO player, I won without rooks.

Bruh it's just a 2000 ELO player, I won without rooks.

@thibault Heyyy baby !! Fixed, now I can play using ff 143.0.1 flatpak :)

@thibault Heyyy baby !! Fixed, now I can play using ff 143.0.1 flatpak :)

This topic has been archived and can no longer be replied to.