What's in this update

This month we're covering the latest releases of Equo Chromium v138 and v144, and a big announcement: Equo is heading to Java Forum Stuttgart 2026 as a sponsor.

Both versions received two rounds of shared improvements this month, highlighted together to avoid repetition. Each also ships version-specific additions, detailed below.

---

Equo is heading to Java Forum Stuttgart 2026

Equo is sponsoring Java Forum Stuttgart 2026, joining one of the most active Java communities in Europe as both a sponsor and an exhibitor.

Java Forum Stuttgart brings together a community where Eclipse RCP, SWT, and Swing applications are still very much in active use, and still very much worth modernizing. It's exactly the kind of event where we get to see, firsthand, the mission-critical applications our products were built for.

If you're attending and maintain a mission-critical Eclipse RCP, SWT, or Swing desktop application, bring it to our booth on July 9. We'll show it evolving live: a modern UX on the desktop, or the same application running in a browser, without a single rewrite.

---

Equo Chromium: Shared improvements — v138 and v144

New subscribe() event and Standalone capabilities

Both versions now support a new subscribe().onBeforeClose() event, letting applications react the moment a browser closes. Standalone mode also gained non-blocking behavior on Mac through ChromiumBrowser.pumpOnce(), along with support for isolated browser instances in windowless mode, giving teams more control when building lightweight, embedded browser experiences.

Wayland and launcher improvements

A fix now forces XWayland to prevent browser clipping on Wayland for Swing applications, and a separate fix prevents the application from closing unexpectedly on Standalone Wayland. Both versions also simplified the Equo Chromium launcher reference by using an unversioned symlink, making upgrades more predictable going forward.

Security updates

Both versions include security updates backported from their respective long-term support lines of Chromium, keeping production applications protected without requiring any action from your team.

Input, display, and platform fixes

The latest releases (v144.0.7 and v138.0.18) bring a focused set of fixes across input, display, and platform-specific behavior. IME input for CJK languages (Korean, Chinese, Japanese, and others) now works correctly on Linux/X11, and a separate issue that prevented typing in browser text inputs on Wayland is resolved. On macOS, hover state now restores correctly after deminiaturizing a window when using Client-Side Decorations. Wayland detection on WSL has been improved, and a browser scaling issue on multi-monitor setups with Eclipse 4.36 and later on Windows is now fixed.

---

What's new in v144

v144 resolved an issue with setUrl() when using custom headers, which was causing a blank screen on initial load. Teams relying on custom headers for navigation can expect more consistent behavior.

The latest release also brings restricted iframes support to SWT Evolve on v144, an addition that was previously available on v138 only.

---

What's new in v138

v138's June cycle focused on stability and parity, alongside one targeted addition: restricted iframes are now allowed in SWT Evolve. Outside of that, this release brings v138 fully in line with the shared improvements above, keeping it just as dependable for the teams who rely on it in production.

---

Full release notes

For the complete list of changes, patch details, and platform requirements:

Equo Chromium v144 release notes

Equo Chromium v138 release notes

---

Consistent progress, now in person

Equo Chromium keeps shipping the kind of incremental, dependable progress that keeps mission-critical applications running smoothly. This month's updates land across both v138 and v144, with security, stability, and small but meaningful new capabilities for teams building with Standalone mode.

And this July, that same commitment takes us beyond the release notes. At Java Forum Stuttgart 2026, we're looking forward to meeting the community building with Eclipse RCP, SWT, and Swing in person and showing firsthand what modernization without rewrites looks like.

More is on the way. Thank you for being part of this journey.

---

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

Thank you for choosing Equo!