The developers of the corresponding software now have until the coming summer to change their applications. Then, further measures should prevent external codes from simply locking into the browser. There are already alternatives to such an approach. For example, external applications can use the interfaces provided for plug-ins – or the native messaging API.
A first step to end the current state Google will go in the spring: When the version 66 of the browser is published in April, there is a more concrete information of the user. In the event of a crash, he is then told that it is not the browser itself but external software that is responsible for the problem. Here a removal of the software is recommended.
In July, the Chrome 68 will then prevent the entry of the codes – but only if this does not hinder the launch of the browser itself. In case of doubt, the external software will then proceed as usual. Google wants to introduce a complete blockade only a few months later with the version 72, which should appear in January 2019.