NotHereToPlayGames Posted September 11, 2024 Posted September 11, 2024 (edited) 3 hours ago, Saxon said: I removed/disabled Webstore from/in the pak data (with precise instructions by D.Draker), yet I still see this, too. Ideas? I guess I would have to have a copy of "your version" to really be able to answer that. Edited September 11, 2024 by NotHereToPlayGames
Saxon Posted September 11, 2024 Posted September 11, 2024 23 hours ago, NotHereToPlayGames said: I guess I would have to have a copy of "your version" to really be able to answer that. The extension, including its manifest, was completely removed. I can't add since it exceeds the allowed attachment, sorry.
NotHereToPlayGames Posted September 11, 2024 Posted September 11, 2024 You'd have to upload it somewhere and post the link. In a PM if you prefer.
VistaLover Posted January 5 Posted January 5 3 hours ago, Dave-H said: Off-topic, but I can't get violentmonkey to work in 360Chrome 13.5. It apparently installs fine, but does not actually work. The installed scripts do nothing. Hi Dave, Happy New Year ! It's been a long while since I last launched my 360EEv13.x copies, but your post made me test things on my side; I seem unable to confirm nor reproduce your findings here ; in a quasi-fresh profile of v13.5.1022.0 I installed the latest BETA version of the Violentmonkey extension from the CWS, https://chrome.google.com/webstore/detail/violentmonkey-beta/opokoaglpekkimldnlggpoagmjegichg The "new" CWS is incompatible with Cr86, so I first downloaded the .CRX file of the extension via "Supermium+Get CRX" extension... As you wrote, VM-2.29.1b installed fine; I then imported a scripts+settings back-up I had previously exported from my VM installation under KafanMiniBrowser (Cr87-based); that backup was imported successfully in the 360EEv13.5 browser; all installed scripts were loaded without errors and upon checking them on the associated webpages, I verified they work as intended... I have many userscripts installed but, as two examples for you, below is the userscript https://github.com/Procyon-b/GitHub-sort-by-recently/blob/master/userscript.user.js working on the VM GH repo page (the script, unfortunately, ONLY works when NOT being logged-in to GH): and further down is the userscript https://greasyfork.org/scripts/479807-chrome-new-webstore-make-available-for-all-web-browsers-which-support-it working on the "new CWS" webpage for VM BETA: There have been many rebuilds of the 360EEv13.x browsers , unsure which flavour you're using yourself; TBH, since both 13.0 and 13.5 use the same Cr86 core, I never did bother myself with 13.5 and stuck, at that time, to a v13.0 (Russian) mod; roytam1's Serpent 52 was serving me well at that period, 360EEv13 was ONLY used by me for some Chromium-specific webpages... It's really sad that now both 360EEv13.x and St52 are inadequate for the sites I use (e.g. GitHub), so latest Supermium it has to be for me, mainly ; but when I was using 360EEv13, I had no issues with the Violentmonkey extension... Please try to troubleshoot with a fresh 13.5 profile; and try to familiarise yourself with all the VM settings; take extra care to leave the "script injection mode" to its default setting, i.e. "auto"... Cheers ... 1
NotHereToPlayGames Posted January 5 Posted January 5 @VistaLover - I'd be interested in the Promise.withResolvers() (first implemented with Chrome v119) polyfill code.
Dave-H Posted January 5 Posted January 5 15 hours ago, VistaLover said: Hi Dave, Happy New Year ! It's been a long while since I last launched my 360EEv13.x copies, but your post made me test things on my side; I seem unable to confirm nor reproduce your findings here ; in a quasi-fresh profile of v13.5.1022.0 I installed the latest BETA version of the Violentmonkey extension from the CWS, https://chrome.google.com/webstore/detail/violentmonkey-beta/opokoaglpekkimldnlggpoagmjegichg The "new" CWS is incompatible with Cr86, so I first downloaded the .CRX file of the extension via "Supermium+Get CRX" extension... As you wrote, VM-2.29.1b installed fine; I then imported a scripts+settings back-up I had previously exported from my VM installation under KafanMiniBrowser (Cr87-based); that backup was imported successfully in the 360EEv13.5 browser; all installed scripts were loaded without errors and upon checking them on the associated webpages, I verified they work as intended... I have many userscripts installed but, as two examples for you, below is the userscript https://github.com/Procyon-b/GitHub-sort-by-recently/blob/master/userscript.user.js working on the VM GH repo page (the script, unfortunately, ONLY works when NOT being logged-in to GH): and further down is the userscript https://greasyfork.org/scripts/479807-chrome-new-webstore-make-available-for-all-web-browsers-which-support-it working on the "new CWS" webpage for VM BETA: There have been many rebuilds of the 360EEv13.x browsers , unsure which flavour you're using yourself; TBH, since both 13.0 and 13.5 use the same Cr86 core, I never did bother myself with 13.5 and stuck, at that time, to a v13.0 (Russian) mod; roytam1's Serpent 52 was serving me well at that period, 360EEv13 was ONLY used by me for some Chromium-specific webpages... It's really sad that now both 360EEv13.x and St52 are inadequate for the sites I use (e.g. GitHub), so latest Supermium it has to be for me, mainly ; but when I was using 360EEv13, I had no issues with the Violentmonkey extension... Please try to troubleshoot with a fresh 13.5 profile; and try to familiarise yourself with all the VM settings; take extra care to leave the "script injection mode" to its default setting, i.e. "auto"... Cheers ... Thanks for replying in the right thread @VistaLover! I've just tried this again, this time downloading the CRX file using the Get CRX extension as you did. I used the release version rather than the beta though. Still the same result, everything seems to install OK, the scripts all imported OK and show no errors, but the Violentmonkey icon remains stubbornly grey, and the scripts don't actually do anything. As you can see, I keep getting 'Violentmonkey was restarted. Please reload the tab to run userscripts'. Reloading the tab does not change this. I'm using 360Chrome 13.5.2036.0. Orangemonkey 1.09 still works, but I get constant nags popping up saying it's about to be unsupported, which it is of course! The new version, Orangemonkey Pro, does not work with Chromium 86 of course!
NotHereToPlayGames Posted January 5 Posted January 5 I am unable to replicate. Violentmonkey and scripts install and execute just fine for me in 360Chrome v13.5.1030 ungoogled, v13.5.2036 ungoogled, and in v13.5.2036 regular. Both in XP and in 10. The only thing I did during my testing which seems different from your testing is that I did not "import" scripts. I installed "new" because I had nothing to import at the time. So I just ran some greasyfork font scripts just for testing. Everything worked as expected. 1
VistaLover Posted January 5 Posted January 5 12 hours ago, NotHereToPlayGames said: I'd be interested in the Promise.withResolvers() (first implemented with Chrome v119) polyfill code. ... Can't remember where I snitched this from or where to test its correct functionality, but here you go : // ==UserScript== // @name Inject Promise.withResolvers() Polyfill [119] // @version 0.0.1 // @match *://*/* // @run-at document-start // @grant none // ==/UserScript== Promise.withResolvers || (Promise.withResolvers = function withResolvers() { var a, b, c = new this(function (resolve, reject) { a = resolve; b = reject; }); return {resolve: a, reject: b, promise: c}; }); 1
Dave-H Posted January 5 Posted January 5 37 minutes ago, NotHereToPlayGames said: I am unable to replicate. Violentmonkey and scripts install and execute just fine for me in 360Chrome v13.5.1030 ungoogled, v13.5.2036 ungoogled, and in v13.5.2036 regular. Both in XP and in 10. The only thing I did during my testing which seems different from your testing is that I did not "import" scripts. I installed "new" because I had nothing to import at the time. So I just ran some greasyfork font scripts just for testing. Everything worked as expected. The strange thing is that exactly the same thing happened when I tried Tampermonkey Legacy 5.1.1. Everything looked fine, but didn't actually work! In both cases, I simply imported the saved scripts zip file that I had exported from Orangemonkey, but of course there could be a compatibility issue there. I'm pretty sure that I did also try importing a script into Violentmonkey directly from the script file, and that didn't work either, but I will try that again.
VistaLover Posted January 5 Posted January 5 (edited) 35 minutes ago, Dave-H said: but I will try that again. ... First do as instructed: 19 hours ago, VistaLover said: Please try to troubleshoot with a fresh 13.5 profile; If you're using one of the "portable" (with X-Loader) distributions, it's quite easy to back-up your current profile (dir "USER DATA") and restore it when testing is over; also back-up your loader config file (360Loader.ini), if custom-modified, and use the stock version for testing; on the fresh profile, install just VM (stable or BETA), install some userscripts and test their correct functioning; if they do work as designed, then your predicament in your dirty profile is due to a) a custom browser setting, b) a custom chrome://flags/, c) a custom cmdline switch defined inside 360Loader.ini (under "Parameters"), d) an interaction with one of the rest of the installed extensions, e) something else I can't think off-the-top-of-my-head ... 4 hours ago, Dave-H said: Orangemonkey 1.09 still works, but I get constant nags popping up saying it's about to be unsupported, which it is of course! The new version, Orangemonkey Pro, does not work with Chromium 86 of course! Almost all Web Extensions targeting Google Chrome will have to migrate, eventually, to MV3, which by itself requires Chrome 88+, and this is just for the simplest of extensions; many require even higher Chrome versions, because the needed MV3 APIs were introduced well after v88... Violentmonkey will also have to migrate, there's an open GH issue about it: https://github.com/violentmonkey/violentmonkey/issues/1934 Thus, if you need to keep using 360EEv13.x, you'd have to freeze extensions to their last MV2 iteration... PS: I inadvertently submitted this post before its conclusion, so your copy delivered through e-mail notification will have ended abruptly; apologies ... Edited January 5 by VistaLover Finishing post 1
Dave-H Posted January 5 Posted January 5 Just to say that I tried using the scripts which Violentmonkey said were designed for the site I was on (in this case Facebook). I installed a couple of them, using the Violentmonkey interface only, and they again apparently installed fine, but didn't work. So, whatever the problem is, it's presumably nothing to do with the scripts themselves or the way that they're being imported. I will try with a new clean 360Chrome profile. The easiest way I can think of to do that is to disable the current user profile folder by re-naming it, and then running the browser, and it should generate a clean new one. If the problem is still there, I will check the flags in the loader.ini file, which are - --user-data-dir="%Profile%" --no-default-browser-check --disable-component-update --disable-background-networking --allow-outdated-plugins --cipher-suite-blacklist=0xcc14,0xe013 --ignore-certificate-errors --user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36" 1
VistaLover Posted January 6 Posted January 6 (edited) ... OK @Dave-H, I think I have solved this difficult riddle of yours, so I'd kindly ask for "preferential treatment" for the rest of the year ; joking aside, I bet you 100 quid you have toggled the following pref chrome://flags/#enable-experimental-web-platform-features to "Enabled", to squeeze more out of the old Chromium 86 JS+CSS engine, have you not? On an epiphany (pun intended, it's already Jan 6th here), I remembered a discussion inside the Supermium issue tracker, where Client Hints was the topic... The aforementioned pref, in versions of Chrome ranging in the mid-to-late 80s, enables an alpha/gestational form of the CH API, which was only finalised in the early-to-mid 90s (and sometime after Cr87 it was put behind its own flag, decoupled from experimental-web-platform-features) ... If you visit https://browserleaks.com/client-hints do you get under "Client Hints JavaScript API: API Support" -> True ? If yes, that's the origin of your VM issue; I can replicate your 360EEv13.5 VM issue myself if I do enable that pref ("Disabled" in a fresh/default profile), please see below: The behaviour you're experiencing is caused by Violentmonkey (and Tampermonkey ?) code but in defence of the VM maintainers, they couldn't possibly author code to cover ALL cases of users messing with the "you're-not-supposed-to-touch" Chrome's "Experiments", aka "chrome://flags/"; more so, when they're currently supporting Cr 61-131 (and each of those has its own, unique, set of "Experiments") ... Technical stuff: The culprit commit is the one below: https://github.com/violentmonkey/violentmonkey/commit/d2dda25d91e3718e5b20ba4648e82baf730e6178 from May 2024; this one assumes the browser comes equipped with the final iteration of the Client Hints API, which isn't true for Cr86/87; no CH API (the default in Cr86/87) doesn't break VM >= 2.19.1, but a draft/RC CH API does ... Mitigations: If you want to install and use the latest version of VM in 360EEv13.x (Cr86), you'd have to a) disable/never enable "chrome://flags/#enable-experimental-web-platform-features"; this will reduce, somewhat, web compatibility with certain sites that expect recent Chromium-based web engines... b) if you opt to enable "chrome://flags/#enable-experimental-web-platform-features" for webcompat purposes, then you should disable Cr86's draft CH API via the cmdline switch: " --disable-features=UserAgentClientHint" (e.g., add that to loader's "Parameters"); some recent websites which rely on sniffing UA CHs may break... If the website of interest remains functional ONLY when detecting some Client Hints (e.g., some sites "take you for a bot" and outright block you when no CHs are sent), then you'd have to enable "chrome://flags/#enable-experimental-web-platform-features" in 360EEv13.x but opt for an older version of VM, one < 2.19.1 (crx4chrome should afford those...). Well, that's it ; detective work concluded successfully: case filed! Best wishes ... Edited January 6 by VistaLover 4
NotHereToPlayGames Posted January 6 Posted January 6 (edited) 6 hours ago, VistaLover said: I bet you 100 quid you have toggled the following pref chrome://flags/#enable-experimental-web-platform-features to "Enabled" Eureka! I did not originallyhave this toggled to Enabled, but doing so definitely broke Violentmonkey's ability to inject scripts! I only tried most-recent stable (non-beta) version. It does not break Tamerpermonkey's v4.13 ability to inject scripts (only tried that version because that was already present in the 360Chrome profile). Tampermonkey's most-recent stable (non-beta) version does not work (reducing min-ver in manifest will get it to install, but the GUI will not load). That's where I stopped for now... I personally PREFER Tampermonkey over Violentmonkey but BOTH are equally GREAT and only a matter of PERSONAL PREFERENCE. If the OP wants to isolate how "old" of a Tampermonkey version he must go and still be able to use the "experimental-web-platform-features", I don't mind hunting that down. We do know that version 4.13 does work! Technically, I've never had any use for any version newer but cannot recall offhand "why" I opted for v4.13. t is VERY common for me to test tons of extension versions and hand-select the version I *keep*. Which is not always "latest and greatest" but the actual "why" will vary greatly from one extension to the next. Edited January 6 by NotHereToPlayGames
Dave-H Posted January 6 Posted January 6 Thank you so much @VistaLover, that has indeed worked! I changed the flag, and I will see if that causes any other problems, in which case I will follow your other suggestions. Strange that both Violentmonkey and Tampermonkey showed this issue, but not Orangemonkey. 1
VistaLover Posted January 6 Posted January 6 (edited) 17 hours ago, NotHereToPlayGames said: Tampermonkey's most-recent stable (non-beta) version does not work (reducing min-ver in manifest will get it to install, but the GUI will not load). https://chromewebstore.google.com/detail/tampermonkey/dhdgffkkebhmkfjojejmpbldmpobfkfo v5.3.3 is of the MV3 type and requires APIs found on Cr120+ : "manifest_version": 3, "minimum_chrome_version": "120", 17 hours ago, NotHereToPlayGames said: We do know that version 4.13 does work! Technically, I've never had any use for any version newer but cannot recall offhand "why" I opted for v4.13. I looked at my own archives, where I had noted down that the last MV2 version of (stable) TM is v5.1.1 (requires Cr71+); the last TM BETA version in MV2 "manifest format" was v5.1.6194 (again, Cr71+); both can be acquired from crx4chrome ; NB: You'd have to use a more recent browser to get these, though, because crx4chrome has put self-hosted files behind a CF check that Cr86 is unable to pass ... Addition: The last MV2 stable version (5.1.1) of TM has been re-uploaded to CWS under a new name/extension-id: https://chromewebstore.google.com/detail/tampermonkey-legacy/lcmhijbkigalmkeommnijlpobloojgfn From cursory testing, both TM-5.1.1 and TMb-5.1.6194 seem to install and function properly under 360EEv13.5, even when "chrome://flags/#enable-experimental-web-platform-features" has been user-enabled (so definitely a plus compared to latest VM version): On 1/6/2025 at 1:12 AM, Dave-H said: The strange thing is that exactly the same thing happened when I tried Tampermonkey Legacy 5.1.1 7 hours ago, Dave-H said: Strange that both Violentmonkey and Tampermonkey showed this issue I couldn't reproduce , this is another riddle of yours I'm not willing to dive into (perhaps TM-5.1.1 is broken on your "dirty" profile because of something else? ) ... Cheers ... Edited January 7 by VistaLover typos
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now