Chromium/zh: Difference between revisions

In Chromium, policy settings are accessible via {{Ic|chrome://policy}}. They allow the user to change enterprise policies affecting things like

* Creating webapps when the browser is installed

* Finding and downloading browser extensions automatically

* Enabling or disabling the dinosaur game when the device is offline

* Disable screenshots to be taken with browser extensions

* Block all downloads from the browser (if you want to do that for some reason)

* and more!

A full list of policies can be found at [https://chromeenterprise.google/policies/ Chrome Enterprise Policy List & Management].

By default NixOS provides a few policies that can be enabled directly, a simple example is given below to understand how these are implemented

* {{Ic|homepageLocation}} option allows you to set the site that the homepage will open on

* {{Ic|extensions}} allows for the download of extensions directly in the browser through a simple list of the extension ID's that can be obtained from the [https://chromewebstore.google.com/ Chrome Web Store] by opening an extension page and copying the last part of the URL

** In the example however there is another component, the download source from which the extensions will be downloaded

** The URL provided in the list is the link that is used by google for managing, checking and updating extensions

** So the method of just placing the extension ID can work like this: {{Ic|"fnpbehpgglbfnpimkachnpnecjncndgm"}}

** But just in case that method does not automatically function the second method is shown above, where you place {{Ic|;}} and then the URL {{Ic|https //clients2.google.com/service/update2/crx}} to explicitly tell NixOS where to install the extension from

* There are many more options that are natively supported and you can learn about them through {{Ic|man configuration.nix}}

* But as shown above there is also an {{Ic|extraOpts}} option and that is used for policies that are not supported for direct setup, such as the policy to install web-apps

There are hundreds of policies in Chromium based browsers, and not all have direct methods to set them. The {{Ic|extraOpts}} option allows for the declaration of all the other policies.

There is no single place to find all Chromium policies, but these are some places to look;

* Commonly used policies are present and documented within {{Ic|man configuration.nix}} under {{Ic|programs.chromium}}.

* You can navigate to {{Ic|chrome://policy}} and enable "Show policies with no value set" to see all available keys. Clicking a policy name opens its specific definition and usage details.

* The most up to date policies for Chromium are available in the [https://source.chromium.org/chromium/chromium/src/+/main:chrome/common/pref_names.h source code.]

In some cases, {{ic|chrome://gpu}} will show Video Decode as enabled, but Video Acceleration Information as blank, with {{ic|chrome://media-internals}} using the FFmpeg Video Decoder (software decoding). If this happens, try to enable the following features:

<div lang="en" dir="ltr" class="mw-content-ltr">

== Enabling native Wayland support ==

You can enable native Wayland support in all Chromium based and most Electron apps by setting the `NIXOS_OZONE_WL` environment variable to `1`.

<div lang="en" dir="ltr" class="mw-content-ltr">

== Enabling DRM (Widevine support) ==

By default, {{nixos:package|chromium}} does not support playing DRM protected media. However, there is a build time flag to include the proprietary Widevine blob from Nixpkgs:

<div lang="en" dir="ltr" class="mw-content-ltr">

== KeePassXC support in Flatpak ==

To enable browser integration between KeePassXC and Chromium-based browsers when running in Flatpak, configure the following filesystem access:

<div lang="en" dir="ltr" class="mw-content-ltr">

== Using libc memory allocator ==

Chromium may not work when an alternative system-wide memory allocator like scudo is used. To use libc on Chromium, the following firejail wrap is required: