Extend cookie deprecation metadata issue to include opt-out percentages, if present. Sample screenshots: With 1P opt-out: https://screenshot.googleplex.com/8DfCEkp2WC6gJPU With 3P opt-out: https://screenshot.googleplex.com/XEZnoDPNHuvk2BE Also include cookie operation to determine whether to show the Read or Set description. Screenshot: https://screenshot.googleplex.com/BCkjXKX9yqd9WS7 Bug: b/341051114, b/341794619 Change-Id: Id19b50a22642d6dcfad413b9f1db6849cc822935 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5551153 Reviewed-by: Joshua Hood <jdh@chromium.org> Reviewed-by: Wolfgang Beyer <wolfi@chromium.org> Commit-Queue: Anton Maliev <amaliev@chromium.org>
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com. Check out the project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
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