... Hopefully the following indispensable Chrome extension
https://chrome.google.com/webstore/detail/get-crx/dijpllakibenlejkbajahncialkbdkjc
will continue to work as designed in the "ungoogled" flavours...
I use it routinely to manually download and archive .CRX files directly from CWS (not crx4chrome and similar... ), because my experience so far of using various 360EE variants in my Vista laptop has proved that any of my already installed extensions
a. may suddenly disappear completely from CWS, for various reasons...
b. be updated to a version not working correctly/at all with a specific 360EE version; this is often true for 360EEv11 (Chromium 69 based) and 360EEv12 (Chromium 78 based), but I expect to hit similar issues in the near future even for 360EEv13 (Chromium 86 based), because most Chrome extensions are developed/updated to target current Chrome (v92?) and declared backwards compatibility in CWS is often just a joke...
It's too late if I first update an extension but then discover it's broken, because CWS, unlike AMO, doesn't host previous version(s) of an extension...
Below is an excerpt of a previous edit (saved in an e-mail notification) of
https://msfn.org/board/topic/182993-360-extreme-explorer-arcticfoxie-versions/?tab=comments#comment-1205088
I've been mostly using the Russian RePacks of 360EE variants and while I was always able to add Chrome extensions directly from CWS, never have I observed one automatically update...
One can perform a simple test to verify:
Browse crx4chrome or similar third party Chrome extension archives, search there for and download the .CRX file of a previous version of an extension extant in CWS (all crx4chrome hosted files were originally retrieved from CWS) ; manually install by dropping the file on the Extensions tab (chrome://extensions/) ...
No matter how long you give it (hours, days, etc,), the extension won't be auto-updated to the latest version found inside CWS; often times, this is a blessing in disguise, because, despite CWS saying the opposite, the updated version won't "like" your version of 360EE (being sourced from an older Chromium codebase...).
However, in the event you do want to update an installed extension, again this is not straightforward ; visiting the CWS entry for the extension, you're only given a choice to "Remove from Chrome", not "Update Extension"; to "update", you have to actually first "remove", but this means losing all extension custom settings/modifications...
Several Chrome extensions offer the choice of backing-up settings/configuration prior to removal (with the option of importing back in a fresh installation), which makes updating them in 360EE somewhat less cumbersome...