Web developers have found aborted AbortSignal objects to be useful for a variety of purposes. It is similar in spirit to Promise.reject(), and provides improved developer ergonomics. Other features in this release AbortSignal.abort() Static MethodĪbortSignal.abort() is a static method that allows creating a new AbortSignal object that is already aborted. Such solutions have thus far been unable to match the quality and accuracy of native augmented reality capabilities or support world scale. Without this feature, developers would have to resort to running their own computer vision algorithms on data from getUserMedia() (available on navigator and MediaDevices) in order to detect planes present in the users' environment. WebXR applications can now retrieve data about planes present in a user's environment, which enables augmented reality applications to create more immersive experiences. For JavaScript modules, execution still needs to wait for an entire resource tree to download because of deterministic execution. Ideally loading multiple subresources should use streaming and parallelization, which is not possible with one JavaScript file. Even with bundled JavaScript, execution needs to wait for all bytes to download. The output of some JavaScript bundlers does not interact well with the HTTP cache and configuring them can sometimes be difficult. This feature addresses issues with previous approaches to resource bundling. Web Bundles provides a new approach to load a large number of resources efficiently using a format that allows multiple resources to be bundled. The following features, previously in a Chrome origin trial, are now enabled by default. PWA as URL Handlers allows apps like to register themselves as URL handlers for URLs that match patterns like, or so that links from outside of the PWA, for example, from an instant messenger application or an email client, open in the installed PWA rather than in a browser tab. For more information, see Customize the window controls overlay of your PWA's title bar. Developers can use this feature to make their installed desktop web apps look like O.S. The web app developer is responsible for drawing and input-handling for the entire window except for the window controls overlay. Window 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). Window Controls Overlay for Installed Desktop Web Apps Incorporating developer feedback from the first origin trial, the API enters a second origin trial with an improved shape and ergonomics. And a restaurant can show a touchscreen menu on a kiosk and a separate window for employees. An art or music creation app can place palettes on a second screen. With this API, a presentation app can show slides on one screen and speaker notes on another. The Multi-Screen Window Placement API allows you to place windows on any display connected to your machine, store that placement, and make a window full-screen on any display. This is fine for some sites, but creates dependency problems for sites that gather content from users (Google Earth, social media generally, forums, etc.). It is functional and solid, but turns out to be difficult to deploy at scale, as it requires all subresources to explicitly opt-in. Today, COEP: require-corp exists, and is used to enable cross-origin isolation. Sites that wish to continue using SharedArrayBuffer must opt-in to cross-origin isolation. Similarly to COEP: require-corp, it can enable cross-origin isolation. New Origin Trials Cross-Origin-Embedder-Policy: credentiallessĬross-origin no-CORS requests can now be made to omit credentials (cookies, client certificates, etc.) using the credentialless keyword. To learn more, see the Microsoft Edge Origin Trials Developer Console. Microsoft Edge runs its own origin trials separate from Chrome. To learn more about origin trials in Chrome, visit the Origin Trials Guide for Web Developers. To register for any of the origin trials currently supported in Chrome, including the ones described below, visit the Chrome Origin Trials dashboard. Origin trials allow you to try new features and give feedback on usability, practicality, and effectiveness to the web standards community. This version of Chrome introduces the origin trials described below. Learn more about the features listed here through the provided links or from the list on. Unless otherwise noted, changes described below apply to the newest Chrome beta channel release for Android, Android WebView, Chrome OS, Linux, macOS, and Windows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |