

getScreenDetails ( ) įor example, you can determine the primary screen, then use requestFullscreen() to make an element full screen on that display. isExtended īut, the key functionality is in window.getScreenDetails(), which provides details about the attached displays. You can quickly check if there's more than one screen connected to the device with. The Multi-Screen Window Placement API makes it possible to enumerate the displays connected to the user's machine, and place windows on specific screens. For example, when using Slides to present, I want the slides to appear full screen on the primary display, and my speaker notes to appear on the other display. # Multi-screen window placement APIįor some apps, opening new windows and putting them in specific places, or specific displays is an important feature.
#Chrome extension split screennote trial#
Starting in Chrome 101, the user agent will be gradually reduced.Ĭheck out User Agent Reduction Origin Trial and Dates on the, to learn more about what will be removed, and when. This is part of a strategy to replace use of the User-Agent string, with the new User-Agent Client Hints API. Speaking of the user agent, Chrome 100 will be the last version to support an unreduced User-Agent string by default.


When browsers first reached version 10, there were a few issues as the major version number went from one digit to two. Let's dive in and see what's new for developers in Chrome 100. The Multi-Screen Window Placement API makes it possible to enumerate the displays connected to a user's machine, and place windows on specific screens.There are some important changes to the user agent string.Take a stroll down memory lane and celebrate #100CoolWebMoments since Chrome's first release.Chrome 100 has a three digit version number.
