Google Chrome for Windows is a fast, capable web browser, but that doesn’t mean it’s perfect. Case in point: Chrome’s proclivity to slowdowns, crashes, and other unwanted behaviors as a result of third-party applications. It’s a serious problem, but Google’s working on fixing it.
In a post published Friday on the Chromium Blog, Google says that it found that roughly two-thirds of Chrome for Windows users use applications that interact with Chrome. In past, these applications needed to inject code in Chrome in order to work properly. The problem, according to Google, is that this form of code injection is 15 percent more likely to cause a crash.
Google’s proposes that instead of injecting code inside of Chrome processes, developers use Chrome extensions and Native Messaging. Soon, they won’t have a choice — starting with Chrome 68 in July 2018, Google will begin blocking third-party Windows applications from injecting code into Chrome on Windows.
Google says that the transition will happen in three phases: In April 2018, Chrome 66 will begin showing affected users a warning after a crash, alerting them to the presence of the code-injecting application. It’ll also show them how to update or remove that application.
The next phase will take place in July 2018, when Chrome 68 starts to block third-party code-injecting applications. Google says that if the offending applications prevent Chrome from starting, it’ll restart and allow the injection. However, it’ll display a warning showing users how to remove the application.
The final phase starts January 2019, when Chrome 72 begins blocking all code injections by default. (Google encourages developers to use Chrome Beta for testing.)
According to Google, most software that injects code into Chrome will be affected by these changes. Some exceptions include Microsoft-signed code, accessibility software, and IME software.
“Fewer crashes means more happy users, Chrome Stability Team member Chris Hamilton wrote in a blog post. “[We] look forward to continuing to make Chrome better for everyone.”
Source: Chromium Blog
from xda-developers http://ift.tt/2zFPEvW
via IFTTT
Aucun commentaire:
Enregistrer un commentaire