Changelog
io.Connect Desktop 9.15
Release date: 14.07.2026
| Components | Version |
|---|---|
| Electron | 43.1.0 |
| Chromium | 150.0.7871.47 |
| Node.js | 24.18.0 |
The following libraries are bundled with io.Connect Desktop 9.15 and will be used for auto injection:
| Injected Library | Version |
|---|---|
@interopio/desktop |
6.17 |
@interopio/fdc3 |
2.7 |
New Features
Transparency & Hardware Acceleration
By design, the Workspaces App and the Web Group App web pages are positioned on top of the app windows participating in the respective Workspace or web group. This requires the platform to ensure that the app windows below the web pages remain visible and can receive mouse events.
By default, hardware acceleration is disabled and the Workspaces App and the Web Group App web pages are rendered in software mode with true per-pixel transparency. This means that the app window areas in the respective web page are genuinely transparent - the app windows positioned below the Workspaces App and the Web Group App web pages are visible and receive mouse events directly.
When hardware acceleration is enabled, however, the platform must cut the app window areas out of the Workspaces App and the Web Group App web pages so that the app windows below the web page remain visible and can receive mouse events. As a result, any custom popups (menus, panels, overlays) displayed from the Workspaces App and the Web Group App web pages over the app windows may be cut together with the app window area.
To ensure that custom popups are displayed and function properly in your Workspaces App and Web Group App, you can now use the
"mode"property of the"transparency"object under the"hardwareAcceleration"property of the"windowManagement"top-level key in thesystem.jsonsystem configuration file of io.Connect Desktop. This setting is designed to be used in combination with the-webkit-app-regionCSS property, which you can use to define transparent and opaque areas in your custom elements and instruct the platform to treat them as such.The
"mode"property accepts"UseRegions"(default) and"UseAppRegions"as values.
"UseRegions"is the default value, which instructs the platform to attempt to automatically determine and cut out the app window areas from the respective web pages. This may lead to undesirable behavior when custom popups are displayed over the app windows, as the platform may cut out the popup together with the app window area.When hardware acceleration is enabled, it's highly recommended to set the
"mode"property to"UseAppRegions", which will allow you to instruct the platform to honor the transparent and opaque areas defined via the-webkit-app-regionCSS property and use this information to determine which areas of the respective web pages to cut out to reveal the app windows positioned below:{ "windowManagement": { "hardwareAcceleration": { "enabled": true, "transparency": { "mode": "UseAppRegions" } } } }⚠️ Note that the
"UseAppRegions"mode requires@interopio/workspaces-ui-reactversion 4.5.1 or later and@interopio/groups-ui-react4.5.1 or later for the Workspaces App and the Web Group App respectively.The following example demonstrates how to use the
-webkit-app-regionCSS property to define transparent and opaque areas in a custom element:/* This area will be cut so the app window below will be visible and will be able to receive mouse events. */ .app-window-area { /* The `-webkit-app-region` CSS property controls only how the platform will treat the element, not its visual transparency or opacity. To make the element visually transparent, you still have to set its background as transparent. */ background-color: transparent; -webkit-app-region: transparent; } /* This area will be opaque, making the custom popup visible and clickable above the app windows. */ .my-custom-popup { background-color: grey; -webkit-app-region: opaque; }⚠️ Note that the
-webkit-app-regionproperty isn't inheritable, so you must explicitly mark all relevant elements with it.⚠️ Note that for the elements marked with
-webkit-app-region: transparentor-webkit-app-region: opaqueto be visually transparent or opaque, you still need to apply standard CSS for background color and opacity. It's highly recommended to always keep all empty areas that are displayed over the app windows visually transparent - this will ensure consistent behavior when hardware acceleration is enabled and also when using software rendering (e.g., when hardware acceleration is unavailable on the user machine).
Improvements & Bug Fixes
Upgraded to Electron 43.1.0 (Chromium 150).
Improved handling of HTML popup controls in always-on-top windows in window groups.
Improved the resilience of the performance metrics collector to prevent crashes when capturing a snapshot before initialization.
Fixed an issue related to focusing the already running platform instance in custom platform builds when the user attempts to launch a new platform instance.