{"id":56128,"date":"2020-02-05T00:00:00","date_gmt":"2020-02-04T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/reliz-chrome-80"},"modified":"2020-02-18T14:04:20","modified_gmt":"2020-02-18T11:04:20","slug":"reliz-chrome-80","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-chrome-80","title":{"rendered":"Release of Chrome 80","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Google Inc. <noindex><a rel=\"nofollow\" href=\"https:\/\/chromereleases.googleblog.com\/2020\/02\/stable-channel-update-for-desktop.html\">introduced<\/a><\/noindex> release of the web browser <noindex><a rel=\"nofollow\" href=\"http:\/\/www.google.com\/chrome\">Chrome 80<\/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, Chrome 81, is scheduled for March 17.<\/p>\n<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/support.google.com\/chrome\/a\/answer\/7679408\">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\/2019\/12\/chrome-80-content-indexing-es-modules.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-80\">80<\/a><\/noindex>:\n<\/p>\n<ul>\n<li class=\"l\"> For a small percentage of users, a tab grouping feature is offered, allowing similar tabs to be combined into visually separated groups. Each group can have its own color and name. Users not included in the first wave of activation can enable grouping support through the option &#171;chrome:\/\/flags\/#tab-groups&#187;.\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/pics_base\/0_1580888736.png\"><img decoding=\"async\" alt=\"Release of Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/beb1532c92889a0623d9b36fbbd11dff.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> Support for the feature <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=50156\">Scroll-To-Text<\/a><\/noindex>, allowing links to be created on individual words or phrases without explicitly indicating tags in the document using the &#171;a name&#187; tag or the &#171;id&#187; property. The syntax for such links is planned to be established as a web standard, which is still in the stage of <noindex><a rel=\"nofollow\" href=\"https:\/\/wicg.github.io\/ScrollToTextFragment\/\">draft<\/a><\/noindex>. The anchor for scrolling transitions is separated from the usual anchor by the marker &#171;:~:&#187;. For example, when opening the link &#171;https:\/\/opennet.ru\/52312\/#:~:text=Chrom\u0435&#187;, the page will shift to the position of the first mention of the word &#171;Chrom\u0435&#187;, and this word will be highlighted.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.chromium.org\/2020\/02\/samesite-cookie-changes-in-february.html\">A more stringent restriction on cookie transmission between sites has been applied, prohibiting the processing of third-party cookies for non-HTTPS requests when accessed to sites different from the current page's domain. These cookies are used to track user movements across sites in advertising network codes, social media widgets, and web analytics systems. It is important to note that the SameSite attribute specified in the Set-Cookie header is used to control cookie transmission, which is now set to \u201cSameSite=Lax\u201d by default, limiting the sending of cookies for cross-site subrequests such as image requests or content loading through an iframe from another site. Sites can override the default SameSite mode by explicitly setting the SameSite=None value when setting cookies. However, the SameSite=None value for cookies can only be set in Secure mode (applicable to connections via HTTPS). The change will be gradually<\/a><\/noindex> a stricter limitation on the transmission of cookies between sites, prohibiting the processing of third-party cookies set when accessing sites different from the domain of the current page for non-HTTPS requests. Such cookies are used to track user movements between sites in ad network code, social media widgets, and web analytics systems. It is important to note that the SameSite attribute specified in the Set-Cookie header is now defaulted to &#171;SameSite=Lax&#187;, which restricts the sending of cookies for cross-site subrequests, such as image requests or loading content via iframe from another site. Sites can override the default SameSite mode by explicitly setting SameSite=None when setting the cookie. Furthermore, the SameSite=None value for cookies can only be set in Secure mode (applicable for connections over HTTPS). The change will begin to be rolled out gradually. <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromium.org\/updates\/same-site\">starting February 17, initially for a small percentage of users and then gradually expanding the coverage.<\/a><\/noindex> On February 17, initially for a small percentage of users, and then gradually expanding the reach.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=52158\">Added<\/a><\/noindex> protection against intrusive notifications related to permission confirmation. Since such activity, like spam requests for push notifications, interrupts user workflow and distracts attention away from actions in confirmation dialogues, Chrome 80 will now display an informational tooltip in the address bar with a warning about blocking permission requests instead of a separate dialogue. This tooltip will then minimize into an indicator with an image of a crossed-out bell. Clicking on the indicator allows users to either grant or deny the requested permission at their convenience. Automatically, this new mode will selectively activate for users who have typically blocked such requests and for sites that record a high percentage of denied requests. A special option has been added in settings to enable this new mode for all requests (chrome:\/\/flags\/#quiet-notification-prompts).\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/pics_base\/0_1578565088.png\"><img decoding=\"async\" alt=\"Release of Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/0417193e7ff32c39042da014436c1d3a.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/2019\/12\/chrome-80-deps-rems\">Disabled<\/a><\/noindex> popup display (invoking the method window.open()) and sending synchronous XMLHttpRequest calls in event handlers for unloading or hiding the page (unload, beforeunload, pagehide, and visibilitychange);\n<li class=\"l\"> An initial <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=51612\">protection<\/a><\/noindex> from loading mixed multimedia content (when resources are loaded over http:\/\/ on an HTTPS page). On pages opened via HTTPS, links to 'http:\/\/' will now be automatically replaced with 'https:\/\/' in blocks related to audio and video playback. If an audio or video resource is unavailable over https, its loading is blocked (users can manually allow it through a menu accessed via the lock symbol in the address bar).\n<p>Images will continue to load unchanged (auto-replacement will be applied in Chrome 81), but for replacing with https or blocking images, developers are provided with the CSP properties upgrade-insecure-requests and block-all-mixed-content. The blocking of mixed content for scripts and iframes was previously implemented.<\/p>\n<li class=\"l\"> Gradual <noindex><a rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=51295\">disablement<\/a><\/noindex> of FTP support has begun. By default, FTP support remains active for now, but it will be <noindex><a rel=\"nofollow\" href=\"https:\/\/chromestatus.com\/feature\/6246151319715840\">conducted<\/a><\/noindex> an experiment in which FTP support will be disabled for a certain percentage of users (to revert this, the browser must be launched with the '--enable-ftp' option). It should be noted that previous releases have already blocked the display of resources loaded via 'ftp:\/\/' in the browser window (for instance, the display of HTML documents and README files has been discontinued), denied FTP usage for loading subresources from documents, and halted proxy support for FTP. However, the ability to download files through direct links and display the contents of directories still remains.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5180316371124224\">Added<\/a><\/noindex><br \/>\nThe ability to use vector SVG images as a website icon (favicon).<\/p>\n<li class=\"l\"> Settings have been added to selectively disable certain types of data transmitted during synchronization between browsers.\n<li class=\"l\"> A rule has been added for centrally administered corporate users <noindex><a rel=\"nofollow\" href=\"https:\/\/cloud.google.com\/docs\/chrome-enterprise\/policies\/?policy=BlockExternalExtensions\">BlockExternalExtensions<\/a><\/noindex>, which allows prohibiting the installation of external extensions on the device.\n<li class=\"l\"> If the user refreshes the page in private browsing mode, Firefox will interpret this as a problem and suggest <noindex><a rel=\"nofollow\" href=\"https:\/\/v8.dev\/features\/optional-chaining\">of<\/a><\/noindex> a one-time check of the entire chain of properties or calls in JavaScript. For example, when accessing 'db.user.name.length', it was previously necessary to check all components step by step, such as through 'if (db &amp;&amp; db.user &amp;&amp; db.user.name)'. Now, using the operation '?.', you can access the value 'db?.user?.name?.length' without prior checks, and such an access will not result in an error output. In case of issues (if any element is processed as null or undefined), the output will give the value 'undefined'.\n<li class=\"l\"> A new logical operator, '??', has been proposed in JavaScript, which returns the right operand if the left operand is NULL or undefined, and vice versa. For example, 'const foo = bar ?? 'default string'' will return the string if bar is null or the value of bar otherwise, including when bar is 0 and '', unlike the operator '||'.<noindex><a rel=\"nofollow\" href=\"https:\/\/v8.dev\/features\/nullish-coalescing\">??<\/a><\/noindex>&#171;, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0432\u043e\u0437\u0432\u0440\u0430\u0449\u0430\u0435\u0442 \u043f\u0440\u0430\u0432\u044b\u0439 \u043e\u043f\u0435\u0440\u0430\u043d\u0434, \u0435\u0441\u043b\u0438 \u043b\u0435\u0432\u044b\u0439 \u043e\u043f\u0435\u0440\u0430\u043d\u0434 \u0438\u043c\u0435\u0435\u0442 \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0435 NULL \u0438\u043b\u0438 undefined, \u0438 \u043d\u0430\u043e\u0431\u043e\u0440\u043e\u0442. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, &#171;const foo = bar ?? &#8216;default string'&#187; \u0435\u0441\u043b\u0438 bar \u0440\u0430\u0432\u0435\u043d null, \u0432\u0435\u0440\u043d\u0451\u0442 \u0441\u0442\u043e\u043a\u0443 \u0438\u043b\u0438 \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0435 bar \u0432 \u043f\u0440\u043e\u0442\u0438\u0432\u043d\u043e\u043c \u0441\u043b\u0443\u0447\u0430\u0435, \u0432 \u0442\u043e\u043c \u0447\u0438\u0441\u043b\u0435, \u043a\u043e\u0433\u0434\u0430 bar \u0440\u0430\u0432\u0435\u043d  0 \u0438 &#8216; &#8216;, \u0432 \u043e\u0442\u043b\u0438\u0447\u0438\u0435 \u043e\u0442 \u043e\u043f\u0435\u0440\u0430\u0442\u043e\u0440\u0430 &#171;||&#187;.\n<li class=\"l\"> In Origin Trials mode (experimental features that require separate <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.chrome.com\/origintrials\/#\/trials\/active\">activation<\/a><\/noindex>) the Content Indexing API has been proposed. The Origin Trial implies the ability to work with the specified API 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. The API <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/content-indexing-api\/\">Content Indexing<\/a><\/noindex>, provides metadata about content that was previously cached by web applications operating in Progressive Web Apps (PWS) mode. The application can store various data on the browser side, including images, videos, and articles, and utilize them via the Cache Storage and IndexedDB APIs when the network connection is lost. The Content Indexing API allows the addition, retrieval, and deletion of such resources. This API is already used in browsers to enumerate the list of pages and multimedia data available for offline viewing.\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/lh5.googleusercontent.com\/tkanWDKiU0jTm_ovD1MMjiV9cMX_XPexDY5_kyiZwScsnlPblj-wZUfWOax8aBAuzY3xl7h8tS4x92npA8UDJiKXH7jJfXTnehfU-g08RPbDZS8I-T62Dqzkrc5-3vN-UzCsXgAg\"><img decoding=\"async\" alt=\"Release of Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/5a9d7a4d4664a7d9e297ca707479d045.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> Stabilized and now distributed outside of Origin Trials, the API <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/contact-picker\/\">Contact Picker<\/a><\/noindex>, enabling the user to select entries from the address book and transmit certain details about them to the site. Upon request, a list of properties to retrieve is defined. These properties are explicitly displayed to the user, who decides whether to send these properties or not. The API can be used, for example, in a web-based email client to select recipients for a sent email, in a web application with VoIP functionality to initiate a call to a specific number, or in a social network to find already registered friends. Within the framework of Origin Trials, some new properties for the Contact Picker have been proposed: in addition to the previously available full name, email, and phone number, the ability to transmit postal addresses and images has been added.\n<li class=\"l\"> In Web Workers <noindex><a rel=\"nofollow\" href=\"https:\/\/web.dev\/module-workers\/\">introduced<\/a><\/noindex> a new way to load ECMAScript modules that allows avoiding the use of the importScripts() function, which blocks the worker during the import script processing and executes it in the global context. The new method involves creating special modules for Web Workers that support standard JavaScript import mechanisms and can be loaded dynamically without blocking the execution of the worker. A new resource type is provided in the Worker constructor \u2014 'module':\n<p>   const worker = new Worker('worker.js', {<br \/>\n     type: 'module'<br \/>\n   });<\/p>\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/chromestatus.com\/feature\/5855937971617792\">If the user refreshes the page in private browsing mode, Firefox will interpret this as a problem and suggest<\/a><\/noindex> a built-in capability for handling compressed streams in JavaScript that does not require the use of external libraries. For compression and decompression, the APIs have been added <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.google.com\/document\/d\/1TovyqqeC3HoO0A4UUBKiCyhZlQSl7jM_F7KbWjK2Gcs\/edit\">CompressionStream and DecompressionStream<\/a><\/noindex>. Compression is supported using gzip and deflate algorithms.\n<p>   const compressionReadableStream<br \/>\n         = inputReadableStream.pipeThrough(new CompressionStream('gzip'));<\/p>\n<li class=\"l\"> The CSS property '<noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5668660729348096\">line-break: anywhere<\/a><\/noindex>', allowing breaks at any typographic character level, including breaks near punctuation characters, predefined spaces (<pre>), and in the middle of words. The CSS property '<noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5126089347170304\">overflow-wrap: anywhere<\/a><\/noindex>&#187; allows breaking non-breaking sequences of characters anywhere if a suitable break position could not be found in the line.\n<li class=\"l\"> For the media context processed in encrypted form, support has been implemented for the method <noindex><a rel=\"nofollow\" href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/API\/MediaCapabilities\/decodingInfo\">to obtain decoding information for a specific configuration of encrypted and unencrypted media content, allowing applications to understand in advance whether the configuration is supported and whether the content will be smoothly and efficiently reproduced.<\/a><\/noindex>, which provides information about the browser's capabilities related to decoding protected content (for example, the specified method can be used to select high-quality or energy-saving decoding scenarios considering available bandwidth and screen size).\n<li class=\"l\"> A method has been added <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5687791428042752\">HTMLVideoElement.getVideoPlaybackQuality()<\/a><\/noindex>, through which information about video playback performance can be obtained to adjust bitrate, resolution, and other video parameters.\n<li class=\"l\"> In the <noindex><a rel=\"nofollow\" href=\"https:\/\/www.w3.org\/TR\/payment-request\/\">Payment Handler<\/a><\/noindex>, which simplifies integration with existing payment systems, the ability to <noindex><a rel=\"nofollow\" href=\"https:\/\/www.chromestatus.com\/feature\/5660404216758272\">delegate<\/a><\/noindex> the processing of address and contact information to an external payment system handler (the payment system application may have more accurate information than the browser).\n<li class=\"l\"> Support for the HTTP header <noindex><a rel=\"nofollow\" href=\"https:\/\/w3c.github.io\/webappsec-fetch-metadata\/#sec-fetch-dest-header\">Sec-Fetch-Dest<\/a><\/noindex>, enabling the submission of additional metadata regarding the type of content associated with the request (for example, for requests via the img tag, the type 'image' is specified, for fonts \u2014 'font', for scripts \u2014 'script', for styles \u2014 'style', etc.). Based on the specified type, the server can take measures to protect against certain types of attacks (for instance, it is unlikely that a handler for money transfer will be specified via the img tag, so such requests do not need to be processed).\n<li class=\"l\"> In the JavaScript engine V8 <noindex><a rel=\"nofollow\" href=\"https:\/\/v8.dev\/blog\/v8-release-80\">optimization has been carried out<\/a><\/noindex> of pointer storage in the heap. Instead of storing the full 64-bit value, only the unique lower bits of the pointer are stored. This optimization has reduced memory consumption in the heap by 40%, at the cost of a 3-8% reduction in performance.<br \/>\n<center><img decoding=\"async\" alt=\"Release of Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/f4d864466d5a0deb2b358e3d709d2e6c.png\" style=\"display:block;margin: 0 auto;\" \/><\/center><\/p>\n<p><center><img decoding=\"async\" alt=\"Release of Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/5219cc489b9572b105bb1dceeaedde6d.png\" style=\"display:block;margin: 0 auto;\" \/><\/center>\t<\/p>\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/2019\/12\/devtools\">Changes<\/a><\/noindex> in the web developer tools:\n<ul>\n<li class=\"l\"> In the web console, the ability to override let and class expressions has been introduced.\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/letafter.png\"><img decoding=\"async\" alt=\"Release of Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/900fb4a45dcfbe3c59093a875664d432.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> Improved debugging tools for WebAssembly. Support for  <noindex><a rel=\"nofollow\" href=\"http:\/\/dwarfstd.org\/\">DWARF<\/a><\/noindex> for step-by-step debugging, setting breakpoints, and analyzing stack traces in the source code of the WebAssembly application.\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/wasm.png\"><img decoding=\"async\" alt=\"Release of Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/18918605318647f5bdaf403822f83010.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> The panel for analyzing network activity has been improved. It now includes a feature to view the call chain of scripts related to the initiation of requests.\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/initiators.png\"><img decoding=\"async\" alt=\"Release of Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/1981db2b84541612ec63f54dea90a25d.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<p>New columns Path and URL have been added, showing the absolute path and full URL for each network resource. The selected request is highlighted in the overview diagram.<\/p>\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/overview.png\"><img decoding=\"async\" alt=\"Release of Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/e2f07ee205c13a4f10ef9b9e944d8fa8.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> The Network Conditions tab now includes an option to modify the User-Agent parameter.\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/useragent.png\"><img decoding=\"async\" alt=\"Release of Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/c605d0146e32813320d6517c55e4efe2.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> A new interface has been proposed for configuring the audit panel.<br \/>\n<center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/start.png\"><img decoding=\"async\" alt=\"Release of Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/c16f004b56b488f06fe68d27291b1e11.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<li class=\"l\"> In the tab <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/tools\/chrome-devtools\/coverage\">Coverage<\/a><\/noindex> there is an option to collect coverage data for each function or for each block of code (more detailed statistics, but requires more resources).\n<p><center><noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/images\/2019\/12\/modes.png\"><img decoding=\"async\" alt=\"Release of Chrome 80\" src=\"\/wp-content\/uploads\/2020\/02\/2c80bbceb4c576bf399399986c81bb2d.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/center><\/p>\n<\/ul>\n<li class=\"l\"> The AppCache manifest action (a technology for enabling web applications to work in offline mode) <noindex><a rel=\"nofollow\" href=\"https:\/\/blog.chromium.org\/2020\/01\/appcache-scope-restricted.html\">is restricted<\/a><\/noindex> to the current site directory (if the manifest was loaded from www.example.com\/foo\/bar\/, then the ability to override the URL will only work within \/foo\/bar\/). Support for AppCache is planned to be completely removed in Chrome 82. The reason given is the desire to eliminate one of the vectors for attacks related to cross-site scripting. Instead of AppCache, it is recommended to use the <noindex><a rel=\"nofollow\" href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/API\/Cache\">Cache<\/a><\/noindex>.\n<li class=\"l\"> <noindex><a rel=\"nofollow\" href=\"https:\/\/developers.google.com\/web\/updates\/2019\/12\/webvr-1-1-removed\">Support for the outdated WebVR 1.1 API has been discontinued, which can now be replaced with the<\/a><\/noindex> that provides access to components for creating virtual and augmented reality and standardizes interaction with various classes of devices, from stationary virtual reality headsets to solutions based on mobile devices. <noindex><a rel=\"nofollow\" href=\"https:\/\/immersive-web.github.io\/webxr\/\">WebXR Device<\/a><\/noindex>Protocol handlers registered via the registerProtocolHandler() and unregisterProtocolHandler() methods can now operate only in a secure context (when accessed via HTTPS).\n<li class=\"l\"> In addition to new features and bug fixes, the new version has resolved\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-M80\">Many of the vulnerabilities were identified through automated testing tools.<\/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>No critical issues have been found that allow bypassing all browser security levels and executing code outside the sandbox environment. As part of the vulnerability reward program for the current release, Google has paid 37 rewards totaling $48,000 (one reward of $10,000, three rewards of $5,000, three rewards of $3,000, four rewards of $2,000, three rewards of $1,000, and six rewards of $500). The amount for 17 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=52312\">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 80. \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 81 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-56128","post","type-post","status-publish","format-standard","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-80\" \/>\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 80 | 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-80\" \/>\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-02-04T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-02-18T11:04:20+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 80 Release | ProHoster","description":"Google has released the web browser","canonical_url":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-chrome-80","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 80 | 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-80","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-02-04T21:00:00+00:00","article:modified_time":"2020-02-18T11:04:20+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"56128","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 19:30:42","updated":"2022-10-07 18:25:29","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\/56128","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=56128"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/56128\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=56128"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=56128"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=56128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}