Recent content by jdjohndoe13

A new Nagatoro chapter came out few hours ago. I've been reading comments section there and had this vague feeling like something is ju-u-ust a bit out of focus. Oh, so annoying! Then a notification about a new Kanojo, Okarishimasu chapter came out. I rushed to the comments section here and was...

@marvinsod Oh right. I did think about that option before I got to computer to write the comment, but, apparently, forgot. It really looks like the author left a lot of plausible cockblocks all over the place.

@aftp4 He won't. He had plans for the Christmas, so he'll only find out that Sakurai is his sister's boyfriend much later in the future.

Tags #tragedy, #gore when?

What will happen next chapter? Place your bets: They will be interrupted by the lizard (it's still on the wall). They will be interrupted by Hiro's growling stomach (it growled earlier). They will be interrupted by the hotel worker who brought them some snacks (as a one year anniversary gift)...

@Degritone Did you try the same thing with TamperMonkey instead of GreaseMonkey? I'm not sure that GreaseMonkey understands TamperMonkey's script format. I've checked it on fresh Firefox 56.0.2 portable: installed TamperMonkey, added script, opened manga - it works. Not sure if you can have both...

@Degritone OS version? Browser version? What's the error in console?

@DrMuhammad Sorry, no experience. But since Then maybe there is something different when you start it in "normal" mode? I'd recommend reinstalling Chrome (i.e. uninstall, reboot the device, install it again), and, if that doesn't help, look up how to reset Chrome settings or emulate fresh...

@zx4 The statistics was requested. It's up to admins to decide whether they want to publish it or not. The solution for old version of Firefox is available. Another user (theo1996) has just confirmed that it works even for Firefox 48. Right now I think there is no point to sit in one's hands and...

@zx4 They don't even know that these users exist. They wrote it previously:

@theo1996 I created a new folder. Opened console. Ran command Went inside subfolder node_modules\abortcontroller-polyfill\dist Copied the contents of the file abortcontroller-polyfill-only.js. There was no "dist" folder in GitHub repository (or I couldn't find it), and I didn't want to build...

But... what's wrong adding shims and polyfills for old clients? It doesn't break the functionality for modern clients, it doesn't bloat the JavaScript too much, and you can download the polyfill only if you detect that it's needed... Yes, you have to write an extra few lines of code, but...

@theo1996 did you try the solution for old Firefox?

@Grimwear, @crazybars, @Anthony, @DarkFenix, @Cinsyac, @maindish, @jhs_reika OK, found the solution for Firefox version 56 and older: install AbortController polyfill manually for your browser only via TaperMonkey add-on. Step-by-step instruction: Download and install TamperMonkey version...

@DarkFenix and other users with Firefox 56 or older: moderator has already told us: So... yeah. Use another browser to view MangaDex from now on. You can download a portable version of Firefox or Google Chrome and keep it specifically for MangaDex.