Google Git
Sign in
chromium / chromium / src / 8edcb697fe1619424c5780bfff1664ff6b641929
commit8edcb697fe1619424c5780bfff1664ff6b641929[log] [tgz]
authorAri Chivukula <arichiv@chromium.org>Thu Mar 10 19:22:31 2022
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Mar 10 19:22:31 2022
treea8629d08053425a4ce29cc3ebfe7f21a851034a8
parent90381b85e0f668d050793e99b929fba6a77dc14d [diff]
[WebSQL] Add flag to disable WebSQL, and enterprise policy to override

WebSQL is a legacy standard, so there should add a way for users to
disable it and enterprises to re-enable if needed. Specifically:
(1) A new flag called web-sql-access, defaulting to enabled, that the
user can switch off.
(2) A new enterprise policy called WebSQLAccess, defaulting to disabled,
that can force enable WebSQL over the setting in the user's flag.

These are being added with an eye toward a future where WebSQL might be
disabled by default. When that's the case, the user would be able to
enable via the flag and/or the enterprise can enable via the policy.

TL;DR: if flag or policy is on, WebSQL is enabled. Enabled is still the
default state.

P.S. I'm not using the existing Database runtime feature because that's
hooked into WebPreferences. If Database is on, the flag and policy can
still disable WebSQL. If Database is off, the flag and policy have
no effect.

Bug: 695592
Change-Id: I7a48ef23179085dcbdc5fceec2bc3f8ca4e7b2c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3499154
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Commit-Queue: Ari Chivukula <arichiv@chromium.org>
Auto-Submit: Ari Chivukula <arichiv@chromium.org>
Cr-Commit-Position: refs/heads/main@{#979893}
21 files changed
tree: a8629d08053425a4ce29cc3ebfe7f21a851034a8
  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. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  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. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  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.