[Merge m135] Reland "Have InspectorView remove the Infobar instead of CookieControlsView" This is a reland of commit 1ac4ec696c100a4ad50d8a951d96069f2a791d06 Original change's description: > Have InspectorView remove the Infobar instead of CookieControlsView > > If CookieControlsView was responsible for listening for a > PrimaryPageChanged event and then removing the Infobar, the infobar > would not be removed if CookieControlsView was never created to > listen in the first place. This is a problem because the Infobar > might be created by the InspectorMain entrypoint which does not > guarantee that a CookieControlsView will be created as well. > > By moving the listener to the InspectorView, we guarantee that the > Infobar is removed when the user reloads the page without needing > to open the Privacy and security panel. > > Bug: 400962121 > Change-Id: I612c4899e218e094fd31a3eda154ec69c20e8035 > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6346989 > Reviewed-by: Kim-Anh Tran <kimanh@chromium.org> > Reviewed-by: Danil Somsikov <dsv@chromium.org> > Commit-Queue: Joshua Thomas <masnoble@chromium.org> Bug: 400962121 Fixed: 405951279 Change-Id: I2d12b5bdcc19ed4d814208788e6c0503991d1e83 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6367775 Reviewed-by: Danil Somsikov <dsv@chromium.org> Reviewed-by: Kim-Anh Tran <kimanh@chromium.org> Commit-Queue: Joshua Thomas <masnoble@chromium.org> (cherry picked from commit 7411149fb580997b03862748742ce3b7a045c9f0) Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6391375
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 Chromium DevTools 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.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/devtools-reviews@chromium.org mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.