1.5.4.3

Changelog

• Added Korean translation (courtesy of @jjhitel)
• Fix for extensions not installing correctly on some browsers #145

1.5.4.2

Changelog

• Updated Turkish translation (courtesy of @Tmp341)
• Used MTL to translate all untranslated strings.

Known Bugs

• The "Add to Chrome" button will sometimes be disabled when navigating around the web store. If this happens you can refresh the page to fix it. (#135)

1.4.5

This version is ONLY for browsers which do not support Manifest V3

• Use at your own risk I haven't tested this at all.

1.5.4.1

Changelog

This is a test release of an alternative method of supporting the new chrome web store.

Known Bugs

• Will not always apply correctly when navigating between pages within the web store, if the "Add to Chrome" button is greyed out for you, try refreshing the page.
• No translations were added for the new option.

Technical details

Integration is achieved by modifying the window.chrome object on the CWS page, namely window.chrome.webstorePrivate and window.chrome.management. The web store uses these APIs to check which extensions you have installed and show the appropriate buttons. See chromeApi.js for a list of functions that were implemented, note that the local implementation doesn't always match the official version, for example chrome.management.getAll does not return all extensions but rather an array containing a single extension at most (the one whose page you are on). Because I can't reverse engineer the source of the chrome web store I can't be sure that data obtained from these methods isn't being sent back to Google. This should not be too worrying since even if that is the case the data they can access is limited to information about which extensions you have installed (a similar amount of data is transmitted whenever you check for updates with chromium-web-store) but if you are concerned I have added an option you can uncheck: Enable Chrome Web Store Integration

1.5.4

Changelog

• Support new web store page (#126)

1.5.3.1

Changelog

• Use updated icons #118

1.5.3

Changelog

• Add to Chromium context menu fallback now works in browsers which disallow scripting on the Chrome Web Store (includes Chrome and vanilla Chromium)

Manifest V3 migration issues (#76) have been mostly resolved so this will become a full release shortly.
If you experience issues please make sure you are using chromium v106.0.5240.0 or later.

1.5.2.2

Changelog

• Fix a bug causing failed extension updates to not affect the badge.
• Fix "Update All"

1.5.2

Changelog

• Now works correctly on Edge "collection" pages (#100)
• Fixed badge text color (#101)
• Fixed a bug that could cause non-CWS extension installs to fail (#103)
• Fix a variety of manifestv3 related bugs (from #76)

1.5.1

WARNING: Unless you need the new features or Manifest V3 support (or want to help with testing) I do not recommend you install this version.

Manifest V3 is currently very incomplete and as a result I have had to use several hacky workarounds to replicate some basic functionality available in Manifest V2, install at your own risk.

Changelog

• Update to Manifest V3
• Added an option to always download CRX files (for better compatibility with non-ungoogled browsers, should help avoid CRX_HEADER_INVALID and Apps, extensions and user scripts cannot be added from this website errors.)
• Change the way extensions are downloaded, which should streamline the update process in cases where setting #extension-mime-request-handling was not possible or not working.
• This version likely contains bugs; if you open an issue please specify that you are using the Manifest V3 version (or cws 1.5+)

If you are using the new Always download CRX files option (most likely because your browser does not support the #extension-mime-request-handling flag), do note that you can drag and drop extensions from the download bar directly into chrome://extensions to install them, even if they are in .zip format (see the video attached in #95).