{"id":88912,"date":"2020-07-16T07:42:12","date_gmt":"2020-07-16T05:42:12","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/reliz-chrome-84"},"modified":"2020-07-16T07:42:12","modified_gmt":"2020-07-16T05:42:12","slug":"reliz-chrome-84","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-chrome-84","title":{"rendered":"Chrome 84 Release","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Google Inc. <noindex><a rel=\"nofollow\" href=\"https:\/\/support.google.com\/chrome\/a\/answer\/7679408#84\">introduced<\/a><\/noindex> release of the web browser <noindex><a rel=\"nofollow\" href=\"http:\/\/www.google.com\/chrome\">Chrome 84<\/a><\/noindex>. At the same time, <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromium.org\/developers\/calendar\">is available<\/a><\/noindex> the stable release of the open-source project <noindex><a rel=\"nofollow\" href=\"http:\/\/dev.chromium.org\/\">Chromium<\/a><\/noindex>, which serves as the foundation for Chrome. The Chrome browser <noindex><a rel=\"nofollow\" href=\"https:\/\/code.google.com\/p\/chromium\/wiki\/ChromiumBrowserVsGoogleChrome\">differs<\/a><\/noindex> features the use of Google logos, a crash notification system, the ability to load Flash plugins on demand, modules for playing protected video content (DRM), an automatic update installation system, and the transmission of RLZ parameters during searches. <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=26822\">. The next release of Chrome 80 is scheduled for February 4.<\/a><\/noindex>. The next release of Chrome 85 is scheduled for August 25.<\/p>\n<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/support.google.com\/chrome\/a\/answer\/7679408#84\">Key<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/productforums.google.com\/forum\/#!forum\/chrome\">changes<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.chromium.org\/2020\/05\/chrome-84-beta-web-otp-web-animations.html\">downward API support (simultaneously with this in<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/2020\/\">Activated<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/v8.dev\/blog\/v8-release-84\">84<\/a><\/noindex>:<\/p>\n<ul>\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=51599\">support for inactive<\/a><\/noindex>  support for TLS 1.0 and TLS 1.1. To access sites over a secure connection, the server must support at least TLS 1.2; otherwise, the browser will now display an error. According to Google, currently about 0.5% of web page requests are still made using outdated versions of TLS. The shutdown is in accordance with <noindex><a rel=\"nofollow\" href=\"https:\/\/datatracker.ietf.org\/doc\/draft-ietf-tls-oldversions-deprecate\/\">recommendations<\/a><\/noindex>  IETF (Internet Engineering Task Force). The reason for discontinuing TLS 1.0\/1.1 is the lack of support for modern ciphers (such as ECDHE and AEAD) and the requirement to support older ciphers, the reliability of which is now questioned in the current stage of computing (e.g., they require support for TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA, and MD5 and SHA-1 are used for integrity and authentication). The setting that allows reverting to TLS 1.0\/1.1 will be retained until January 2021.\n<li class=\"l\"> Blocking is ensured <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=52329\">unsafe downloads<\/a><\/noindex> (unencrypted) of executable files and added warnings for unsafe archive downloads. In the future, support for downloading files without encryption is planned to be gradually discontinued. The blocking was implemented because downloading files without encryption can be used for malicious actions by substituting content during MITM attacks.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5995832180473856\">Added<\/a><\/noindex> initial support <noindex><a rel=\"nofollow\" href=\"https:\/\/wicg.github.io\/client-hints-infrastructure\/\">identifier<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/httpwg.org\/http-extensions\/client-hints.html\">Client Hints<\/a><\/noindex>, developed as an alternative to the User-Agent header. The Client Hints mechanism offers a series of headers, \"Sec-CH-UA-*\", as a replacement for the User-Agent, allowing selective data delivery regarding specific browser and system parameters (version, platform, etc.) only upon request from the server. Users have the ability to specify which parameters are permissible for delivery and selectively provide such information to website owners. When using Client Hints, the identifier is not transmitted by default without an explicit request, making passive identification impossible (by default, only the browser name is indicated). <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5704553745874944\">Work<\/a><\/noindex> by <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=52182\">unification of the User-Agent<\/a><\/noindex> <noindex><a rel=\"nofollow\" href=\"https:\/\/groups.google.com\/a\/chromium.org\/forum\/m\/#!msg\/blink-dev\/-2JIRNMWJ7s\/yHe4tQNLCgAJ\">postponed<\/a><\/noindex> until next year.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromium.org\/updates\/same-site\">Continued<\/a><\/noindex> activation<br \/>\nstricter <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=52189\">restrictions<\/a><\/noindex> on Cookie transmission between sites, which had been <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.chromium.org\/2020\/05\/resuming-samesite-cookie-changes-in-july.html\">canceled<\/a><\/noindex> Due to COVID-19, the processing of third-party cookies set when accessing sites different from the current page's domain is prohibited for non-HTTPS requests. Such cookies are used to track user movements across sites in advertising networks, social media widgets, and web analytics systems. <\/p>\n<p>It is worth noting that the SameSite attribute, specified in the Set-Cookie header for managing Cookie transmission, will default to \"SameSite=Lax\", which restricts the sending of Cookies for cross-site subrequests, such as image requests or content loading via iframe from another site. Sites can override the default SameSite mode by explicitly setting the SameSite value to None when installing Cookies. Moreover, the SameSite=None value for Cookies can only be set in Secure mode (applicable for connections over HTTPS). The change will be applied gradually, initially to a small percentage of users and then progressively expanding the coverage.<\/p>\n<li class=\"l\"> An experimental implementation has been added <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=52957\">of a resource-intensive ad blocker<\/a><\/noindex>, which can be activated by adjusting the setting \"chrome:\/\/flags\/#enable-heavy-ad-intervention\". This blocker automatically disables advertising iframe blocks after exceeding threshold values of traffic and CPU load. The blocking will occur if over 60 seconds of CPU time is spent in the main thread in total or 15 seconds within a 30-second interval (utilizing 50% of resources for over 30 seconds), as well as when more than 4 MB of data is loaded over the network.\n<p>Blocking will only occur if the user has not interacted with the ad block (for example, has not clicked on it) before exceeding the limits, which, considering traffic restrictions, will allow blocking the autoplay of large video ads without explicit user activation. The proposed measures will free users from ads with inefficient code implementation or intentional parasitic activity (such as those performing mining). According to Google statistics, the ads falling under the blocking criteria make up only 0.30% of all ad blocks, but these ads consume 28% of CPU resources and 27% of traffic from the total ad volume. <\/p>\n<li class=\"l\"> Work has been done to reduce CPU resource consumption when the browser window is not visible to the user. Chrome now checks if the browser window is being overlapped by other windows and excludes pixel rendering in overlapping areas. The rollout of this new feature will be gradual: optimization will be enabled for some users in Chrome 84, and for the rest in Chrome 85.\n<li class=\"l\"> Enabled by default is protection against <noindex><a rel=\"nofollow\" href=\"https:\/\/support.google.com\/webtools\/answer\/9799829\">annoying notifications<\/a><\/noindex>, such as spam requests for push notifications. Since such requests interrupt user tasks and distract attention to confirmation dialog actions, instead of a separate dialog, an informational tooltip will be displayed in the address bar that does not require user action, warning about blocking the authority request, which automatically collapses into an indicator with a strikethrough bell icon. By clicking on the indicator, the requested permission can be activated or declined at any convenient moment.\n<\/p>\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/lh6.googleusercontent.com\/pM2hu9foX9242Vc4AOuz_ntSYy50F_Lb_61o7-s-cCGT4l8sS08fO40JHdKM-6q0afoRqZmOE1dXwJI5kPNs-kwB_KJPosvLLqklNQN4yren24JCG67MwY926uM4IU7vuqV4JqeU\"><img decoding=\"async\" alt=\"Chrome 84 Release\" src=\"\/wp-content\/uploads\/2020\/07\/b327d04760987f54372a2ff4d057eb2e.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> User selection is remembered when opening external protocol handlers \u2014 users can choose \"always allow for this site\" for a specific handler, and the browser will remember this decision in relation to the current site.\n<li class=\"l\"> Protection against changing user settings without explicit consent has been added. If an extension changes the default search engine or the page displayed for a new tab, the browser will now show a dialog asking to confirm the specified action or cancel the change.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/4926989725073408\">Continued<\/a><\/noindex> implementation of protection against loading mixed multimedia content (when resources are loaded via http:\/\/ on an HTTPS page). On pages opened via HTTPS, links to 'http:\/\/' will now be automatically replaced with 'https:\/\/' in blocks related to image loading (previously, scripts and iframes were replaced, and auto-replacement of audio and video resources is expected in the next release). If an image is not available via https, its loading is blocked (manual unblocking can be marked through the menu accessible via the lock symbol in the address bar).\n<li class=\"l\"> Support for the API has been added <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/web-otp\/\">Web OTP<\/a><\/noindex> (developed as SMS Receiver API), allowing for the integration of one-time password input on a web page after receiving an SMS message with a confirmation code sent to the user's Android smartphone running a browser. SMS confirmation, for example, can be used to verify the phone number provided by the user during registration. Previously, the user had to open the SMS application, copy the code to the clipboard, return to the browser, and paste the code; however, the new API enables this process to be automated and reduced to a single touch.\n<li class=\"l\"> Expanded API <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/web-animations\/\">Web Animations<\/a><\/noindex><br \/>\nfor controlling the playback of web animations. The new release adds support for compositing operations, allowing for control over how effects are combined and providing new handlers that are invoked upon content replacement events. The Web Animations API also now supports Promises to define the sequence in which animations are displayed and to better manage how animations interact with other application features.<\/p>\n<li class=\"l\"> Several new APIs have been added in Origin Trials (experimental features that require separate activation). Origin Trials allow the specified API to be used from applications loaded from localhost or 127.0.0.1, or after registration and obtaining a special token, which is valid for a limited time for a specific site.\n<ul>\n<li class=\"l\"> API <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5658847691669504\">Cookie Store<\/a><\/noindex> to allow Service Workers to access HTTP Cookies, serving as an asynchronous alternative to using document.cookie.\n<li class=\"l\">  API <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/idle-detection\/\">Idle Detection<\/a><\/noindex> for detecting user inactivity, allowing the determination of when a user is not interacting with the keyboard\/mouse, when the screensaver is active, the screen is locked, or when work is being done on another monitor. The application is informed of inactivity by sending a notification after reaching a specified inactivity threshold.\n<li class=\"l\"> Mode <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5683766104162304\">Origin Isolation<\/a><\/noindex>, allowing the developer to use a more complete isolation of content processing in a separate process tied to the origin (origin \u2014 domain+port+protocol), rather than the site, at the cost of discontinuing support for some deprecated features, such as synchronous execution of scripts using document.domain and calling postMessage() to send messages to instances of WebAssembly.Module. In other words, Origin Isolation allows for organizing separation into different processes based on the resource's domain rather than the website with all foreign inclusions on pages.\n<li class=\"l\"> API <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/features\/6533147810332672\">WebAssembly SIMD<\/a><\/noindex> for using vector SIMD instructions in applications in WebAssembly format. To ensure platform independence, a new 128-bit type is proposed that can represent different types of packed data, along with several basic vector operations for processing packed data. SIMD allows for improved performance through parallel data processing and will be beneficial when compiling native code into WebAssembly. To enable SIMD support, the setting 'chrome:\/\/flags\/#enable-webassembly-simd' can be used.\n<\/ul>\n<li class=\"l\"> Stabilized and now distributed outside of Origin Trials<br \/>\nAPI <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/content-indexing-api\/\">Content Indexing<\/a><\/noindex>, providing metadata about content that was previously cached by web applications operating in Progressive Web Apps (PWA) mode. The application can store various data on the browser side, including images, videos, and articles, and can utilize them when the network connection is lost, through the Cache Storage and IndexedDB APIs. The Content Indexing API allows adding, finding, and deleting such resources. This API is already used in browsers to list the pages and multimedia data available for offline viewing.<\/p>\n<li class=\"l\"> The API variant has been stabilized <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/2018\/12\/wakelock\">Wake Lock<\/a><\/noindex> based on the Promise mechanism, providing a safer way to manage screen auto-lock disabling and transitioning devices into power-saving modes.\n<li class=\"l\"> In the version for the Android platform <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/app-shortcuts\">has added<\/a><\/noindex> supporting application shortcuts that allow for quick access to commonly used actions in the application. To create shortcuts, simply add items to the web application manifest in PWA format.<br \/>\n<center><noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/app-shortcuts\/\"><img decoding=\"async\" alt=\"Chrome 84 Release\" src=\"\/wp-content\/uploads\/2020\/07\/bd93f6ee778be3c616f66229bc54bf54.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> API usage is permitted for Web Workers <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/reporting-observer\/\">ReportingObserver<\/a><\/noindex>, which allows defining a handler for generating a report triggered by the use of deprecated features. The generated report can be saved by the user, sent to a server, or processed by a JavaScript script.\n<li class=\"l\"> Updated API <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/resize-observer\">Resize Observer<\/a><\/noindex>, which allows attaching a handler that will receive notifications about the size changes of specified elements on the page. Three new properties have been added to ResizeObserverEntry: contentBoxSize, borderBoxSize, and devicePixelContentBoxSize to provide more detailed information, output as an array of ResizeObserverSize objects.\n<li class=\"l\"> A new keyword '<noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5644990145363968\">revert<\/a><\/noindex>' for resetting an element's style to its default value.\n<li class=\"l\"> The CSS property prefix '-webkit-appearance' and '-webkit-ruby-position' have been removed, which are now available as '<noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/4715298156445696\">appearance<\/a><\/noindex>\" and \"<noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/6249925820022784\">ruby-position<\/a><\/noindex>&#171;.\n<li class=\"l\"> In JavaScript <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5700509656678400\">within<\/a><\/noindex> support for marking class methods and properties as private, after which access to them will be limited to within the class (previously, only fields could be private). To mark methods and properties as private, you should use <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/tc39\/proposal-private-methods\/blob\/master\/README.md\">to indicate<\/a><\/noindex> Place the symbol '#' before the field name.\n<li class=\"l\"> In JavaScript <noindex><a rel=\"nofollow\" href=\"https:\/\/v8.dev\/blog\/v8-release-84\">has added<\/a><\/noindex> disabling the tracker blocking <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%A1%D0%BB%D0%B0%D0%B1%D0%B0%D1%8F_%D1%81%D1%81%D1%8B%D0%BB%D0%BA%D0%B0\">weak references<\/a><\/noindex> (weak reference) to JavaScript objects, allowing a reference to be maintained without preventing the related object from being garbage collected. Support for finalizers has also been added, allowing a handler to be defined that is invoked after a specified object's garbage collection is completed.\n<li class=\"l\"> Application launch on WebAssembly has been accelerated due to the implementation in the initial (baseline) compiler Liftoff. <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/WebAssembly\/threads\">atomic instructions<\/a><\/noindex> and <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/WebAssembly\/bulk-memory-operations\">batch operations with memory<\/a><\/noindex>. Improved tools for debugging WebAssembly, significantly enhancing debugging performance when using breakpoints (previously, an interpreter was used for debugging, but now the Liftoff compiler is utilized).\n<li class=\"l\"> In the web development tools at https:\/\/developers.google.com\/web\/updates\/2020\/05\/devtools, the panel for analyzing performance has been updated. General information about the <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/tbt\/\">TBT<\/a><\/noindex> (Total Blocking Time) metric has been added, showing how long a page appears accessible, but is actually not (i.e., the page is rendered, but the main thread execution is blocked, preventing data input). A new Experience section for analyzing the <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/cls\/\">CLS<\/a><\/noindex> (Cumulative Layout Shift), reflecting the visual stability of content. A preview of images specified through the 'background-image' property has been implemented in the CSS styles inspection panel.\n<\/ul>\n<p>56 vulnerabilities. <noindex><a rel=\"nofollow\" href=\"https:\/\/bugs.chromium.org\/p\/chromium\/issues\/list?can=1&#038;q=label%3ARelease-0-M84\">38 vulnerabilities<\/a><\/noindex>AddressSanitizer <noindex><a rel=\"nofollow\" href=\"http:\/\/code.google.com\/p\/address-sanitizer\/wiki\/AddressSanitizer\">MemorySanitizer<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/code.google.com\/p\/memory-sanitizer\/wiki\/MemorySanitizer\">Control Flow Integrity<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/sites.google.com\/a\/chromium.org\/dev\/developers\/testing\/control-flow-integrity\">LibFuzzer<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/sites.google.com\/a\/chromium.org\/dev\/developers\/testing\/libfuzzer\">AFL<\/a><\/noindex> and <noindex><a rel=\"nofollow\" href=\"http:\/\/lcamtuf.coredump.cx\/afl\/\">AFL<\/a><\/noindex>. One issue (CVE-2020-6510, buffer overflow in the fetch background operations handler) has been marked as critical, allowing it to bypass all browser security levels and execute code in the system outside the sandbox environment. As part of the vulnerability reward program for this release, Google has paid 26 rewards totaling $21,500 (two rewards of $5,000, two rewards of $3,000, one reward of $2,000, two rewards of $1,000, and three rewards of $500). The size of 16 rewards has not yet been determined. <\/p>\n<p><noindex><a rel=\"nofollow\" name=\"link\"><\/a><\/noindex><\/p>\n<p>Source: <a \ncontent=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=53362\">opennet.ru<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Google \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0430 \u0440\u0435\u043b\u0438\u0437 web-\u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0430 Chrome 84. \u041e\u0434\u043d\u043e\u0432\u0440\u0435\u043c\u0435\u043d\u043d\u043e \u0434\u043e\u0441\u0442\u0443\u043f\u0435\u043d \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u044b\u0439 \u0432\u044b\u043f\u0443\u0441\u043a \u0441\u0432\u043e\u0431\u043e\u0434\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0435\u043a\u0442\u0430 Chromium, \u0432\u044b\u0441\u0442\u0443\u043f\u0430\u044e\u0449\u0435\u0433\u043e \u043e\u0441\u043d\u043e\u0432\u043e\u0439 Chrome. \u0411\u0440\u0430\u0443\u0437\u0435\u0440 Chrome \u043e\u0442\u043b\u0438\u0447\u0430\u0435\u0442\u0441\u044f \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043b\u043e\u0433\u043e\u0442\u0438\u043f\u043e\u0432 Google, \u043d\u0430\u043b\u0438\u0447\u0438\u0435\u043c \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u043e\u0442\u043f\u0440\u0430\u0432\u043a\u0438 \u0443\u0432\u0435\u0434\u043e\u043c\u043b\u0435\u043d\u0438\u0439 \u0432 \u0441\u043b\u0443\u0447\u0430\u0435 \u043a\u0440\u0430\u0445\u0430, \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c\u044e \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u043c\u043e\u0434\u0443\u043b\u044f Flash \u043f\u043e \u0437\u0430\u043f\u0440\u043e\u0441\u0443, \u043c\u043e\u0434\u0443\u043b\u044f\u043c\u0438 \u0434\u043b\u044f \u0432\u043e\u0441\u043f\u0440\u043e\u0438\u0437\u0432\u0435\u0434\u0435\u043d\u0438\u044f \u0437\u0430\u0449\u0438\u0449\u0451\u043d\u043d\u043e\u0433\u043e \u0432\u0438\u0434\u0435\u043e\u043a\u043e\u043d\u0442\u0435\u043d\u0442\u0430 (DRM), \u0441\u0438\u0441\u0442\u0435\u043c\u043e\u0439 \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u043e\u0439 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0439 \u0438 \u043f\u0435\u0440\u0435\u0434\u0430\u0447\u0435\u0439 \u043f\u0440\u0438 \u043f\u043e\u0438\u0441\u043a\u0435 RLZ-\u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u043e\u0432. \u0421\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u0439 \u0432\u044b\u043f\u0443\u0441\u043a Chrome 85 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":88913,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-88912","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Google \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0430 \u0440\u0435\u043b\u0438\u0437 web-\u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0430\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/en\/blog\/news\/reliz-chrome-84\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0420\u0435\u043b\u0438\u0437 Chrome 84 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Google \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0430 \u0440\u0435\u043b\u0438\u0437 web-\u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0430\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/en\/blog\/news\/reliz-chrome-84\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-07-16T05:42:12+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-07-16T05:42:12+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Chrome 84 Release | ProHoster","description":"Google has released the web browser","canonical_url":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-chrome-84","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0420\u0435\u043b\u0438\u0437 Chrome 84 | ProHoster","og:description":"\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Google \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u0438\u043b\u0430 \u0440\u0435\u043b\u0438\u0437 web-\u0431\u0440\u0430\u0443\u0437\u0435\u0440\u0430","og:url":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-chrome-84","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-07-16T05:42:12+00:00","article:modified_time":"2020-07-16T05:42:12+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"88912","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 13:19:36","updated":"2022-09-30 22:56:22","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/88912","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=88912"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/88912\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media\/88913"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=88912"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=88912"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=88912"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}