Greasy Fork镜像

The ppixiv script seems to have stopped working for me.

I'm on Windows 11, chrome ver 130.0.6723.59, tampermonkey ver 5.3.1, ppixiv version 242.
I wouldn't be surprised if chrome's recent changes broke something.
I tried looking if there was any recent news on it but couldn't seem to find anything, so I'm posting here.

Tried reinstalling the script, no changes. Tried reinstalling tampermonkey, no changes. Tried it incongnito, no changes. Tried appending "#ppixiv", no changes. Cleared pixiv site data, no changes. Tried restarting my PC, no changes.
The ppixiv script seems to be considered running in tampermonkey when I am on pixiv. Though, when I open the dev console, it doesn't show any errors or any mention of the script.

Not sure what else it could be. Any help is much appreciated.

Yeah, it must be some change with Chrome.
Tried ppixiv on Firefox and it works just fine.
I did try it on Edge beforehand and it didn't seem to be working, but it's working now

Check if TamperMonkey is up to date, it looks like Chrome suddenly removed an event class that's been around for years, which broke many websites and extensions. It's working for me with tue cnrrent version of Chrome with TamperMonkey and ViolentMonkey.

5.3.1 seems to be the latest. I tried reinstalling TamperMonkey from the Chrome store and the Github.
Tried 5.3.6215 beta version, but no changes.

First time I've heard of ViolentMonkey, so I'll give that a try

Works with ViolentMonkey!
Though Chrome store says ViolentMonkey doesn't follow "best practices", so who knows if it'll break later

(Mind changing the "doesn't work"? It counts as a negative review.)

I think Google just doesn't like extensions that give people control over websites.

You should see "ppixiv is running in..." logged to the console if it's running at all, if you don't see that then there's something wrong earlier on. I was seeing an error that wasn't obviously caused by the script manager (it showed something like "VM1234" as the source line), but when I viewed the source it turned out to be TamperMonkey itself failing. So there might be errors in the log that are related but not obvious at a glance.

Ah, okie! Thanks for the quick responses!