I can't click setting, menu bar, etc

[comedyxtragedy]

I had the same problem with browser in my android phone. Forced to change into chrome, but the older chapter won't load fast 😔

 

[Teasday]

The problem seems to be ddosguard not sending Brotli encoded files only to browsers that support it, like they should. It's pretty weird that this would suddenly just start happening and with seemingly only specific files at that.

We changed a setting without turning the feature completely off yet. Let me know if the issue got any better, preferably after a hard refresh / cache reset.

 

[TimothySue]

Everything is still broken but, when using "www." in the url, the settings menu no longer looks weird.

 

[Teasday]

Welp I did a cache reset but hopefully things will work now again, after the initial 502s are dealt with

 

[Cyberbeing]

I can confirm. After clearing my browser cache, now both www.mangadex.org and mangadex.org seem ok. Dropdowns, Toggles, Settings all seem normal from testing so far. And I'm not seeing any more of those "SyntaxError: illegal character" on js files or the Unclosed String issue on the CSS in web console.

Interesting that Brotli encoding ended up being the root cause, since according to https://caniuse.com/#feat=brotli & https://hacks.mozilla.org/2015/11/better-than-gzip-compression-with-brotli/ it seems it should be support in some fashion in Firefox 45.9.0. Maybe it's something like the server was sending Brotli without declaring it as such in Content-Encoding, while modern Chrome/Firefox auto-detect it or something. Never checked that. Problem does seem resolved now though, so probably no use in further messing with things.

Edit: The Firefox dev blog article does mentions something like that. Responding with an unsupported content encoding, or with a header that doesn’t match the actual encoding of the content can lead to decompression errors which is exact symptoms I was seeing before when I mention in the other thread that js files were initially opening corrupted.

Edit2: Looking into it further, it seems this version of Firefox doesn't expose Brotli support by default after-all, and needs to be enabled explicitly by the user in about:config with network.http.accept-encoding & network.http.accept-encoding.secure by changing

gzip, deflate

to

gzip, deflate, br

. Who knows if there is some other issue which caused it not to be enabled by default though (edit: yep, tested it and Brotli doesn't work in Fx45.9 with Google). The other browsers affected by this without such configuration settings would be out of luck though, so not really a solution.

 

[Teasday]

@Cyberbeing The header was the expected

content-encoding: br

so if your browser couldn't decode it, Brotli support must have been turned off.

The strange part is that ddosguard should have served br or gzip based on browser support for it, but I guess something must have gone awry in the past week or two because this wasn't a problem before.