[Extensions] Add tests for SW registration from injected scripts

Previously, there were no browser tests validating whether scripts
injected by an extension into a web page can register cross-origin,
extension-resource, redirected, or blob URL service workers on the
target web origin. In addition, the browser test
ExtensionWebRequestApiTestWithContextType.WebRequestRedirectsWorkers,
which tests webRequest redirects around workers, was disabled across
platforms due to flakiness, remained on Manifest V2, and lacked test
coverage for chrome-extension:// redirect targets.

With this change, browser tests in
InjectedScriptServiceWorkerBrowserTest and
ExtensionWebRequestApiTestWithContextType explicitly verify that service
worker registration restrictions are enforced for extension-injected
scripts across three scenarios:
- Scenario 1: Registering a service worker from a cross-origin web
  script or an extension resource script. Covered by
  RegisterCrossOriginExtensionResourceOrBlobWorkerFails, verifying
  rejection with SecurityError in both isolated and main worlds.
- Scenario 2: Registering a same-origin service worker and intercepting
  or replacing the script via declarativeNetRequest or webRequest
  redirects. Covered by
  InterceptWorkerScriptViaDnrFailsWithRedirectError (for DNR) and
  InterceptWorkerScriptViaWebRequestFailsWithRedirectError (for
  webRequest), verifying rejection with SecurityError and that no
  registration is created. In addition,
  ExtensionWebRequestApiTestWithContextType.WebRequestRedirectsWorkers
  is revived, converted to Manifest V3, and expanded with
  chrome-extension:// redirect test cases alongside https:// and data:
  URLs across all worker types.
- Scenario 3: Registering a service worker from a same-origin blob
  URL. Covered by
  RegisterCrossOriginExtensionResourceOrBlobWorkerFails, verifying
  rejection with TypeError in both isolated and main worlds.

Bug: 40092884
Change-Id: Id8aa3aeaa68d2f3191bb7e4596e07ac34154b6b9
Fixed: 40255652, 40259518, 40282182, 393555373
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8427581
Reviewed-by: Andrea Orru <andreaorru@chromium.org>
Commit-Queue: Justin Lulejian <jlulejian@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1707525}
7 files changed
tree: 8234fe9348a98ed7b97e06de8baf77858754ac6e
  1. .agents/
  2. .claude/
  3. .gemini/
  4. .github/
  5. agents/
  6. android_webview/
  7. apps/
  8. ash/
  9. base/
  10. build/
  11. build_overrides/
  12. buildtools/
  13. cc/
  14. chrome/
  15. chromecast/
  16. chromeos/
  17. codelabs/
  18. components/
  19. content/
  20. crypto/
  21. dbus/
  22. device/
  23. docs/
  24. extensions/
  25. fuchsia_web/
  26. gin/
  27. google_apis/
  28. gpu/
  29. headless/
  30. infra/
  31. ios/
  32. ipc/
  33. media/
  34. mojo/
  35. net/
  36. pdf/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. webkit/
  52. .clang-format
  53. .clang-tidy
  54. .clangd
  55. .cursorignore
  56. .geminiignore
  57. .git-blame-ignore-revs
  58. .gitallowed
  59. .gitattributes
  60. .gitignore
  61. .gitmodules
  62. .gn
  63. .mailmap
  64. .rustfmt.toml
  65. .yapfignore
  66. ATL_OWNERS
  67. AUTHORS
  68. BRANCH_FEATURE_OWNERS
  69. BRANCH_OWNERS
  70. BUILD.gn
  71. CODE_OF_CONDUCT.md
  72. codereview.settings
  73. CPPLINT.cfg
  74. CRYPTO_OWNERS
  75. DEPS
  76. DIR_METADATA
  77. LICENSE
  78. LICENSE.chromium_os
  79. OWNERS
  80. package.json
  81. PRESUBMIT.py
  82. PRESUBMIT_test.py
  83. PRESUBMIT_test_mocks.py
  84. README.md
  85. SECURITY_OWNERS
  86. vpython.toml
  87. vpython.toml.uv.lock
  88. 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.