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 69.0.3497.81

Google Chrome logo, 2018 (80 pix) Google heeft versie 69 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. In versie 69 heeft onder meer het uiterlijk een opfrisbeurt gekregen. De belangrijkste veranderingen in deze uitgave, naast de gebruikelijke bug- en security fixes, zijn hieronder voor je op een rijtje gezet.

New CSS tricks
Chrome has added several new CSS features.

Conic gradients
CSS conic (angular/sweep) gradients allow color transitions around a center rather than radiating from it. This allows, for example, creating a hue wheel using only two CSS properties. More examples are available.

New margin, padding, and border properties
Logical margin, padding, and border properties now use standard names, specifically margin-{block,inline}-{start,end}, padding-{block,inline}-{start,end} and border-{block,inline}-{start,end}-{width,style,color}. These capabilities were previously supported through -webkit prefixes and non-standard names. Shorthand properties are only added for border-{block,inline}-{start,end}.

CSS scroll snap
CSS scroll snap positions are offsets in a scroll container's visual viewport where scrolling will stop after each scrolling operation. This improves the user experience by allowing scrollable zones to easily stop at predefined points. This also enables common UX scroll patterns without the need for JavaScript. One such pattern is a horizontal image carousel accomplished with the declarations below. The article Well-Controlled Scrolling with CSS Scroll Snap provides more depth.

Display cutouts
Display cutouts are now supported in Chrome through the new CSS env() function (environment variables) and the viewport-fit meta tag. This allows developers to take advantage of the entire screen on devices that have a display cutout. For example, to tell the browser to expand into the display cutout area the site should set the viewport-fit property in the viewport meta tag to cover. The site can then use the safe area inset CSS environment variables to layout their content without being covered by the cutout. The explainer and the spec provide more information.

Canvas
OffscreenCanvas is a new interface that allows 2D and WebGL canvas rendering contexts to be used in Workers. This increases parallelism in web applications and improves performance on multi-core systems. Chrome now also supports DedicatedWorker.requestAnimationFrame(), allowing animation-like events to be triggered the same on dedicated workers as they are in Window.

DOM
A new method named Element.toggleAttribute() allows toggling the existence of an element's attribute in a way similar to Element.classList.toggle. An optional force parameter forces addition or deletion of the attribute depending on the value of force. This makes managing boolean attributes much simpler as the interface doesn't use strings as does Element.setAttribute().

Fetch API: Request.isHistoryNavigation
A boolean property has been added to request objects to indicate whether a particular request is a history navigation. This allows a service worker to know whether a request was due to a back/forward navigation. An example of how this might be used is that a service worker could respond to such a navigation with a cached response.

JavaScript APIs
JavaScript has several new APIs:
  • The ReportingObserver API provides a JavaScript callback function invoked in response to deprecations and browser interventions. The report can be saved, sent to the server, or or handled using arbitrary JavaScript. This feature is designed to give developers greater insight into the operation of their sites on real-world devices.
  • JavaScript arrays are getting two new methods. Array.prototype.flat() returns a new array with all sub-array elements concatenated into it recursively up to the specified depth. The sub-array elements become members of the new array. Array.prototype.flatMap() first maps each element using a mapping function, then flattens the result into a new array. This method is functionally equivalent to a map followed by calling flat() with a depth of 1.
Keyboard Map API
Some applications such as games assign specific functions to specific physical keys. When the interface references these keys it needs to show either the character displayed on the key, which varies by locale, or the character assigned to the key by an alternate keyboard layout that may have been installed by the user. Because of these layout variations it's sometimes possible for the character shown in the interface to not reference the intended physical key. This new API provides a way to translate KeyboardEvent.code values representing physical keys into correct strings for display to the user. You can find details and examples of this new API in the specification and the explainer.

Loader
Support for the "rtt", "downlink", and "ect" client hint values and HTTP request headers have been added to Chrome to convey a device's network connection speed to servers. For example, the rtt client hint provides the server with the estimated effective round-trip time of the current connection, rounded to the nearest multiple of 25 milliseconds.The server could use this serve a downsampled image if the connection speed is slower than expected. These network quality hints provide to the server the same values as provided to a web page by the Network Information APIs navigator.connection.rtt, navigator.connection.downlink, and navigator.connection.effectiveType.

Media: Querying encryption scheme support through EME
Some platforms or key systems only support AES-128 in CTR mode, while others only support CBCS mode. Still others are able to support both. A new method allows web developers to query whether a specific encryption scheme is supported by Encrypted Media Extensions (EME).

Mid-ligature text selection
Chrome now allows for text to be selected inside ligatures. (A ligature is a combination of two or more letters in a single symbol.) This includes both mouse selection as well as cursor selection in input and textarea elements. We have also changed slightly the way we render text selection to support this change. Parts of text that happen to lie outside the selection area are now rendered with the original style.

Performance
To avoid leaking information between frames, performance.memory values are currently heavily quantized, and delayed by 20 minutes. If the renderer process is locked to documents from a single site (as in the case of Site Isolation on desktop), we can expose this information with fewer concerns about leaking information between frames. In these cases, we'll not return quantized memory consumption information, delayed by 30 seconds. This allows developers to detect performance regressions from user data more easily because the memory measurements will be more accurate and can be taken more frequently.

ServiceWorker
Service workers have two improvements:
  • ServiceWorkerRegistration.update() previously resolved with undefined. Now it resolves to the registration object as required by the specification.
  • Because of a technical limitation, navigator.serviceWorker previously threw a SecurityError when accessed on an insecure context. After this change, navigator.serviceWorker returns undefined.
This aligns with the specification.

Update behavior of CSS Grid Layout percentage row tracks and gutters
In a future release there will be a change to how percentage row tracks and gutters are resolved on grid containers with indefinite height. Currently they behave similar to percentage heights in regular blocks, but going forward they will behave the same as for columns, making them symmetric. Percentages will be ignored when computing intrinsic height (like it happens now) and resolved afterwards against that height. That way both column and row axes will have a symmetric behavior in order to resolve tracks and gutters specified by percentages. In Chrome 69 you'll get a warning in the JavaScript console about this change. If you want to keep the current behavior in Chrome 70 you need to replace your percentage row tracks and gutters in indefinite height grid containers by "auto" and "0px" respectively.

Web Locks API
The Web Locks API allows scripts running in one tab to asynchronously acquire a lock, hold it while work is performed, then release it. While held, no other script executing in the same origin can acquire the same lock. A lock represents some potentially shared resource, identified by a name chosen by the web app. For example, if a web app running in multiple tabs wants to ensure that only one tab is syncing to the network, each tab could try to acquire a my_net_sync lock, but only one tab will succeed. An example is shown below. It shows a function called when a lock for my_resource is acquired. await navigator.locks.request('my_resource', async lock => { const url = await look_up_in_database(); const response = await fetch(url); const body = await response.text(); await store_body_in_database(body); }); For more details about the API methods and options, see the explainer and draft specification.

Web Authentication now supports CTAP2 FIDO devices
Web Authentication adds support for CTAP2 devices, which provide advanced security capabilities such as biometric authentication and resident keys (keys stored on the device). The WebAuthentication API formerly only supported Universal 2nd Factor (U2F) devices at the transport layer. This change doesn't alter the API surface itself, but enables richer device interactions via the existing Web Authentication API.

WebRTC
WebRTC has two improvements:
  • Chrome now supports the RTCRtpParameters.headerExtensions dictionary entry which is returned by RTCRtpSender.getParameters(). This is a read-only field that allows inspection of the parameters that are set on a PeerConnection after negotiation.
  • The RTCRtpSender and RTCRtpReceiver interfaces now provide the getCapabilities() method
which returns the most optimistic view of the capabilities of the system for sending media of the given kind. It does not reserve any resources, ports, or other state but is meant to provide a way to discover the types of capabilities of the browser including which codecs or RTP extensions may be supported.

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

Removal of 'stalled' event from HTMLMediaElements that use Media Source Extensions
Previously, the HTMLMediaElement.stalled event fired when media download has failed to progress for at least 3 seconds. In Media Source Extensions, the web app manages the download and the media element is not aware of its progress. Since some apps append media data in chunks larger than 3 seconds, stalled was being fired at inappropriate times. To solve this, stalled has been removed for Media Source Extensions.

Removal of document.createTouchList
The document.createTouchList() method was removed in favor of the Touch() constructor which has been supported since Chrome 48.

The window.confirm() method no longer activates its parent tab
If a document in a background tab calls window.confirm(), it returns immediately with false, and no dialog is shown to the user. If the tab is active, then the call shows a dialog as normal. Specifically, this removes the ability to use window.confirm() to bring a tab to the front because this is rarely what the user wants.

Versienummer 69.0.3497.81
Releasestatus Final
Besturingssystemen Windows 7, Linux, macOS, Windows Server 2012, Windows 8, Windows 10, Windows Server 2016
Website Google
Download https://www.google.com/chrome/
Licentietype Freeware

Reacties (47)

Wijzig sortering
Er zijn ook weer flink wat security-problemen verholpen (40 in totaal): https://chromereleases.go...l-update-for-desktop.html
  • [$5000][867776] High CVE-2018-16065: Out of bounds write in V8. Reported by Brendon Tiszka on 2018-07-26
  • [$3000][847570] High CVE-2018-16066:Out of bounds read in Blink. Reported by cloudfuzzer on 2018-05-29
  • [$500][860522] High CVE-2018-16067: Out of bounds read in WebAudio. Reported by Zhe Jin(金哲),Luyao Liu(刘路遥) from Chengdu Security Response Center of Qihoo 360 Technology Co. Ltd on 2018-07-05
  • [N/A][877182] High CVE-2018-16068: Out of bounds write in Mojo. Reported by Mark Brand of Google Project Zero on 2018-08-23
  • [N/A][848238] High CVE-2018-16069:Out of bounds read in SwiftShader. Reported by Mark Brand of Google Project Zero on 2018-05-31
  • [N/A][848716] High CVE-2018-16070: Integer overflow in Skia. Reported by Ivan Fratric of Google Project Zero on 2018-06-01
  • [N/A][855211] High CVE-2018-16071: Use after free in WebRTC. Reported by Natalie Silvanovich of Google Project Zero on 2018-06-21
  • [$4000][864283] Medium CVE-2018-16072: Cross origin pixel leak in Chrome's interaction with Android's MediaPlayer. Reported by Jun Kokatsu (@shhnjk) on 2018-07-17
  • [$3000][863069] Medium CVE-2018-16073: Site Isolation bypass after tab restore. Reported by Jun Kokatsu (@shhnjk) on 2018-07-12
  • [$3000][863623] Medium CVE-2018-16074: Site Isolation bypass using Blob URLS. Reported by Jun Kokatsu (@shhnjk) on 2018-07-13
  • [$2500][864932] Medium: Out of bounds read in Little-CMS. Reported by Quang Nguyễn (@quangnh89) of Viettel Cyber Security on 2018-07-18
  • [$2000][788936] Medium CVE-2018-16075: Local file access in Blink. Reported by Pepe Vila (@cgvwzq) on 2017-11-27
  • [$2000][867501] Medium CVE-2018-16076: Out of bounds read in PDFium. Reported by Aleksandar Nikolic of Cisco Talos on 2018-07-25
  • [$1000][377995] Medium CVE-2018-16077: Content security policy bypass in Blink. Reported by Manuel Caballero on 2014-05-27
  • [$1000][858820] Medium CVE-2018-16078: Credit card information leak in Autofill. Reported by Cailan Sacks on 2018-06-28
  • [$500][723503] Medium CVE-2018-16079: URL spoof in permission dialogs. Reported by Markus Vervier and Michele Orr¨ (antisnatchor) on 2017-05-17
  • [$500][858929] Medium CVE-2018-16080: URL spoof in full screen mode. Reported by Khalil Zhani on 2018-06-29
  • [N/A][666299] Medium CVE-2018-16081: Local file access in DevTools. Reported by Jann Horn of Google Project Zero on 2016-11-17
  • [N/A][851398] Medium CVE-2018-16082: Stack buffer overflow in SwiftShader. Reported by Omair on 2018-06-11
  • [N/A][856823] Medium CVE-2018-16083: Out of bounds read in WebRTC. Reported by Natalie Silvanovich of Google Project Zero on 2018-06-26
  • [$1000][865202] Low CVE-2018-16084: User confirmation bypass in external protocol handling. Reported by Jun Kokatsu (@shhnjk) on 2018-07-18
  • [N/A][856578] Low CVE-2018-16085: Use after free in Memory Instrumentation. Reported by Roman Kuksin of Yandex on 2018-06-26
Nu nog het privacy-probleem :)
Nog meer mensen die de oude "New tab" pagina kwijt zijn?
Die pagina met thumbnails van meest bezochte sites was erg handig.

Kan het niet terug vinden? De optie staat aan maar het blijft de Google homepage.
Dat had ik dus ook.
Open een nieuwe tab en vul in : chrome://flags/
Zoek naar Enable using the Google local NTP en zet die op Enabled
Restart chrome en het is weer terug.
Supergoed deze tip! Hartelijk dank hiervoor :) .
Ik was hier al dik een half uur naar aan het zoeken. Ik kan nu zelfs 10 shortcuts gebruiken i.p.v. 8 zoals vroeger.
Als je de update nog niet krijgt of niet ziet, ga naar

Drie bolletjes (rechts boven) -> instellingen -> hamburger menu (links boven) -> Over Chrome (of about chrome)
Dan zoekt chrome naar een update en installeert die 'm ook

ik heb mijn chrome op Engels staan :+

[Reactie gewijzigd door IM_YOUR_MAMA op 4 september 2018 21:30]

Had jij ook het probleem dat Chrome een foutmelding gaf? Heb hem toen opnieuw opgestart (Chrome) en toen zei 'ie dat 'ie complete/up-to-date was :+. Iemand anders die ik net sprak had het ook.
Nee. Het downloaden en installeren ging zonder problemen. Na het installeren herstarten en klaar :)

Maar is die update wel gelukt of zegt chrome dat je de nieuwste versie al hebt? Mischien dan een dagje wachten en dan op een forum kijken als het weer niet lukt

[Reactie gewijzigd door IM_YOUR_MAMA op 4 september 2018 21:53]

Oh nee hij is wel ge´nstalleerd hoor, maar leek gewoon op een foutieve foutmelding dus :P, want er was uiteindelijk helemaal niets aan de hand.
Of je vult in je adres balk in:

chrome://settings/help
Is niet eens dringend tijd dat Tweakers die screenshot vervangt? Het design van Chrome is ondertussen al 2 keer vernieuwd geweest...
Tot zover bekend doet @Drobanir de gehele download section van Tweakers in zijn uppie. Ik kan mij voorstellen dat hij wel iets beters heeft te doen dan alle screenshots bij te houden. :)
Nee hoor, @Qwerty-273 (Japke Rosink) onderhoudt het ook.
Ah I was unaware. Thanks.
Met af en toe een stukje minder meukjes van mijn kant. Dus het kan heel goed zijn dat je Bart zijn naam/nick een stuk vaker ziet dan die van mij :)
U vraagt, wij draaien. ;-)
Wel dan: het Chrome logo is ook al een tijdje out-of-date. :P
Heb ik ook nog even voor je aangepast.
Nice, maar waarom niet het officiŰle logo?

[Reactie gewijzigd door Loller1 op 9 september 2018 21:05]

1x maar? Ik weet dat tot deze update de blauwe balk er nog steeds was op Windows 7 maar niet 10.
Ik wilde het precies typen toen ik dit artikel las. Maar toen bedacht ik me dat het opzich wel grappig is dat ze nog de oude versie laten zien, voor de nostalgie. Alhoewel dat misschien juist ook wel een leukigheidje zou kunnen zijn als ze het juist wel voor elke versie waar een grote uiterlijke verandering plaatsvindt voor bijhouden. Zo kun je terug gaan in de tijd in de downloadsectie bij Tweakers en kun je zien hoe het per versie er nog uit zag.
Geldt natuurlijk voor alle programma's die ze in hun 'downloads' vermelden.
Hebben meer mensen dat de content van de webpagina ineens wazig is? URL balk enz zijn scherp, maar een lijkt wel een waas over de content heen te zitten...
Misschien iets te maken met scaling? Restart je pc eens.
Deze heeft de nieuwe look. Material heet het dacht ik. Vind ik niet mooi. En zeker die ronde adresbalk niet.
Ah kijk, ik dacht dat het nieuwe design bij v70 kwam. Mooi! Ik vind het wel gewaagd na zo veel jaar hetzelfde ontwerp vast te houden iets anders te gaan proberen.

Ik vind het wel mooi. Ff wennen, dat wel maar ik vind helemaal mooi.
Chrome 69 also has initial support for AV1 video decoding though in this release it's only for the desktop versions of Chrome, limited to Main Profile 0, doesn't support AV1 encoding, and only works with the MP4 ISO-BMFF container.
Chrome speelt nu ook video's met AV1 codec af. Zou me niets verbazen als Youtube hier heel snel mee gaat testen!

Gebruik het nieuwe ontwerp 5 min en ben er nu al aan gewend. Vond het oude ontwerp ook prima, maar het oogt nu wel weer lekker fris en modern.
Brrrr dit uiterlijk kan me weinig bekoren. Doet me denken aan hoe Firefox er vroeger uit zag met afgeronde hoeken etc (of misschien was dat het thema wat ik vroeger gebruikte).
Daarentegen vind ik de tegel in het W10 start menu wel beter. Tenminste niet zo'n witte achtergrond.
Vind dit wel een hele fijne update. Het nieuwe uiterlijk vind ik wel mooi! :)

Op dit item kan niet meer gereageerd worden.


Apple iPhone XS Red Dead Redemption 2 LG W7 Google Pixel 3 XL OnePlus 6T (6GB ram) FIFA 19 Samsung Galaxy S10 Google Pixel 3

Tweakers vormt samen met Tweakers Elect, Hardware.Info, Autotrack, Nationale Vacaturebank en Intermediair de Persgroep Online Services B.V.
Alle rechten voorbehouden © 1998 - 2018 Hosting door True