Cookies op Tweakers

Tweakers maakt gebruik van cookies, onder andere om de website te analyseren, het gebruiksgemak te vergroten en advertenties te tonen. Door gebruik te maken van deze website, of door op 'Ga verder' te klikken, geef je toestemming voor het gebruik van cookies. Wil je meer informatie over cookies en hoe ze worden gebruikt, bekijk dan ons cookiebeleid.

Meer informatie

Software-update: Google Chrome 71.0.3578.80

Google Chrome logo, 2018 (80 pix) Google heeft versie 71 van zijn webbrowser Chrome uitgebracht. Google Chrome is beschikbaar voor Windows, Linux en macOS. Er zijn ook versies voor Android en iOS, maar die volgen een iets ander releaseschema. Sinds versie 50 is de ondersteuning voor oudere versies van Windows en macOS vervallen. De belangrijkste veranderingen in deze uitgave, naast de gebruikelijke bug- en security fixes, zijn hieronder voor je op een rijtje gezet.

International Relative Time Format^
When writing (and speaking), phrases such as 'yesterday' or 'in three months' are common. Yet such phrases are not part of built-in date and time APIs. To fill this need, libraries provide utility functions to provide localized versions of such phrases. The downside to this approach is that using these functions on the web requires downloading lists of customary words or phrases for each supported language. This increases a library's bundle size and download time. Chrome 71 introduces Intl.RelativeTimeFormat(), which shifts the burden to the JavaScript engine. This new API has a number of capabilities including such things as retrieving information for multiple languages, dealing with parts of a date or time individually (in other words, formatToParts()), and more. Read our article for details.

Add FullscreenOptions^
The Element.requestFullscreen() method can now be customized on Android using an optional options parameter. Its navigationUI parameter allows you to choose between making the navigation bar visible versus a completely immersive mode where no user agent controls are shown until a gesture is performed. Possible values are "auto", "show", and "hide". This value expresses an application preference, with "auto" meaning no preference. The UI may overrule this vale in any case.

Add 'persistent-storage' property to the Permission API^
The "persistent-storage" property is a new permission for the Permission API. The permission state can already be queried with, with this change navigator.permissions.query({name:"persistent-storage"}) can be used as well.

Async touchpad pinch zoom events^
Async touchpad pinch zoom events are for improving the page pinch zoom performance. Currently, the touchpad pinch zoom exposes a control wheel event that allows JS to cancel it. With this change, if the user doesn't make a pinch action on the touchpad, effectively canceling the control wheel event, then following control wheel events are not cancelable. But JavaScript does not know which ctrl wheel is the first one in the sequence, so if you want to cancel pinch zoom, you need to cancel all of them.

COLR/CPAL font support^
Chrome now supports COLR/CPAL fonts which are a type of OpenType color font composed of layers of vector outline glyphs and color palette information into the final colored glyph. With this change, Chrome supports three color font formats cross-platform, the other two being CBDT/CBLC and SBIX. Because they are vector based, COLR/CPAL fonts provide for faster downloads and require less storage. An example of a COLR/CPAL font is the Twemoji color font.

CSS gradient color stop double-position syntax^
Support is added for the stop position syntax from the CSS Image Values and Replaced Content Module Level 4 spec. Currently, repeating colors require explicit positions. For example:
linear-gradient(45deg, black 25%, black 50%, white 50%, white 75%)
To simplify the definition of solid color bands, two positions may be specified instead. For example:
linear-gradient(45deg, black 25% 50%, white 50% 75%)

Implement 'left' and 'right' values for 'text-underline-position'^
Currently, in vertical flow for Chinese and Japanese, which side the underline appears on is not the same across browsers. To fix this, Chrome is adding support for 'left' and 'right' values of the 'text-underline-position' property. This property is part of the CSS3 Text Decoration spec which adds properties that implement new text decoration styling features such as lines, color, and style, including 'text-underline-position'.

JavaScript Modules: Credentials mode defaults to "same-origin"^
The default credentials mode for module script requests is changing from "omit" to "same-origin", providing credentials to same-origin module script requests and their descendant scripts (static and dynamic imports). The current behavior can be surprising in that it's misaligned with other high-level features like the Fetch API, and in the web platform's current architecture, causes a second server connection. This is undesirable for developers looking to reduce latency.

TextEncoderStream and TextDecoderStream APIs^
Text encoding and decoding supports streams to enable you to easily convert streams of binary data to text and vice-versa. An example of its usefulness is with readable streams. With a non-stream Response object, response.body.text() returns text. There is no equivalent for the ReadableStream returned by Response.Body, which can only return bytes. With the new API a streaming response body may be converted to text as so: Response.Body.pipeThrough(new TextDecoderStream()).

Unprefixed Fullscreen API^
The Fullscreen API has features for entering, and exiting fullscreen mode as well as event handlers for monitoring such changes. A prefixed version of the API has been supported since Chrome 15. This update adds an unprefixed version of the API.

MediaElement and MediaStream nodes defined only for AudioContext^
Chrome now only allows creation of MediaElementAudioSourceNode, MediaStreamAudioSourceNode, and MediaStreamAudioDestinationNode elements using an AudioContext. Previously these could be created using an OfflineAudioContext, but that does not comply with the spec. The behavior with an OfflineAudioContext is not well-defined and contrary to the real-time nature of the nodes themselves.

