Revert "[CDP] introduce Inspector.workerScriptLoaded"

This reverts commit 022b53e3fb2c5fd52e4be026fad5097de1a52b17.

Reason for revert:
LUCI Bisection has identified this change as the cause of a test failure. See the analysis: https://ci.chromium.org/ui/p/chromium/bisection/test-analysis/b/6242229220802560

Sample build with failed test: https://ci.chromium.org/b/8700937344516775633
Affected test(s):
[ninja://:blink_web_tests/inspector-protocol/target/target-send-message.js](https://ci.chromium.org/ui/test/chromium/ninja:%2F%2F:blink_web_tests%2Finspector-protocol%2Ftarget%2Ftarget-send-message.js?q=VHash%3Adae5f96b53c0ec12)

If this is a false positive, please report it at http://b.corp.google.com/createIssue?component=1199205&description=Analysis%3A+https%3A%2F%2Fci.chromium.org%2Fui%2Fp%2Fchromium%2Fbisection%2Ftest-analysis%2Fb%2F6242229220802560&format=PLAIN&priority=P3&title=Wrongly+blamed+https%3A%2F%2Fchromium-review.googlesource.com%2Fc%2Fchromium%2Fsrc%2F%2B%2F7016867&type=BUG

Original change's description:
> [CDP] introduce Inspector.workerScriptLoaded
>
> This event tells when the main worker script, and all imported
> scripts, have been evaluated. Most of the time, accessing worker
> before this moment is useless, as you get an empty context.
>
> Now clients can setup the worker before the main script is evaluated,
> then call Runtime.runIfWaitingForDebugger, and then wait until the
> main script is evaluated before evaluating anything in the fully
> setup worker.
>
> Bug: 407795731
> Change-Id: Ie800a17dae42810e077c7c0bf49f0821d728a674
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7016867
> Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
> Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1530173}
>

Bug: 407795731
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Change-Id: Ie6c5035c66b3ff0199dabc87c0cd5aa5074eea70
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7045937
Owners-Override: Giovanni Ortuno Urquidi <ortuno@chromium.org>
Reviewed-by: Giovanni Ortuno Urquidi <ortuno@chromium.org>
Commit-Queue: Giovanni Ortuno Urquidi <ortuno@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1530214}
15 files changed
tree: 34ab0c21b5242af7a784bc4d8d79051ba6d88e61
  1. .gemini/
  2. .github/
  3. agents/
  4. android_webview/
  5. apps/
  6. ash/
  7. base/
  8. build/
  9. build_overrides/
  10. buildtools/
  11. cc/
  12. chrome/
  13. chromecast/
  14. chromeos/
  15. codelabs/
  16. components/
  17. content/
  18. crypto/
  19. dbus/
  20. device/
  21. docs/
  22. extensions/
  23. fuchsia_web/
  24. gin/
  25. google_apis/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. net/
  34. pdf/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. .clang-format
  51. .clang-tidy
  52. .clangd
  53. .cursorignore
  54. .geminiignore
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. CRYPTO_OWNERS
  72. DEPS
  73. DIR_METADATA
  74. LICENSE
  75. LICENSE.chromium_os
  76. OWNERS
  77. PRESUBMIT.py
  78. PRESUBMIT_test.py
  79. PRESUBMIT_test_mocks.py
  80. README.md
  81. SECURITY_OWNERS
  82. WATCHLISTS
README.md

Logo Chromium

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.