diff options
| author | Florian Bruhin <me@the-compiler.org> | 2022-03-04 12:45:14 +0100 |
|---|---|---|
| committer | Florian Bruhin <me@the-compiler.org> | 2022-03-06 23:05:13 +0100 |
| commit | 355ec2ca6f8af97bc5653e8a05d9bc011688e9fa (patch) | |
| tree | a385b6b3fdecc75da0d9b7bb92d4be8ee62ea9c5 | |
| parent | 7f1d92b59697ade838a9df980d4cfc93319de0c3 (diff) | |
| download | qutebrowser-new-chromium-args.tar.gz qutebrowser-new-chromium-args.zip | |
Update docsnew-chromium-args
| -rw-r--r-- | doc/help/settings.asciidoc | 3 | ||||
| -rw-r--r-- | qutebrowser/config/configdata.yml | 12 |
2 files changed, 8 insertions, 7 deletions
diff --git a/doc/help/settings.asciidoc b/doc/help/settings.asciidoc index 2e51ecc7f..b332e7c46 100644 --- a/doc/help/settings.asciidoc +++ b/doc/help/settings.asciidoc @@ -3821,7 +3821,8 @@ What sandboxing mechanisms in Chromium to use. Chromium has various sandboxing layers, which should be enabled for normal browser usage. Mainly for testing and development, it's possible to disable individual sandboxing layers via this setting. Open `chrome://sandbox` to see the current sandbox status. Changing this setting is only recommended if you know what you're doing, as it **disables one of Chromium's security layers**. To avoid sandboxing being accidentally disabled persistently, this setting can only be set via `config.py`, not via `:set`. -See the Chromium documentation for more details: - Linux: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux/sandboxing.md - Windows: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/design/sandbox.md - FAQ (Windows-centric): https://chromium.googlesource.com/chromium/src/+/HEAD/docs/design/sandbox_faq.md +See the Chromium documentation for more details: +- https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux/sandboxing.md[Linux] - https://chromium.googlesource.com/chromium/src/+/HEAD/docs/design/sandbox.md[Windows] - https://chromium.googlesource.com/chromium/src/+/HEAD/docs/design/sandbox_faq.md[FAQ (Windows-centric)] This setting requires a restart. diff --git a/qutebrowser/config/configdata.yml b/qutebrowser/config/configdata.yml index 28df8da0e..9a72ea82c 100644 --- a/qutebrowser/config/configdata.yml +++ b/qutebrowser/config/configdata.yml @@ -301,6 +301,7 @@ qt.chromium.sandboxing: backend: QtWebEngine restart: true no_autoconfig: true # due to it being dangerous + # yamllint disable rule:line-length desc: >- What sandboxing mechanisms in Chromium to use. @@ -316,12 +317,11 @@ qt.chromium.sandboxing: `config.py`, not via `:set`. See the Chromium documentation for more details: - - Linux: - https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux/sandboxing.md - - Windows: - https://chromium.googlesource.com/chromium/src/+/HEAD/docs/design/sandbox.md - - FAQ (Windows-centric): - https://chromium.googlesource.com/chromium/src/+/HEAD/docs/design/sandbox_faq.md + + - https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux/sandboxing.md[Linux] + - https://chromium.googlesource.com/chromium/src/+/HEAD/docs/design/sandbox.md[Windows] + - https://chromium.googlesource.com/chromium/src/+/HEAD/docs/design/sandbox_faq.md[FAQ (Windows-centric)] + # yamllint enable rule:line-length qt.highdpi: type: Bool |