Keyconfig has been removed from the Chrome Web Store

このサイトを検索 | Search this site
,Japan


Google Chrome Extension Keyconfig for Google Chrome has been removed from the Chrome Web Store.

And, Keyconfig installed on the computer was removed at the time of version upgrade of Chrome.

It has been confirmed that some of the field extensions (extensions distributed outside of the Chrome Web Store) were loaded with malware and adware, and Google It is likely to be related to the way in which the extension installation has been tightened.

Inline installation API

Since distribution of poor-quality non-functional extensions results in a decline in Chrome's reputation, Google has changed to a specification to remove the inline installation API from Chrome 71.

As a result, the extension installation is limited to the Chrome Web Store.

At the same time, extensions that Google deems inappropriate are popularly deleted such as Keyconfig, without hesitation.

The Keyconfig has been removed from the Chrome Web Store, but it can still work if you have backed up the source code before compiling (.crx).

This article contains information about Chrome's "Load Unpackaged Extensions" feature, which is the last step to getting Keyconfig removed from the Chrome Web Store.


Load an unpackaged extension

To make the Keyconfig script work, enable Chrome's Developer Mode and use the "Load Unpackaged Extensions" feature.

How to load extensions before packaging
Chrome> Settings> Other Tools> Extensions: Enable Developer Mode> Import Unpackaged Extensions

However ...

It is possible to make Keyconfig work, but as a trade-off every time you start Chrome you will be prompted to disable the field extension.

Transcription
Disable developer mode extensions

"An extension running in developer mode can damage your computer. If you are not a developer, please disable these extensions running in developer mode for safety."

The extension of os0x has disappeared

The developer of Keyconfig is os0x, but has announced several other enhancements.

The following extensions developed by os0x are completely BANed, so did you pay attention to Google?
  • ChromeGestures: Mouse Gesture Extension
  • ChromeKeyconfig: Shortcut Key Customization Extension
  • AutoPatchWork: Enhancement equivalent to AutoPagerize

There is still an os0x GitHub site, so if you really want to use Keyconfig you can get the source code from GitHub.

Please refer to the external link at the end of the sentence for the link.

Afterword

As I said at the beginning, although Chrome's inline installation API has been abolished, it is no longer possible to make bad expansion impossible, but extensions that have passed Google's review will be uploaded to the Chrome Web Store There is still the possibility that certain extensions will pass the review.

It was thought that it would be impossible to load unpackaged extensions if the inline installation API was discontinued, but for now it's still fine.

Keyconfig was a very easy-to-use extension, but if you combine various extensions you can get the functionality that Keyconfig has realized, so how about looking for an extension that suits you?

I think that the possibility that Keyconfig will come back suddenly is not zero, so if you can not give up, bookmark the URL when it was alive.


SC2
ブログサークルSNS
クリックして応援してね!
人気ブログランキングPVアクセスランキング にほんブログ村ブログランキング・にほんブログ村へ

このサイトを検索 | Search this site

コメントを投稿

0 コメント