Engine 6.11.2-14

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-12. Still QtWebEngine 6.11.2 on Chromium 140.0.7339.225, now with twenty-six patches instead of twenty-four. No security fix comes with this release. Release -13 was built along the way and never published.

• 0025, a favicon is drawn again when the colour scheme changes (Omaweb's #700). A page is told a colour scheme the application changes while it runs, the icon of each page on show is drawn again under it, and every drawing the profile keeps is marked out of date, so another page draws its icon afresh on its next visit. An icon that follows prefers-color-scheme, such as chatgpt.com's, now follows a live Omarchy theme change.
• 0026, the application can say a page is a tab (#694).

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, and the module's version is pinned to 6.11.2 (omaweb-qtwebengine-patches#21).

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 twenty-six patches in patches/ of omaweb-qtwebengine-patches at 3124a21, 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.

What it was tested against.

• x86_64 was built against Qt 6.11.2 from Omarchy's stable mirror (qt6-base 6.11.2-3), with clang, LLD, ThinLTO and Chrome's PGO profile in an Arch container on an Intel Core Ultra X7 358H, as an incremental build of a tree the series' own refresh.sh extended: "25 already applied, 1 more, no conflicts". Its libraries are .so.6.11.2, and it depends on qt6-base>=6.11.2 and qt6-declarative>=6.11.2.
• verify-x86_64.txt is that build's gate. It read V8's ninja file and found it compiled with its write barriers, then passed 61 of 61, 10 of 10, 3 of 3, 6 of 6 and 3 of 3. The container had no stock engine, so the stock comparison was skipped.
• aarch64 is built separately, against Arch Linux ARM's Qt 6.12.0, and joins this release with its own gate.