Engine 6.11.2-15

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-14. Still QtWebEngine 6.11.2 on Chromium 140.0.7339.225, now with twenty-nine patches instead of twenty-six. No security fix comes with this release.

• 0027, a page's SVG icon ranks above its raster ones (Omaweb's #700). chatgpt.com declares a black ICO for any size ahead of an SVG that follows prefers-color-scheme, and Chromium preferred the ICO's exact frames, so the tab showed a black mark under a dark theme. A small icon is now tried from the page's SVG first, and the raster is shown only when the SVG can't be fetched. Touch icons keep their ranking.
• 0028, a page is told what its passkeys can reach without Bluetooth (#711). The engine is built without BlueZ, and PublicKeyCredential.getClientCapabilities() waited for a Bluetooth adapter that never came, so the promise never settled. The engine now says it has no Bluetooth LE, and a page hears: no hybrid transport and no platform authenticator.
• 0029, a push subscription is answered alike in every window (#421). With no push service, PushManager.subscribe() is rejected at once, with "push service not available", in a private profile as in any other. Before, a private profile asked for the notifications permission first, which put a question to the reader that led nowhere and told a site the two apart. Notification.requestPermission() is unchanged.

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.

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-nine patches in patches/ of omaweb-qtwebengine-patches at a8932b3, 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, with clang, LLD, ThinLTO and Chrome's PGO profile in an Arch container, as an incremental build of the -14 tree with the three new patches applied: "26 already applied, 3 more, no conflicts". It depends on qt6-base>=6.11.2.
• verify-x86_64.txt is that build's gate. It found V8 compiled with its write barriers, then passed 61 of 61, 10 of 10, 3 of 3, 9 of 9, 3 of 3 and 6 of 6, the last being 0028's and 0029's cases.
• aarch64 was built against Arch Linux ARM's Qt 6.12.0 with GCC, incrementally on the -14 tree, and verify-aarch64.txt is its gate, with the same sections passing in full.
• Neither container had a stock engine, so the stock comparison was skipped on both.
• A real USB security key hasn't signed in on this engine. 0028 changes the Bluetooth answer the security key request also reads, and its tests cover only what a page is told.