Update feature check for window segments With crrev.com/c/3153295, the `getWindowSegments` method on Window is being removed and is moving to a property on VisualViewport, in response to feedback from the standardization process. The method was being used as feature detection for the dual screen device emulator, so move to the new check instead. Bug: none Change-Id: Ie36ee8ec6dc280da58e17a2bf7f845e47497c45b Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3160316 Reviewed-by: Paul Lewis <aerotwist@chromium.org> Commit-Queue: Daniel Libby <dlibby@microsoft.com>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Please be aware that DevTools follows additional development guidelines.
The issue triage guidelines can be found in docs/triage_guidelines.md.
Instructions to set up, use, and maintain a DevTools frontend checkout can be found in docs/workflows.md.
DevTools frontend repository is mirrored on GitHub.
DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.
The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools