Qt WebEngine Platform Notes | Qt WebEngine 5.9

Qt 5.9 | Qt WebEngine | Qt WebEngine Platform Notes

Qt 5.9.9 Reference Documentation

# Qt WebEngine Platform Notes

## Building Qt WebEngine from Source

Static builds are not supported.

The requirements for building Qt 5 modules from source are listed separately for each supported platform:

- Qt for Windows - Requirements
- Qt for X11 Requirements
- Qt for macOS - Requirements

In addition, the following tools are required for building the Qt WebEngine module:

- All Platforms
- Windows
- Linux
- macOS

The tests for skipping the Qt WebEngine build are located in the `qtwebengine` repository, in the `tools\qmake\mkspecs` subdirectory. They can be found by searching for `skipBuild`.

### All Platforms

On all platforms, the following tools are required:

- Python 2.7.5 or later. Python 3 is not supported.
- Bison, Flex
- GPerf

### Windows

On Windows, Visual Studio 2015 or 2017 and Windows 10 SDK are required.

### Linux

On Linux, Clang or GCC version 4.7 or later is required. Supported configurations are `linux-g++` and `linux-clang`.

Qt WebEngine requires `pkg-config` to detect most of its dependencies. The following `pkg-config` files are required:

- `dbus-1`
- `fontconfig`

If Qt was configured for `xcb`, the following `pkg-config` files are also required:

- `libdrm`
- `xcomposite`
- `xcursor`
- `xi`
- `xrandr`
- `xscrnsaver`
- `xtst`

Further, development packages for `khr` and `libcap` need to be installed.

### macOS

On macOS, the following are required:

- macOS 10.9 or later
- Xcode 5.1 or later
- macOS 10.10 SDK or later

Note: Qt WebEngine cannot be built for the 32-bit mode of macOS (using the `macx-clang-32` `mkspec`).

## Mac App Store Compatibility

Applications using Qt WebEngine are not compatible with the Mac App Store, because:

- The Chromium part of the code uses several private API methods, which are prohibited by the App Store.
- Applications submitted to the App Store must be code-signed with the App Sandbox feature enabled. The App Sandbox feature interferes with Chromium's own sandbox initialization, which results in Chromium not being properly initialized. This also ties in with the private API usage. Furthermore, standalone Chromium itself is not officially tested with the App Sandbox enabled, and even if work is done to bypass the App Store's restrictions, that would not guarantee correct behavior of the library.

## macOS Airplay Support on MacBooks with Dual GPUs

To make Qt WebEngine work correctly when streaming to an AppleTV from a MacBook that supports GPU switching, it is important to add the `NSSupportsAutomaticGraphicsSwitching` option to the application Info.plist file, with the value set to `YES`. Otherwise rendering issues might occur when creating new web engine view instances after Airplay is switched on or off.

## Default QSurfaceFormat OpenGL Profile Support

If a new default QSurfaceFormat with a modified OpenGL profile has to be set, it should be set before the application instance is declared, to make sure that all created OpenGL contexts use the same OpenGL profile.

On macOS, if the default QSurfaceFormat is set after the application instance, the application will exit with qFatal(), and print a message that the default QSurfaceFormat should be set before the application instance.

## Sandboxing Support

Qt WebEngine provides out-of-the-box sandboxing support for Chromium render processes on Linux and macOS. Sandboxing is currently not supported on Windows due to a limitation in how the sandbox is set up and how it interacts with the host process provided by the Qt WebEngine libraries.

On macOS, there are no special requirements for enabling sandbox support.

On Linux, the kernel has to support the anonymous namespaces feature (kernel version >= 3.8) and seccomp-bpf feature (kernel version >= 3.5). Setuid sandboxes are not supported and are thus disabled.

To explicitly disable sandboxing, the `QTWEBENGINE_DISABLE_SANDBOX` environment variable can be set to 1 or alternatively the `--no-sandbox` command line argument can be passed to the user application executable.

## Accessibility and Performance

Qt WebEngine enables accessibility support for web pages when the following conditions are met:

- Qt Core is configured and built with accessibility support enabled.
- The QPA plugin is notified by the operating system that accessibility should be activated. This happens for example when using a screen reader application on Windows or VoiceOver on macOS.

Due to some limitations, the Linux QPA plugin almost always reports that accessibility should be activated. On big HTML pages, this can cause a significant slowdown in rendering speed.

Because of that, from Qt 5.9 onwards, Qt WebEngine accessibility support is disabled by default on Linux. It can be re-enabled by setting the `QTWEBENGINE_ENABLE_LINUX_ACCESSIBILITY` environment variable to a non-empty value.

## Popups in Fullscreen Applications on Windows

Because of a limitation in the Windows compositor, applications that show a fullscreen web engine view will not properly display popups or other top-level windows. The reason and workaround for the issue can be found at Fullscreen OpenGL Based Windows and QWindowsWindowFunctions::setHasBorderInFullScreen.