MV3 Manifest v3 requires a different workflow when installing a userscript Note: you can restore the old behavior, by changing Userscript URL detection to Legacy
It is very annoying that you need developer mode now since my school chrombook has locked developer mode therefore making me unable to use tampermonkey
Do note that Developer Mode is really easy to turn on. It doesn’t mean using Chrome Dev. It just means that, after you install Tampermonkey, you’ll need to open your Extensions page and click the toggle at the top of the screen.
(訳) 開発者モードをオンにするのはとても簡単だということを知っておいてください。これは Chrome の Dev 版を使うという意味ではありません。Tampermonkey をインストールしたら、拡張機能のページを開いて、画面上部のトグルをクリックするだけです。
問題提起者
I know how to turn Dev mode on. But I am imagining how much pain would be to explain every user why my scripts aren’t working anymore.
There’re older women between them, to make script work for them I organized video-calls in messenger and ordered which buttons must be pressed.
You think only geeks are affected? Ones that can fix everything in a couple of minutes? No, the huge pain is coming because of some Chrome idiots.
In that case, I hope that Tampermonkey itself will tell people that they need to turn on Developer mode and how to do so. The extension won’t work without it, so it would make sense to warn the user every time the extension is loaded. I’m actually relieved that the requirement is so small. The MV3 people really wanted to not allow any external scripts to work at all. A simple toggle that you already have to enable to use unsigned extensions is thus a welcome compromise.
OK, I understand your point. Google forcing MV3 with all its totalitaristic claims, removing ad-blockers and all realized that it’s a bit too much and decided to reduce their appetites. And we all must be glad for this compromise. All hail to Google and MV3 for they decided to cook frog slowly to reduce protests and increase probability of success.
> In that case, I hope that Tampermonkey itself will tell people that they need to turn on Developer mode and how to do so.
Yes, there will by a notification when the action menu is open and also at the options page, which provides a link to the FAQ entry that explains how to enable it.
> A simple toggle that you already have to enable to use unsigned extensions is thus a welcome compromise.
Yes, but developer mode doesn’t seem to be the right one here as it also enables other developer features. Userscript manager users, are not necessarily developers. Also developer mode might be forbidden via policy at some companies.
So what is the state on this now? Nothing has happened for MONTHS. MV3 is basically here and we still don’t have a proper solution for userscripts. You really don’t give a shit, do you?
コメント