Revert "Inherit service worker controller for srcdoc iframe"

This reverts commit f0232ec8df7029a085dd1fac1c9af57eaa52cbab.

Reason for revert: this CL might cause crbug.com/382895651 crbug.com/382895896 because the origin of srcdoc client may not be the origin of controlling service worker script origin.

Although there is a follow up CL (crrev.com/c/6081248) that may fix the issue, I prefer to revert the possible root cause before applying it so that easy to distinguish the root cause.

Original change's description:
> Inherit service worker controller for srcdoc iframe
>
> Same origin srcdoc iframes should be controlled by the same service
> worker that controls the parent frame.
>
> To achieve this, we expand ServiceWorkerClient::InheritControllerFrom to
> also support srcdoc and about:blank iframes and use it to setup service
> worker client for srcdoc frames when NavigationRequest for them is to be
> committed. Not that while InheritControllerFrom is updated to also
> support about:blank iframes, this change is only for srcdoc iframes.
> about:blank iframe navigation is committed synchronously and requires
> separate fix.
>
> To allow these clients to show up in clients.matchAll, we update same
> origin check in GetWindowClients to use GetLastCommittedOrigin instead
> of GetLastCommittedURL of the frames.
>
> As the srcdoc frame test in about-blank-replacement.https.html now
> passes, update expectation to reflect that.
>
>
> Bug: 41411856
> Change-Id: I2c464bd7c0e9e8bdf656ad24aeef631fae5a3a31
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6054691
> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
> Commit-Queue: Liang Zhao <lzhao@microsoft.com>
> Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
> Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1393072}

Bug: 41411856, 382895896, 382895651
Change-Id: Iac2d99aab1f2273e87089053468c8c520d6077e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6083273
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Rakina Zata Amni <rakina@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1394212}
6 files changed
tree: 6a64e99f4622847ad21e22f1a88fd4fbc6b4ad4f
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.