The reason for this change is because of malicious Chrome developers who've abused this feature to trick users into installing confusing, deceptive, or downright malicious Chrome extensions.
That's what your entire comment is about. Your wall of text isn't because you're against the feature, it's because you're against the company adding the feature. You said in this comment that you...
I don't like Google
That's what your entire comment is about. Your wall of text isn't because you're against the feature, it's because you're against the company adding the feature. You said in this comment that you find it a good feature of Firefox. I don't believe you. Maybe you just don't understand what this change actually means.
This isn't stopping you from downloading/installing extensions outside of the Chrome Web Store, it's stopping websites from installing via links/external sites (especially redirects). You can still manually add extensions from outside.
This is similar to how it works in Android. You can't accidentally download an app unless you've gone into the hidden settings to tell the operating system you know what you're doing, this isn't much different than that.
None of this is really the matter at hand. All these extensions are already coming in through the Chrome Web Store. Chrome gimped the use of homebrew extensions and locked most people to their...
None of this is really the matter at hand. All these extensions are already coming in through the Chrome Web Store. Chrome gimped the use of homebrew extensions and locked most people to their store years ago.
This change doesn't do anything about where the extensions are coming from, it's just making people manually download extensions from their storepage instead of having people accept any offer that pops up.
it effectively censors extensions such as ad nauseum, since this extensions is already banned from the store for dubious reasons. I can understand it being used to protect against malicious...
it effectively censors extensions such as ad nauseum, since this extensions is already banned from the store for dubious reasons. I can understand it being used to protect against malicious extensions , but it can also be used to prevent people installing extensions that serve a purpose that runs counter to google's interests by making the installation an arduous task.
Here is the email I just got from google on the topic: Dear Chrome Extension Developer -- This week, we outlined on the Chromium blog our plans to retire the inline installation API for all Chrome...
Here is the email I just got from google on the topic:
Dear Chrome Extension Developer --
This week, we outlined on the Chromium blog our plans to retire the inline installation API for all Chrome Extensions. Users will need to go to the extension's Chrome Web Store page to complete an extension installation.
This change will roll out in three phases:
Extensions first published on June 12, 2018, or later that attempt to call the chrome.webstore.install() function will direct the user to the Chrome Web Store page in a new tab to complete the installation.
Starting September 12, 2018, inline installation will be disabled for existing extensions, and users will be directed to the Chrome Web Store to complete the installation.
In early December 2018, the inline install API method will be removed from Chrome 71.
If you distribute an extension using inline installation, you will need to update install buttons on your website to link to your extension's Chrome Web Store page prior to the stable release of Chrome 71 (by early December, 2018). If you haven't already, be sure to read up on how to create a compelling store listing, and consider using our install badge on your site.
We've also put together a technical FAQ to help you with the migration process.
For more information on this change, please refer to our Chromium blog post.
Good on Google!
That's what your entire comment is about. Your wall of text isn't because you're against the feature, it's because you're against the company adding the feature. You said in this comment that you find it a good feature of Firefox. I don't believe you. Maybe you just don't understand what this change actually means.
This isn't stopping you from downloading/installing extensions outside of the Chrome Web Store, it's stopping websites from installing via links/external sites (especially redirects). You can still manually add extensions from outside.
This is similar to how it works in Android. You can't accidentally download an app unless you've gone into the hidden settings to tell the operating system you know what you're doing, this isn't much different than that.
None of this is really the matter at hand. All these extensions are already coming in through the Chrome Web Store. Chrome gimped the use of homebrew extensions and locked most people to their store years ago.
This change doesn't do anything about where the extensions are coming from, it's just making people manually download extensions from their storepage instead of having people accept any offer that pops up.
it effectively censors extensions such as ad nauseum, since this extensions is already banned from the store for dubious reasons. I can understand it being used to protect against malicious extensions , but it can also be used to prevent people installing extensions that serve a purpose that runs counter to google's interests by making the installation an arduous task.
Thanks for posting this. Time to remove inline install from our webapp I guess.
Here is the email I just got from google on the topic:
Dear Chrome Extension Developer --
This week, we outlined on the Chromium blog our plans to retire the inline installation API for all Chrome Extensions. Users will need to go to the extension's Chrome Web Store page to complete an extension installation.
This change will roll out in three phases:
Extensions first published on June 12, 2018, or later that attempt to call the chrome.webstore.install() function will direct the user to the Chrome Web Store page in a new tab to complete the installation.
Starting September 12, 2018, inline installation will be disabled for existing extensions, and users will be directed to the Chrome Web Store to complete the installation.
In early December 2018, the inline install API method will be removed from Chrome 71.
If you distribute an extension using inline installation, you will need to update install buttons on your website to link to your extension's Chrome Web Store page prior to the stable release of Chrome 71 (by early December, 2018). If you haven't already, be sure to read up on how to create a compelling store listing, and consider using our install badge on your site.
We've also put together a technical FAQ to help you with the migration process.
For more information on this change, please refer to our Chromium blog post.
Regards,
The Chrome Web Store Team