Software-update: Google Chrome 74.0.3729.108

Google Chrome logo (80 pix) Google heeft versie 74 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 versie 74, naast de gebruikelijke bug- en security fixes, zijn hieronder voor je op een rijtje gezet.

CSS prefers-reduced-motion media query

Some users have reported getting motion sick when viewing parallax scrolling, zooming, and other motion effects. To address this, many operating systems like Android provide an accessibility option to reduce motion whenever possible. Chrome now provides a media query, prefers-reduced-motion (part of Media Queries Level 5), that allows websites to honor these options when they are available. For all the details and options, read Move Ya! Or maybe, don't, if the user prefers-reduced-motion!.

Private class fields

Chrome 72 introduced ECMAScript's new public class fields. Class fields simplify class syntax by avoiding the need for constructor functions just to define instance properties. Starting in Chrome 74, you can mark a field as private and no consumer of the class can ever access its value. To mark a field as private, prepend it with a pound sign (#). As with public class fields, your properties do not need to be in a constructor. Unlike public fields, private fields are not accessible outside of the class body. To read more about private class fields as well as the existing public class fields, read Public and private class fields. See Specification Compliance in this article for more on CSS changes.

JavaScript API for feature policy

Feature policies, which were introduced in Chrome 60, allow websites to selectively enable, disable, and modify the behavior of APIs and other web features. This is done either through the Feature-Policy header or through the allow attribute on an iframe. In Chrome 74, feature policies are enhanced with the addition of a JavaScript API, available from document.featurePolicy and frame.featurePolicy. The new API encompasses three functions:

  • returns a list of features allowed by the current domain.
  • allowsFeature() returns a boolean indicating whether a specific feature is allowed by either the current domain or by the specified domain.
  • getAllowlistForFeature() returns a list of domains used on the current page that allow a specified feature.

For examples of these methods and for information about feature policy in general, read Introduction to Feature Policy.

sampleRate option for the AudioContext constructor

Sets the "sampleRate" to a particular value for an AudioContext that will be created. This allows developers to set an arbitrary sample rate for audio processing in Web Audio API that is separate from the hardware rate. Use this to reduce complexity (by using a lower sample rate) or make the sample rate consistent across all devices by using a fixed rate and letting WebAudio resample appropriately for the hardware rate.


Chrome now supports the Intl.Locale class, which allows the following:

  • Parsing and manipulating the language, region, and script of a locale
  • Reading or writing the Unicode extension tags in a locale
  • Storing user locale preferences for this API in a serializable, standard format (rather than using a combination of language and the options object).
Signed exchange reporting for distributors

Signed Exchange Reporting for distributors extends Network Error Logging to enable the distributors of signed exchanges to investigate signed exchange loading errors such as certificate verification errors.

TextEncoder encodeInto() method

Chrome now supports TextEncoder.prototype.encodeInto(), which allows an encoded string to be written directly "into" a supplied pre-allocated buffer, offering a performant alternative to using encode() to produce a buffer, and copying its contents into an existing buffer.

Service worker: client.postMessage() is buffered until the document is ready.

To prevent messages from being delivered before the destination is ready, client.postMessage() does not dispatch the message until one of the following has occurred on the destination:

  • DOMContentLoaded event is fired.
  • onmessage is set.
  • startMessages() is called.
CSS transition events

The CSS Transitions specification requires that transition events are sent when a transition is enqueued, starts, ends, or is canceled as transitionrun, transitionstart, transitionend, and transitioncancel respectively. These events mirror the CSS animation events which allow developers to observe CSS animations. Chrome now follows the specification.

RTCIceCandidate and RTCIceCandidateInit

RTCIceCandidate and RTCIceCandidateInit now comply with the specification. The RTCIceCandidate interface describes an ICE candidate in WebRTC. It is available in Chrome, but it is not spec compliant as it is missing some fields. There are also some deviations from the specification in terms of nullable and read-only attributes and errors thrown by the constructor.

XHR falls back to UTF-8 when invalid encoding is specified

