Constant disconnections continue even with the latest version of safari downloaded

It appears that whatever cloudflare issue chess.com has, the latest version of safari does not fix this. It's been going on for ~3 months now, how is this still not fixed? Every other game disconnects in the opening, once a day a game can't reconnect, matchmaking fails all the time. Why isn't this a priority?

Chess is a frustrating game as is, getting constant disadvantage and/or losses because a game disconnects 2 moves in feels beyond terrible

The issue was an implementation bug by Apple in the way the handle web sockets. It wasn't a site issue or caused by CloudFlare.

Are you sure you're on the version that has the bug addressed?

I wouldn't have posted the thread if I didn't manually install the safari update

And I'm sorry but "implementation bug by Apple" doesn't cut it when the issue persists for three months (?) now. It's insane that there's no attempt at fixing this. Every time I log in and hope the bug is finally fixed I get slapped with -8 elo. Put up a warning "Hey, there's a bug, it hasn't been fixed yet, we can't be bothered to fix this because technically we are not at fault". Anything is better than whatever chess.com is doing right now (nothing?)

https://www.chess.com/forum/view/help-support/mac-safari-26-0-conflict-with-chess-com?page=3#comment-120559434

It was an Apple bug fixed by their engineers.

Evidently it's not fixed. And I'm sorry but a chess.com rep going "yeah sorry not sorry not our fault" while the bug persists for over two months and seemingly nothing is done and the issue is not addressed in any meaningful way is a bad look. I've lost over 50 elo just this past week. It feels horrible. Anything I do in the game does not matter because in a bit all my progress will get annihilated by -8s I have no control over. And I have no way of knowing when/if it will get fixed since chess.com has no communication whatsoever

Other members have updated and are no longer seeing issues with games starting successfully. The big was one where the browser fundamentally broke a standard, only impacted a specific version of that browser, and specifically with a browser specific feature enabled. It's not a fix for Chess.com to make.