To improve performance and reduce crashes caused by third-party software on Windows, Google Chrome, by mid-2018, will no longer allow outside applications to run code within its web browser.

If you are unaware, many third-party applications, like accessibility or antivirus software, inject code into your web browser for gaining more control over your online activities in order to offer some additional features and function properly.

However, Google notes that over 15 percent of Chrome users running third-party applications on their Windows machines that inject code into their web browsers experience crashes—and trust me it’s really annoying.

But don’t you worry. Google now has a solution to this issue.

In a blog post published Thursday on Chromium Blog, Google announced its plan to block third-party software from injecting code into Chrome—and these changes will take place in three steps:

  1. April 2018 — With the release of Chrome 66, Google will begin informing users if code injection causes their browsers to crash, alerting them with the name of the responsible application and a guide to update or remove it.
  2. July 2018 — Chrome 68 will start blocking third-party software from injecting code into Chrome processes. But if this blocking prevents Chrome from starting, the browser will restart and allow the injection. But it will also display a warning for guiding users to remove that particular software.
  3. January 2019 — With no exception, starting with Chrome 72, Google will completely block code injection by any third-party software.

However, there will be some exceptions. Google Chrome will continue to allow Microsoft-signed code, accessibility software, and IME software to inject code into your browsers.

Today’s blog post is an advance notification for all developers out there, whose applications rely on code injection to function properly, forcing them to use either Native Messaging API calls or Chrome extensions to add functionality to the web browser.

“With Chrome extensions and Native Messaging, there are now modern alternatives to running code inside of Chrome processes,” Google said.

According to Google, both methods can be used by developers to retain their app features without having to risk browser crashes.

“Fewer crashes mean more happy users, and we look forward to continuing to make Chrome better for everyone,” Google said while summing up its blog post.

So, companies have almost 13 months to remove the code injecting bits from their software. Google is encouraging developers to use Chrome Beta channel and test their code, though these changes will more likely take effect in the Dev or Canary channels even sooner.

Now, what you are waiting for? Get ready to start rewriting your code.

LEAVE A REPLY

Please enter your comment!
Please enter your name here