Site isolation enabled by default in Chrome 67



[ad_1]

If Google links it to the mitigation of the Specter-type attacks, this feature has been in the works for a long time, as we mentioned at the beginning of December.

The first works on the subject date back to 2015, and the first tests The idea is to have a better separation of elements within a page, which is not without causing some problems.

This is particularly the case for memory consumption, which can rise from 10 to 20% depending on the case. The arrival of Specter will probably have accelerated the process and motivated the teams to put this aspect aside.

After tests on a portion of users in Chrome 66, the version 67 generalizes the process to 99% of between them, the remaining 1% to continue to improve the device. The next step is the mobile, where nothing like that is in place.

Chrome 68 will open the door to manual activation, before probably a generalization there too a few months later if all goes well. [19659006] [ad_2]
Source link