TECH Signal 404
Union: Summer 2026 Update
↗
Illustration only Photo by Ivan Bandura on Unsplash
KDE's Union style engine, which aims to unify Qt and KDE application styling, shipped its first release in Plasma 6.7 as an opt-in option and is undergoing significant architectural changes ahead of a potential broader rollout in Plasma 6.8.
If you build or ship Qt-based applications, Union represents a future where QtQuick and Qt Widgets styling converge under a single engine rather than relying on separate mechanisms. The recent overhaul of style loading breaks existing custom styles but promises a more robust format going forward, so anyone maintaining a KDE/Qt style will need to migrate. The project is still in a transitional state, so production reliance on Union is premature.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Union is now selectable from System Settings in Plasma 6.7 via a proxy style mechanism, but only QtQuick applications actually use Union for rendering while widgets still fall back to Breeze.
The core style loading system was overhauled, meaning any styles created so far must be converted to a new format that lets each style define its own input format.
Qt Widgets support is in progress with Union now rendering everything directly rather than proxying, but it is uncertain whether this work will be ready for Plasma 6.8.
THE READ
What elseif makes of it.
Union's first appearance in Plasma 6.7 is deliberately limited. The team originally wanted Union as the default for QtQuick applications but found that infeasible, settling on a proxy-style approach that lets users opt in from System Settings. When selected, QtQuick applications use Union after a restart, while traditional widgets still delegate to the Breeze style. This makes the current release a testing surface rather than a production default, and the authors explicitly call the selection mechanism a short-term solution.
The most consequential change for style developers is the overhaul of Union's core style loading. Styles now define their own input format, which the article says reduces code, improves robustness, and simplifies future backward compatibility. The trade-off is immediate: every existing Union style must be converted to the new format. A new System Settings page for selecting Union styles is being built, alongside a command-line tool for working with styles, but the page is described as a rough first version that will evolve.
Qt Widgets support is the largest remaining technical gap. Akseli Lahtinen is building a proper Qt Widgets style for Union, and the work has progressed far enough that Union now renders widgets directly rather than acting as a proxy. However, the article notes that the QStyle API is poorly documented and aging, which slows development. The team is unsure whether full widgets support will land by Plasma 6.8, though that is the target.
Beyond the core engine, the project is exploring broader style compatibility. There are discussions about porting the Oxygen style to Union to improve its compatibility with QtQuick applications, and a new Ocean style is being built on Union from the start. These efforts suggest Union is intended to eventually replace the current Application Style system entirely, with the existing selection page being demoted or removed once enough Union styles exist.
Because only a single feed carried this item, there is no independent corroboration of the claims or timelines. Engineers who depend on KDE or Qt styling should treat the Plasma 6.8 ambitions as aspirational rather than committed. The practical takeaway for anyone maintaining a Qt or KDE application style is to monitor the Union repository and prepare for format migration, but not to rearchitect production tooling around Union until the widgets support and default-selection story are further along.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER