Google heeft versie 101 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. In versie 101 wordt onder meer minder informatie met de user agent string meegezonden. Meer informatie over de veranderingen die in deze uitgave zijn aangebracht, naast de gebruikelijke bug- en security fixes, kunnen hieronder worden gevonden.
Reduce User Agent String InformationChrome is trying to reduce the amount of information the user agent string exposes in HTTP requests as well as in
Origin Trialsnavigator.userAgent,navigator.appVersion, andnavigator.platform. We're doing this to prevent the user agent string from being used for passive user fingerprinting. To join the origin trial, see its entry on Chrome Origin Trials. See the end of this article for additional deprecations and removals.This version of Chrome introduces the origin trial described below. Origin trials allow you to try new features and give feedback on usability, practicality, and effectiveness to the web standards community. To register for any of the origin trials currently supported in Chrome, including the ones described below, visit the Chrome Origin Trials dashboard. To learn more about origin trials in Chrome, visit the Origin Trials Guide for Web Developers. Microsoft Edge runs its own origin trials separate from Chrome. To learn more, see the Microsoft Edge Origin Trials Developer Console.
New Origin Trial: Federated Credential Management APIFederated Credential Management API (FedCM) aims to create privacy-preserving identity federation and is designed to make identity federation continue to allow use cases without the need for cross-site tracking such as third-party cookies. This feature starts its origin trial in 101 on Android only. We expect to add desktop support in Chrome 102.
Completed Origin TrialsThe following feature, previously in a Chrome origin trial, is now enabled by default.
Priority HintsPriority Hints provides a way to indicate a resource's relative importance to the browser, allowing more control over the order resources are loaded.
Other Features in this Release AudioContext.outputLatencyfont-palette and Custom @font-palette-values Palettes
AudioContext.outputLatencyproperty is an estimation in seconds of the interval between when the user agent requests a host system to play a buffer and when the first sample in the buffer is processed by the audio output device. For devices such as speakers or headphones that produce an acoustic signal, 'processed by the audio output device' refers to the time when a sample's sound is produced. This property helps developers compensate for the latency between the input and the output. It's also useful for synchronization of video and audio streams. This property is already implemented in Firefox.The
hwb() CSS functionfont-paletteCSS property allows selecting a palette from a color font. In combination with the@font-palette-valuesat-rule, custom palettes can be defined. This feature is useful in designs where an icon or emoji font is used with dark or light mode, or when using multi-colored icon fonts that use thefont-paletteto harmonize with the content's color scheme.HWB (short for 'hue whiteness blackness') is another method of specifying sRGB colors, similar to HSL, but often even easier for humans to work with. The
Make Popup Argument for window.open() Evaluate to 'true'hwb()function specifies HWB values in CSS. The function takes three arguments. The first,hue, specifies hue in degrees (not constrained to the range [0, 360]). The next two,whitenessandblackness, are specified as percentages.This feature follows a recent change to the spec for parsing the
MediaCapabilities API for WebRTCpopupargument forwindow.open(). Previously, whenpopupwas set equal to true,window.open()was interpreted to mean false. This is counterintuitive and confusing. This change makes boolean features easier to use and understand.The MediaCapabilities API has been extended to support WebRTC streams. The MediaCapabilities API helps websites make informed decisions on what codec, resolution, etc. to use for video playback by indicating whether a configuration is supported and also whether the playback is expected to be smooth. Without this feature, web apps need to guess about suitable configurations. This can result in poor quality such as when an application uses low resolution or frame rates unnecessarily, or stuttering when the frame rate is too high.
Secure Payment Confirmation API V3The following features from version three of the Secure Payment Confirmation API are now implemented:
USBDevice forget()
- A relying party ID that is a required input. Because this is required, existing code will need to be updated.
- An optional boolean to allow failed instrument icon download.
- A
payeeNameproperty as an optional input.The
WebUSB sameObject BehaviorUSBDeviceforget()method allows web developers to voluntarily revoke a permission to a USBDevice that was granted by a user.Deprecations, and Removals
USBConfiguration,USBInterface,USBAlternateInterface, andUSBEndpointinstances are now only strictly equal ("===") when they are retrieved from accessors on the sameUSBDevice.This version of Chrome introduces the deprecations and removals listed below. Visit ChromeStatus.com for lists of current deprecations and previous removals.
Remove WebSQL in Third-Party ContextsWebSQL in third-party contexts is now removed. The Web SQL Database standard was first proposed in April 2009 and abandoned in November 2010. Gecko never implemented this feature and WebKit deprecated it in 2019. The W3C encourages Web Storage and Indexed Database for those needing alternatives. Developers should expect that WebSQL itself will be deprecated and removed when usage is low enough.
:fill(white):strip_exif()/i/2002189289.jpeg?f=thumbmedium)
:strip_exif()/u/211274/bestabstractwallpapers5.gif?f=community){kind=small}