Hi everyone,

This January Product Update is focused entirely on Equo Chromium. The theme across the latest releases is simple: better control in Standalone mode, smoother developer workflows, fewer integration frictions when embedding Chromium into Java desktop applications, and continued stability and security improvements.

What’s new in versions 128 & 138

v138

Standalone UX upgrades: Full window control (size/bounds/position + maximize/minimize) plus F12 → DevTools.

Better Eclipse/SWT integration: option to prevent Chromium from consuming SWT shortcuts.

Operational controls for enterprise setups: Runtime proxy updates + improved auth flow (with an option to suppress auth dialogs).

v128

Standalone parity improvements: window control features on the 128 line (size/bounds/position + maximize/minimize).

Enterprise-friendly networking: runtime proxy reconfiguration + improved auth handling (and optional suppression of auth dialogs).

Windows DPI/scaling fixes: continued improvements (including Eclipse 4.38 on Windows).

Fixes & improvements on versions 128 & 138

Proxy/auth reliability: improved Java Authenticator handling + cleaner proxy state (PAC cleared when proxy settings are removed).

Scaling consistency: better DPI/device-scale behavior (notably when switching monitors on Windows) + several scaling fixes.

Linux desktop improvements: GTK4 support and Wayland rendering fixes, including corrected browser layout and parent-window embedding behavior.

Security & packaging maintenance: ongoing updates and signing fixes.

Want the full details?

If you’d like the complete list of changes (including all patch notes and version requirements), you can review the release notes here:

Equo Chromium v138 release notes

Equo Chromium v128 release notes

Final thoughts: what this means for your product

These patch updates are primarily about making Equo Chromium easier to adopt and maintain in real Java desktop applications. They improve the day-to-day experience of shipping embedded web UI on desktop: smoother workflows when developing and debugging, fewer integration frictions when Chromium is embedded alongside existing UI behavior, and continued cross-platform refinements so applications behave more consistently across common desktop environments. In short, the focus is practical: reduce overhead for teams integrating Chromium, and make ongoing updates simpler and more predictable over time.

For any questions or assistance, feel free to reach out at contact@equo.dev.

Thank you for choosing Equo!