Google Git
Sign in
chromium / chromium / src / f985aa28fbdce1a93d72c328351b00c77ba6ba3c
commitf985aa28fbdce1a93d72c328351b00c77ba6ba3c[log] [tgz]
authorJeremie Boulic <jboulic@chromium.org>Mon Apr 29 02:23:19 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 29 02:23:19 2024
treeaaf0d2d4ae1e09616a96b2c2425e80971b406fcd
parentc581af0981a08926330eeb385f674e9d85ebdaf4 [diff]
Revert "iwa: Ensure that IsolatedContext APIs aren't available in opaque origins"

This reverts commit 1e0261cdf7a0ce886287e4e8ec56cca02e4e731f.

Reason for revert: those 2 tests added in this change
- ControlledFrameApiTest.DisabledInSandboxedIframe
- IsolatedWebAppApiAccessBrowserTest.NoApiAccessInSandboxedIframe
are consistently failing on linux-lacros-chrome.

Original change's description:
> iwa: Ensure that IsolatedContext APIs aren't available in opaque origins
>
> This tests that Direct Sockets and <controlledframe> are not visible
> in data: or sandboxed iframes. To support the latter, this also updates
> SiteInfo::ComputeWebExposedIsolationLevel to not delegate
> kIsolatedApplication to sandboxed iframes.
>
> Bug: b/322386534
> Change-Id: Id21fd0c38954fddc11baf4641025b77426de70d9
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5486479
> Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
> Reviewed-by: Chase Phillips <cmp@chromium.org>
> Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1293298}

Bug: b/322386534
Change-Id: I443871137873ba7938f0f836950bcf935cebfb0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5493186
Commit-Queue: Jeremie Boulic <jboulic@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Owners-Override: Jeremie Boulic <jboulic@chromium.org>
Reviewed-by: Jeremie Boulic <jboulic@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1293518}
4 files changed
tree: aaf0d2d4ae1e09616a96b2c2425e80971b406fcd
  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. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. clank
  52. internal
  53. ios_internal
  54. native_client
  55. signing_keys
  56. v8
  57. .clang-format
  58. .clang-tidy
  59. .clangd
  60. .eslintrc.js
  61. .git-blame-ignore-revs
  62. .gitallowed
  63. .gitattributes
  64. .gitignore
  65. .gitmodules
  66. .gn
  67. .mailmap
  68. .rustfmt.toml
  69. .vpython3
  70. .yapfignore
  71. ATL_OWNERS
  72. AUTHORS
  73. BUILD.gn
  74. CODE_OF_CONDUCT.md
  75. codereview.settings
  76. CPPLINT.cfg
  77. DEPS
  78. DIR_METADATA
  79. LICENSE
  80. LICENSE.chromium_os
  81. OWNERS
  82. PRESUBMIT.py
  83. PRESUBMIT_test.py
  84. PRESUBMIT_test_mocks.py
  85. README.md
  86. 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.