Call capture event listeners in capturing phase at shadow hosts^
To be interoperable with other browsers, Chrome now calls capture event listeners in the capturing phase at shadow hosts. Previously this was done in the bubbling phase on Chrome. A complete discussion may be read on the WHATWG repo on GitHub.

Improve :host, :host-context, and ::slotted specificity^
Chrome now calculates the specificity for the :host() and :host-context() pseudo classes as well as for the arguments for ::slotted(). This brings it into compliance with the Shadow DOM v1 spec. Shipping this will ensure interoperability between browsers since other browsers have or are about to ship this in their stable releases.

Deprecations and Removals^
Chrome sometimes deprecates, removes, or changes features to increase interoperability with other browsers. This version of Chrome includes the following such changes.

Remove SpeechSynthesis.speak without user activation^
The speechSynthesis.speak() method now fires an error if the document has not received user activation. This API is being abused by sites since it is one of the only remaining APIs which didn't adhere to autoplay policies in Chrome.

Remove importScripts() of new scripts after service worker installation.^
Previously, a service worker could use importScripts() to import any script at any time. After this change, a service worker can only use importScripts() in two cases:
  • Before installation finishes (from the initial execution of the service worker until it reaches the `installed` state).
  • After installation finishes, only for scripts that were already imported in the previous phase.
Remove prefixed versions of several APIs^
Chrome has removed non-standard aliases for two widely supported standard interfaces. Remove URL.createObjectURL for MediaStream^
The URL.createObjectURL() method has been removed from the MediaStream interface. This method has been deprecated in 2013 and superseded by assigning streams to srcObject.

Remove document.origin^
The document.origin property has been removed. This property was only ever implemented in Chromium and WebKit. It is redundant with self.origin which can be used in both window and worker contexts and has wider support.

Versienummer 71.0.3578.80
Releasestatus Final
Besturingssystemen Windows 7, Linux, macOS, Windows Vista, Windows Server 2008, Windows Server 2012, Windows 8, Windows 10, Windows Server 2016
Website Google
Licentietype Freeware

Door Bart van Klaveren

Downloads en Best Buy Guide

05-12-2018 • 05:11

10 Linkedin

Submitter: mikeoke

Bron: Google

Reacties (10)

Wijzig sortering
Er zijn ook versies voor Android en iOS, maar die volgen een iets ander releaseschema.
Wat voor andere release schema? Ik krijg er op mijn android toestel de update voor versie 71 binnen.
for Windows version 71.0.3578.80
for Android version 71.0.3578.83

Afgelopen maandag waren deze versies nog in Beta maar gister werden de versies ineens Stable

Er is ook nog een releaseschema voor Chrome OS (Chromebooks)
versie 70.0.3538.110 (Platform version: 11021.81.0)

Als je ook de Chrome browsers via je GP (grouppolicy) onderhoud vergeet dan niet om je templates bij te werken.
Ik wilde de "oude" look terug zetten alleen "normal" dmv chrome://flags/#top-chrome-md maar schijnbaar is dit niet meer van toepassing :'(
Iemand die weet welke instelling dit nu wel is.

[Reactie gewijzigd door Pierre op 5 december 2018 08:07]

Waarom wil je niet de nieuwe? Probeer het eens. Mensen houden niet van verandering, dat is een feit. Bijt er even doorheen en na een dag zal je zien dat het toch eigenlijk wel prima werkt.
Gebruik chrome al een aantal maanden niet meer nadat ik merkte dat de fan van mijn videokaart op een hoog toerental begon te draaien terwijl mijn pc in rustmodus stond.
In taakbeheer stonden behoorlijk wat chrome processen te draaien die ik niet thuis kon brengen.
Waarschijnlijk een virusje of een ander vervelend beestje opgelopen die mijn gpu gebruikt om te minen via chrome. (gokje)
De scans die ik daarna heb uitgevoerd leverde helaas niets op.
Dus voor mij voorlopig ff geen chrome. :'(
Al eens geprobeerd van Chrome te draaien met een antiminer?
Of blokkeer de miners in je hosts-file met de nocoin-list. Het bestand is eergisteren nog up-to-date gebracht.
Dit soort gekke dingen krijg je toch niet zomaar binnen? Goede antivirussoftware geïnstalleerd? Ik zou zelf zoiets toch tot de bodem uitzoeken hoe zoiets op mijn pc kan komen ipv geen Chrome meer te gebruiken. Ben zelf al jaren enorm tevreden met Chrome icm abp plug-in en ESET als antivirus waarin ik weinig tot geen problemen ervaar. Tja Chrome houd van ram maar dat heb ik voldoende.
Firefox Quantum geeft prima performance.

Op dit item kan niet meer gereageerd worden.

Apple iPhone SE (2020) Microsoft Xbox Series X LG CX Google Pixel 4a CES 2020 Samsung Galaxy S20 4G Sony PlayStation 5 Nintendo Switch Lite

'14 '15 '16 '17 2018

Tweakers vormt samen met Hardware Info, AutoTrack,, Nationale Vacaturebank, Intermediair en Independer DPG Online Services B.V.
Alle rechten voorbehouden © 1998 - 2020 Hosting door True