RPP: fix overlay visibility We had a bug where sometimes some overlays would incorrectly stay visible even though they should be hidden. The problem was we were controlling this via the `visibility` property, but an element with `visibility: hidden` may still have its children visible if they have their visibility set to `visible`. This was the root of the bug; we were setting the parent overlay to hidden, but that did not apply to all children. This CL moves us to `display: block` and `display: none` which does not have this problem. Fixed: 356352905,356359407,356353052 Change-Id: I8479a237e9f47bbbf2f89789367a8409f0303f28 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5822073 Commit-Queue: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Alina Varkki <alinavarkki@chromium.org> Auto-Submit: Jack Franklin <jacktfranklin@chromium.org> Reviewed-by: Alina Varkki <alinavarkki@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 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.