When an invalid encoding is specified for an XMLHttpRequest (via overrideMimeType() or the response's MIME type), UTF-8 is used in conformance with the specification. Previously Latin-1 was used. Note: This applies to desktop Chrome only.

Remove PaymentAddress's languageCode property

The PaymentAddress's languageCode property has been removed from the Payment Request API. This property is the browser's best guess for the language of the text in the shipping, billing, delivery, or pickup address in Payment Request API. The languageCode property is marked at risk in the specification and has already been removed from Firefox and Safari. Usage in Chrome is small enough for safe removal.

Don't allow popups during page unload

Pages may not use the API to open a new page during its unload event. The popup blocker already prohibited this, but now it is prohibited whether or not the popup blocker is enabled. For now, enterprises can use the AllowPopupsDuringPageUnload policy flag to allow popups during unload. We expect to remove this flag in Chrome 82. Note: This was originally targeted at Chrome 72, but was actually removed to Chrome 74.

Deprecate drive-by downloads in sandboxed iframes

Chrome will soon prevent downloads in sandboxed iframes that lack a user gesture, though this restriction could be lifted via an allow-downloads-without-user-activation keyword in the sandbox attribute list. This allows content providers to restrict malicious or abusive downloads. Downloads can bring security vulnerabilities to a system. Even though additional security checks are done in Chrome and the operating system, we feel blocking downloads in sandboxed iframes also fits the general thought behind the sandbox. Apart from security concerns, it would be a more pleasant user experience for a click to trigger a download on the same page, compared with downloads starting automatically when a user lands on a new page, or started non-spontaneously after the click.

Versienummer 74.0.3729.108
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

Reacties (7)

Wijzig sortering
Deze versie heeft ook dark mode voor Windows.
Ook Chrome OS heeft een update naar 74 gehad.

Voor de Chrome browser is de Dark mode toegevoegd zoals PannekoekenNL hierboven al aangaf maar ook LBS en Cloud Management zijn vereenvoudigt.
Dark mode for Windows in Chrome 74
In Chrome 74, if the system theme is set to dark, Chrome on Windows will also use a dark theme on screen.

Legacy Browser Support will no longer need an extension
In Chrome 74, you can deploy Legacy Browser Support to automatically switch users between Chrome Browser and another browser.

Chrome Browser updates
Chrome Browser Cloud Management
Chrome Browser has introduced support for management through the Google Admin console with Chrome Browser Cloud Management. Admins can use the Admin console to manage Chrome Browser across Windows®, Mac®, and Linux®, without requiring users to sign in. Learn more about Chrome Browser Cloud Management.
Helaas werkt bij mij de dark mode niet.

support bij Google leert dat dit gefaseerd uitgerold word ?
Probeer eens chrome te starten met --force-dark-mode (ongeveer als "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --force-dark-mode).
Dat werkte in voorgaande versies ook, maar vanaf versie 74 zijn de laatste pijnpunten gladgestreken :)

[Reactie gewijzigd door BaggerDeBagger op 24 april 2019 08:57]

Weet iemand of de dark mode ook al voor linux (ubuntu) is ?
Zoja weet iemand dan toevallig hoe je het aan zet ?
Leuk dark mode (zzz) maar wanneer krijgen we de lang geleden beloofde autoplay video blocker?
De feature policy is erg handig om specifieke dingen uit te schakelen zodat security exploits moeilijker te gebruiken zijn. Dit lijkt heel erg op SE Android maar dan voor Chrome en webstandaarden. Alleen jammer genoeg wel server side, dus als een server gekraakt wordt heb je er niks aan.

[Reactie gewijzigd door MrFax op 24 april 2019 20:22]

Op dit item kan niet meer gereageerd worden.

Nintendo Switch (OLED model) Apple iPhone SE (2022) LG G1 Google Pixel 6 Call of Duty: Vanguard Samsung Galaxy S22 Garmin fēnix 7 Nintendo Switch Lite

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

Tweakers maakt gebruik van cookies

Tweakers plaatst functionele en analytische cookies voor het functioneren van de website en het verbeteren van de website-ervaring. Deze cookies zijn noodzakelijk. Om op Tweakers relevantere advertenties te tonen en om ingesloten content van derden te tonen (bijvoorbeeld video's), vragen we je toestemming. Via ingesloten content kunnen derde partijen diensten leveren en verbeteren, bezoekersstatistieken bijhouden, gepersonaliseerde content tonen, gerichte advertenties tonen en gebruikersprofielen opbouwen. Hiervoor worden apparaatgegevens, IP-adres, geolocatie en surfgedrag vastgelegd.

Meer informatie vind je in ons cookiebeleid.


Toestemming beheren

Hieronder kun je per doeleinde of partij toestemming geven of intrekken. Meer informatie vind je in ons cookiebeleid.

Functioneel en analytisch

Deze cookies zijn noodzakelijk voor het functioneren van de website en het verbeteren van de website-ervaring. Klik op het informatie-icoon voor meer informatie. Meer details


    Relevantere advertenties

    Dit beperkt het aantal keer dat dezelfde advertentie getoond wordt (frequency capping) en maakt het mogelijk om binnen Tweakers contextuele advertenties te tonen op basis van pagina's die je hebt bezocht. Meer details

    Tweakers genereert een willekeurige unieke code als identifier. Deze data wordt niet gedeeld met adverteerders of andere derde partijen en je kunt niet buiten Tweakers gevolgd worden. Indien je bent ingelogd, wordt deze identifier gekoppeld aan je account. Indien je niet bent ingelogd, wordt deze identifier gekoppeld aan je sessie die maximaal 4 maanden actief blijft. Je kunt deze toestemming te allen tijde intrekken.

    Ingesloten content van derden

    Deze cookies kunnen door derde partijen geplaatst worden via ingesloten content. Klik op het informatie-icoon voor meer informatie over de verwerkingsdoeleinden. Meer details