[devtools] De-flake OOPIF elements panel test Instead of waiting for multiple life-cycle 'load' events we wait for one DOMContentLoaded event. This guarantees that the iframe is ready with the DOM. Expanding the iframe still happens asynchronously so the timeout is still required. For some reason the elements panel doesn't work nicely with `expandRecursively`, like, at all. Note that reliability is still drastically improved when running the test locally with multiple parallel content_shells. R=alexrudenko@chromium.org Fixed: 358504673 Change-Id: I601ec8629b02fb9dc75876589a2191cfd0f8dc55 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6591362 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Alex Rudenko <alexrudenko@chromium.org> Auto-Submit: Simon Zünd <szuend@chromium.org> Commit-Queue: Alex Rudenko <alexrudenko@chromium.org> Cr-Commit-Position: refs/heads/main@{#1465864}
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.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
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.
If you found a bug, please file it at https://crbug.com/new.