{"id":123876,"date":"2025-04-30T21:05:07","date_gmt":"2025-04-30T19:05:10","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-web-brauzera-chrome-136-s-izolyacziej-stilya-prosmotrennyh-ssylok"},"modified":"2025-04-30T21:05:07","modified_gmt":"2025-04-30T19:05:10","slug":"vypusk-web-brauzera-chrome-136-s-izolyacziej-stilya-prosmotrennyh-ssylok","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-web-brauzera-chrome-136-s-izolyacziej-stilya-prosmotrennyh-ssylok","title":{"rendered":"Release of web browser Chrome 136 with isolation of viewed links style","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Google has released version 136 of the Chrome web browser. At the same time, a stable version of the free project Chromium, which forms the basis of Chrome, is available. Chrome differs from Chromium by the use of Google logos, a crash notification system, modules for playing copy-protected video content (DRM), automatic update installation, continuous Sandbox isolation, the inclusion of keys for the Google API, and the transmission of RLZ parameters during searches. For those who need more time to update, an Extended Stable branch is separately maintained, lasting 8 weeks. The next Chrome release, version 137, is scheduled for May 27. <\/p>\n
Main changes in Chrome 136: <\/p>\n
\n
Added protection against leaking information about previously visited pages caused by the CSS pseudo-class ':visited', which allows the styling of previously opened links. Up to Chrome version 136, clicking on a link would change the styling of that link across all sites displaying it, regardless of which site initiated the visit. On their own site, an attacker could determine whether a user had previously opened links of interest by analyzing the change in styling of those links. For example, if a list of links to different pages is created, previously visited pages in that list will be highlighted by the browser in a different color, allowing one to infer whether the links were opened before.\n
To block information leakage about visited links, Chrome has implemented isolation of the ':visited' selector's processing in relation to the viewed site, meaning that elements are now styled with ':visited' only if they were previously opened from the current site and within the current iframe. The isolation is achieved through hashing the style of visited links using a key made up of three components \u2014 the link, the top-level site, and the host used in the iframe.
<\/center> <\/p>\n
For example, if there was a transition from site 'A' through a link, this link will now only be highlighted on site 'A' and remain unchanged on the attacker's site. An exception is made only for iframes loaded from the main site (same-origin) and links to the current site. Thus, when opening site 'A', links leading to site 'A' will be highlighted even if the transitions to them were from another site, but other links will only be highlighted if the transitions were from site 'A'.
<\/center>
<\/center> <\/p>\n
In Firefox, protection against such leaks was introduced in 2010, but there were methods to bypass it. For instance, in 2024, Firefox 122 eliminated the possibility of analyzing pixel colors using filters that utilize the currentColor parameter and manipulations with the canvas tag in SVG. <\/p>\n
![\"Release](\"\/wp-content\/uploads\/2025\/04\/1b7c32185a1ed94d8970942e0f14d484.png\")
<\/center> <\/p>\n![\"Release](\"\/wp-content\/uploads\/2025\/04\/b38d06dfb9b49ed751e07f0f2ab9564a.png\")
<\/center> ![\"Release](\"\/wp-content\/uploads\/2025\/04\/e24121bf356c24439edcf641d14a834a.png\")
<\/center> <\/p>\n![\"Release](\"\/wp-content\/uploads\/2025\/04\/6fc5942fd8980c8478aa5b05ca16e21d.png\")
![\"Release](\"\/wp-content\/uploads\/2025\/04\/55250fe3582b32958aefab8cfe5d45dd.png\")
<\/center>\n