Sources: Add alert to pretty-print info bar learn more message. When the user clicks "Learn More" in the pretty-print info-bar in sources, a description is added to the screen describing how the pretty-print functionality works. However, nothing is announced to screen readers. This PR marks that info as an alert, so that when it is revealed, Screenreaders announce the info. Bug: 1211509 Change-Id: Iaaa56623c9b98ffacce34d57c38721870dceb15a Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2910444 Commit-Queue: Brandon Goddard <brgoddar@microsoft.com> Reviewed-by: Patrick Brosset <patrick.brosset@microsoft.com> Reviewed-by: Philip Pfaffe <pfaffe@chromium.org>
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