Engine 6.11.2-16

QtWebEngine 6.11.2 with Omaweb's patch series applied, for Linux x86_64 and aarch64.

This is the engine Omaweb runs on, and it is a modified QtWebEngine. It installs into /usr/lib/omaweb and does not replace the distribution's qt6-webengine, so every other Qt application on the machine keeps the engine it had.

What changed since engine-6.11.2-15. Still QtWebEngine 6.11.2 on Chromium 140.0.7339.225, now with thirty-three patches instead of twenty-nine, and x86_64 is now built against Qt 6.12.0, as aarch64 already was. No security fix comes with this release.

• 0030, a clipboard write during a gesture is granted (Omaweb's #745). Blink asks for a sanitized write only when a page writes text or a known image format during a click or a key press, and Chrome grants it without asking. Qt asked about every copy button, or allowed copying with no gesture at all. It now grants the sanitized write as Chrome does, and a read still asks.
• 0031, an extension's clipboardRead and clipboardWrite are answered (#745). The renderer now answers from the extension running the script, as Chrome does, so a password manager's offscreen document can copy with no view to ask from.
• 0032, an offscreen document can select text (#745). The first copy from a password manager's offscreen document took the browser down, because the selection reached for a view delegate that document doesn't have. Stock QtWebEngine 6.11.2 crashes the same way.
• 0033, every page has chrome.app, chrome.csi and chrome.loadTimes (#766). Chrome's renderer defines all three, and Google's sign-in turns away a Chrome-like browser without chrome.app (rrk=46). They are now Chrome's own: chrome.app comes from Chrome's app schema and AppHooksDelegate, and csi and loadTimes from Chrome's v8 extension, so their functions read [native code]. chrome.app.installState() answers not_installed.

Each package names the Qt it was built against. The engine uses Qt's private API, so it runs on the Qt it was built against or a newer one. Each package's qt6-base and qt6-declarative floor is that Qt, now 6.12.0, and the module's version is pinned to 6.11.2.

Corresponding source. The base is Qt's released qtwebengine-everywhere-src-6.11.2.tar.xz, which carries the Chromium tree it builds. The changes are the thirty-three patches in patches/ of omaweb-qtwebengine-patches at 93d8d47, each a single commit with its own reasoning, and on x86_64 toolchain/clang.patch, which changes how the engine is compiled and not what its code does. packaging/MODIFICATIONS.md in the package says the same and ships with it, alongside the LGPL-3.0 text and Chromium's own notice.

The signed copy lives in Omaweb's pacman repository, which is where a reader gets it. The packages here are unsigned, and they are the artifacts the publishing workflow signs. omaweb-qtwebengine-6.11.2-x86_64.tar.zst and omaweb-qtwebengine-6.11.2-aarch64.tar.zst are the install trees the packages were made from.

What it was tested against.

• x86_64 was built against Qt 6.12.0 from Omarchy's stable mirror, with clang 23, LLD, ThinLTO and Chrome's PGO profile in an Arch container. It is the -15 tree with the four new patches applied, "29 already applied, 4 more, no conflicts". The move from clang 22 to 23 rebuilt all of it. It depends on qt6-base>=6.12.0.
• verify-x86_64.txt is that build's gate. It found a font to draw test pages in and V8 compiled with its write barriers, then passed 63 of 63, 10 of 10, 3 of 3, 9 of 9, 3 of 3, 7 of 7 and 13 of 13. The 7 are the page cases, 0033's among them, and the 13 are 0030's clipboard cases.
• The x86_64 package was installed in a fresh Arch container on the stable mirror, and Omaweb's engine contract suite, built against it, passed 261 of 261. That includes the case that reads window.chrome in a page and its frames.
• aarch64 was built against Arch Linux ARM's Qt 6.12.0 with GCC 16.1.1 in an Arch Linux ARM container. It is the -15 tree with the four new patches applied, "29 already applied, 4 more, no conflicts". It depends on qt6-base>=6.12.0.
• verify-aarch64.txt is that build's gate, with the same sections as x86_64's passing in full: a font found, V8 with its write barriers, then 63 of 63, 10 of 10, 3 of 3, 9 of 9, 3 of 3, 7 of 7 and 13 of 13. Its first run had no font in the container, so Blink stopped the renderer and three clipboard cases failed. villekivela/omaweb-qtwebengine-patches#29 installs a font in the build container and has the gate count them first.
• The aarch64 package was installed in a fresh Arch Linux ARM container, and Omaweb's engine contract suite, built against it, passed 261 of 261, the window.chrome case among them.
• Neither container had a stock engine, so the stock comparison was skipped.