Google heeft versie 99 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 99 is onder meer showPicker() toegevoegd, wat gebruikt kan worden voor het invoeren dingen als datum, tijd en kleur. Verder is er een nieuwe download-shortcut, is er handschriftherkenning en zijn de eerste stappen gezet voor het uitfaseren van Manifest v2, war onder meer voor adblockers gevolgen heeft. Meer informatie over de veranderingen die in deze uitgave zijn aangebracht, naast de gebruikelijke bug- en security fixes, kunnen hieronder worden gevonden.
CSS Cascade LayersCSS cascade layers (
@layerrule and layered@importsyntax) provide a structured way to organize and balance concerns within a single origin. Rules within a single cascade layer cascade together without interleaving with style rules outside the layer. This allows authors to achieve a certain cascade ordering for same-origin rules in a proper way.Cascade layers allow authors to create layers to represent element defaults, third-party libraries, themes, components, overrides, etc.—and are able to re-order the cascade of layers in an explicit way. Without cascade layers, authors need to tweak, e.g., selector specificity,
New showPicker() Method on HTMLInputElement Objects@importor source ordering to achieve a certain cascade ordering, which is cumbersome and error-prone. For more information, see this.The new
showPicker()method onHTMLInputElementallows web developers to programmatically show a browser picker for input elements (temporal, color, file, and those with suggestions like datalist or autofill).Developers have been asking for years for a way to programmatically open a browser date picker. Without it, they've had to rely on custom widget libraries and CSS hacks for specific browsers.
This is currently possible in some browsers, for some controls, via the
Origin Trialsclick()method. Unfortunately, that doesn't work in all browsers, making the experience inconsistent across systems and users. ProvidingshowPicker()gives developers a supported alternative toclick(), and aligns Chromium'sclick()behavior with the specification and other browsers in in the future. For more information, see Show a browser picker for date, time, color, and files.This version of Chrome introduces the origin trials 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 Trials: Dark Mode Support for Web AppsWeb app manifests now support the color_scheme_dark field for specifying a different theme color and background color for dark mode. Currently in the web app manifest, only a single theme color and background color can be defined. This means there is no way for apps to specify a different color to use for dark mode.
Completed Origin TrialsThe following features, previously in a Chrome origin trial, are now enabled by default.
Handwriting Recognition APIThis API lets web applications use handwriting recognition services that are available on operating systems to recognize hand-written text in real time. This reduces the need for third-party integration by apps that use handwriting recognition. For more information, see Recognize your users' handwriting.
Window Controls Overlay for Installed Desktop Web AppsWindow controls overlay extends an app's client area to cover the entire window, including the title bar, and the window control buttons (close, maximize/restore, minimize). The web app developer is responsible for drawing and input-handling for the entire window except for the window controls overlay. Developers can use this feature to make their installed desktop web apps look like operating system apps. For more information, see Customize the window controls overlay of your PWA's title bar.
Other Features in this Release Allow infinity, -infinity and NaN in CSS calc()To improve conformance with the spec, the CSS
CSS Color Adjust: 'only' Keyword for color-schemecalc()method now allows infinity and NaN using the'infinity','-infinity', and'NaN'keywords or expressions that can be evaluated as such, for example: 'calc(1/0)'.Note: This feature was erroneously listed as shipping in Chrome 98. It actually shipped in Chrome 99.
The only keyword, which has been re-added to the specification for
document.adoptedStyleSheets is Now Mutablecolor-scheme, is now supported in Chrome. It allows opting out ofcolor-schemefor single, specific elements. For example, this allows overriding of force darkening.In compliance with the spec, the
Improve Alignment with Spec for Exposing nextHopProtocol Across Origin Boundariesdocument.adoptedStyleSheetsproperty is now mutable, meaning operations such aspush()andpop()work on it. The previous implementation ofadoptedStyleSheetswas unwieldy. For example, to add a sheet, the entire array had to be re-assigned.The
New Canvas 2D FeaturesPerformanceResourceTiminginterface exposes thenextHopProtocolproperty to describe the underlying connection type used to fetch a resource. To follow the spec, Chrome is removing an old special case where cross-origin requests exposed potentially sensitive information, putting users at risk.Chrome has added several new attributes to the
CanvasRenderingContext2Dinterface to conform to specs:
ContextLostandContextRestoredevents"willReadFrequently"option for canvases where lots of readback is expected- More CSS text modifier support
- A reset() method
- A
roundRectdraw primitive- Conic gradients
- Better support for SVG filters
For more information, see It's always been you Canvas2D.
Unprefixed text-emphasis PropertiesChrome 99 introduces unprefixed versions of text emphasis CSS properties, specifically:
Deprecations, and Removals"text-emphasis","text-emphasis-color","text-emphasis-position", and"text-emphasis-style"CSS properties. These are unprefixed versions of"-webkit-text-emphasis","-webkit-text-emphasis-color","-webkit-text-emphasis-position", and"-webkit-text-emphasis-style".This version of Chrome introduces the deprecations and removals listed below. Visit ChromeStatus.com for lists of current deprecations and previous removals.
Remove Battery Status API on Insecure OriginsBattery Status API is no longer supported on insecure origins, such as HTTP pages or HTTPS iframes embedded in HTTP pages. The Battery Status API allows web developers to access, among other things, a system's battery charging level and whether it is being charged. It is a powerful feature that has been around for over a decade and, as such, was originally designed with different security constraints.
Remove font-family -webkit-standardThis version of Chrome removes support for the
Remove GamepadListfont-familyvalue"-webkit-standard". This value is merely an alias for the proprietary keyword"-webkit-body"and is only exposed because it's inherited from WebKit. Removing this improves alignment with the CSS specifications and with Firefox.The
Update WebCodecs to Match Specnavigator.getGamepads()method now returns an array ofGamepadobjects instead of a GamepadList.GamepadListis no longer supported in Chrome. This brings Chrome in line with spec and with Gecko and Webkit. For information on Gamepads generally, see Play the Chrome dino game with your gamepad.Chrome has removed two items because of recent changes in the WebCodecs spec.
TheEncodedVideoChunkOutputCallback()method takes anEncodedVideoChunkMetadatadictionary. Previously a member called temporalLayerId was located atEncodedVideoChunkMetadata.temporalLayerId. In conformance with the spec, it is now located atEncodedVideoChunkMetadata.SvcOutputMetadata.temporalLayerId.
The spec requires that theVideoFrame()constructor include a timestamp argument (VideoFrameInit.timestamp) forCanvasImageSourcetypes that don't implicitly have a timestamp (e.g.HTMLCanvasElement). Failing to include the timestamp should result in aTypeError, but Chrome previously defaulted the timestamp to zero. This seems helpful, but is problematic if you then send theVideoFrameto aVideoEncoder, where timestamps are used to guide bitrate control.
:fill(white):strip_exif()/i/2002189289.jpeg?f=thumbmedium)
:strip_icc():strip_exif()/u/1668372/crop61739eae50965_cropped.jpg?f=community){kind=small}
/u/48718/crop619e5ed546e66_cropped.png?f=community){kind=small}
:strip_exif()/u/38542/Scrat1ani.gif?f=community){kind=small}
/u/63682/crop5de0dc242f46f_cropped.png?f=community){kind=small}
/u/1076507/crop6206d5954bbe1_cropped.png?f=community){kind=small}
:strip_icc():strip_exif()/u/961/crop687fa3fc8a3e4_cropped.jpg?f=community){kind=small}
:strip_icc():strip_exif()/u/60174/avatar10570_1%252060pix.jpg?f=community){kind=avatar}