Users don’t compare your embedded browser to “other embedded browsers”. They compare it to Chrome.

And that’s exactly where many desktop applications get stuck: the page renders fine, but the experience doesn’t feel like a real browser.

Popups behave differently. UI flows feel off. Some interactions look “almost right” — but not polished enough for modern web applications and modern user expectations.

Chrome Style Features is our answer: a set of enhancements in Equo Chromium designed to bring a more authentic Chrome-like experience to embedded browsers — while keeping your SWT, Swing, or Standalone UI fully in control.

From “It Renders” to “It Feels Right”

Embedding Chromium used to be about rendering HTML. Today it's about behavior. Modern web applications expect real browser UX — the same windowing semantics, the same popup behavior, the same polished flows users already trust in Chrome. Chrome Style targets exactly that layer, turning a web view into a browser-grade experience.

What You Get?

This is not a theme. Not a skin. Not a CSS tweak. It focuses on real browser UX behaviors that dramatically improve how your embedded web content behaves inside a desktop application.

Extensions: A Real Competitive Advantage

Here's where it becomes a game-changer.

A lot of embedded browsers can render what users do in Chrome. Very few can realistically support what users bring to Chrome: extensions.

Extensions are no longer niche. They're central to modern workflows: password managers, identity tools, wallets, enterprise security add-ons, productivity helpers, internal toolchains — and more.

Chrome Style pushes Equo Chromium closer to the environment these extensions expect — moving your application from embedding web pages to embedding the Chrome ecosystem. This doesn't replace your product UI — it upgrades the embedded browser layer, so extension-driven workflows feel far more natural and reliable.

Popups that behave like Chrome

Popups are one of the biggest sources of "works in Chrome but not in our application" problems.

With Chrome Style, pop-up flows behave more like users expect from Chrome:

More consistent focus/activation behavior.

More natural window semantics.

Better alignment with real-world web application workflows.

The result is fewer edge cases, fewer workarounds, and fewer compatibility issues to maintain.

A more native, polished browser experience

Chrome Style brings a real browser feel to your product. UI interactions are smoother, web-driven flows are handled more consistently, and behavior aligns more closely with Chrome's model. When your product embeds complex web applications — auth flows, multi-window experiences, "open in new window" patterns — these details are what separate a polished product from one that just renders pages.

Better compatibility with modern web tooling

Many workflows today depend on browser-driven UX patterns — including toolchains and add-ons that assume a Chrome-like environment. Chrome Style is built to support these expectations, so your embedded experience is closer to what modern web applications are designed for in the first place.

Standalone: Chrome-Grade Behavior, Fully Under Your Control

In Standalone mode, Chrome Style delivers the richest browser-grade experience available in Equo Chromium — extension support, Chrome-style popup flows, browser-oriented workflows, and support for Client-Side Decorations (CSD), so teams can shape the browser window as part of the product experience itself.

This makes Standalone especially compelling for dashboards, portals, internal tools, and web-first products that want browser-grade behavior without giving up control over application identity, window appearance, and overall UX.

SWT and Swing: Extensions + Power Features via Context Menu

For SWT and Swing, Chrome Style focuses on what matters most in embedded toolkits:

Extension support, designed to enable real extension-driven workflows.

Browser-grade actions exposed through the context menu, giving users access to key features without requiring a full Chrome-style shell.

This approach keeps your SWT/Swing UI intact while upgrading the browser layer where it counts. And it doesn't stop here: we're working toward enabling deeper customization of UI elements over time, so teams can progressively shape the experience while keeping the Chrome-grade foundation.

One Experience Across SWT, Swing, and Standalone

A major goal of Equo Chromium is predictability: what works in one toolkit shouldn't become a special case in another. Chrome Style is designed to elevate the embedded experience without forcing you to rewrite your UI or adopt a "full browser shell" approach.

You keep:

Your native UI (menus, layout, docking, custom toolbars).

Your application identity and product design.

Your integration architecture.

And you gain:

A more Chrome-like behavior layer for modern web content.

A stronger foundation for extension compatibility.

A more "real browser" feel across your desktop stack.

Why This Matters for Modernization

Most modernization projects underestimate one thing: rendering is easy, behavior is hard. Users don't just want the page to load — they want it to behave exactly as it does in Chrome.

Chrome Style helps close that gap — making your application feel more modern, more stable, and more compatible with real-world web UX patterns, including the workflows your users already rely on through extensions.

Want to bring Chrome-grade behavior to your desktop application?

Whether you're modernizing a legacy product, building a new desktop shell, or supporting extension-driven workflows, the right approach depends on your stack and constraints. The Equo team works directly with development teams to evaluate what Chrome Style unlocks for their specific application. Get in touch, and we'll help you figure out the right path forward.