commit | fa905ffd7bfdf9ab99345d254b4614882f0da6b4 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Mon May 25 17:07:16 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Mon May 25 17:07:16 2020 |
tree | 308ae09970efa08d851dfb044cf68a6b829a70dd | |
parent | f82df89d667afb34d788c3845eb4c52b7433f981 [diff] |
Roll DevTools Frontend from ec8892b5506b to ba95542b7b83 (1 revision) https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/ec8892b5506b..ba95542b7b83 2020-05-25 patrick.brosset@microsoft.com New simple E2E tests for the styles and computed panes If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: chromium:1079076 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I690d459b35539efeb57e48a68e68e7ffed86e0f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2214474 Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#771594}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.