Compatibility Report

JadeView currently supports two major desktop platforms, Windows and Linux, and provides a consistent C API:

• Windows: rendered with Microsoft Edge WebView2;
• Linux: rendered with GTK3 + WebKitGTK.

The compatibility details for each platform are described below.

Windows

JadeView has been thoroughly tested on Windows to ensure stable operation across a wide range of Windows environments.

System Requirements

Minimum Configuration

Recommended Configuration

Tested Operating Systems

Rendering Engine and Browser Compatibility

On Windows, JadeView uses Microsoft Edge WebView2 as its rendering engine, and therefore shares the same compatibility characteristics as the Edge browser.

Linux

JadeView already supports Linux: core capabilities such as windows, WebView rendering, custom title bars, library-level resizing, and bidirectional IPC all work as expected.

Runtime Requirements

The Linux build libJadeView.so is based on tao + wry and renders with GTK3 + WebKitGTK 4.1. Its rendering core is WebKit (the same family as Safari), so feature support follows WebKit and differs slightly from Chromium. Running it requires:

Tested / Compatible Distributions

The hard criterion for compatibility is whether the system can provide WebKitGTK 4.1 (soup3) — older distributions only ship 4.0 (soup2), which is not compatible.

Rule of thumb: mainstream distributions released in 2022 or later generally work; older LTS releases from around 2020 do not.

Supported Features

• ✅ Window creation, WebView rendering (WebKitGTK), custom jade:// protocol and asset service paths
• ✅ Frameless window + HTML custom title bar: drag to move, double-click to maximize/restore, minimize/maximize/close buttons
• ✅ Library-level edge/corner resizing: equivalent to the Windows resizing experience, with resize cursors
• ✅ Bidirectional IPC: page window.jade.invoke() ↔ Rust, and Rust can also proactively push back to JavaScript
• ✅ Window operations: title, size, position, show/hide, focus, maximize, minimize, fullscreen, always-on-top, etc.
• ✅ System language, clipboard, network time (pure Rust NTP)
• ✅ Pure Rust subsystems are platform-independent: encryption/decryption, JAPK signing/decryption, asar asset packages

Display Backend (X11 / Wayland)

• X11 (recommended): windows, input, and resizing all work normally; global hotkeys can also only be implemented on X11.
• Wayland: windows and rendering work, but global hotkeys are unavailable (protocol limitation) and the client cannot set an absolute window position (determined by the compositor). If you encounter input issues, you can set GDK_BACKEND=x11 to go through Xwayland.

Running Under WSL2 (WSLg)

WSL2 (including WSLg) can run GUIs directly for development / validation. The following environment variables need to be set (a real Linux desktop usually does not need them):

export GDK_BACKEND=x11                              # Wayland input issues, switch to X11
export WEBKIT_DISABLE_SANDBOX_THIS_IS_DANGEROUS=1   # WSL has no user namespace, otherwise the renderer process won't start
export WEBKIT_DISABLE_DMABUF_RENDERER=1             # Disable DMABUF to avoid a black screen
# Chinese fonts: sudo apt install -y fonts-wqy-zenhei

FAQ

Q: Why doesn't it run on Windows 7?

A: On Windows, JadeView is based on WebView2 technology, which only supports Windows 10 1809 and later.

Q: How do I check the WebView2 Runtime version?

A: You can check it with the following command:

reg query "HKLM\SOFTWARE\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}" /v pv

Q: What if I can't download the WebView2 Runtime?

A: You can download and install it manually:

1. Visit the WebView2 Runtime download page
2. Download the latest Evergreen Bootstrapper
3. Run the installer

Q: Why won't my Linux distribution run it?

A: The most common cause is that the system lacks WebKitGTK 4.1 (soup3). Older distributions (such as Ubuntu 20.04) only provide 4.0 (soup2), which is not compatible. Please upgrade to a mainstream distribution from 2022 or later, or install libwebkit2gtk-4.1-0 yourself. If Chinese characters render as boxes, you need to install CJK fonts.

Compatibility Testing Tools

We use the following tools and methods for compatibility testing:

• Automated testing: UI automation testing with Selenium and Playwright
• Manual testing: manual testing on multiple physical devices and virtual machines
• Performance testing: performance analysis with Lighthouse and Chrome DevTools
• Stability testing: 24/7 continuous operation testing

Getting Support

If you run into compatibility issues, please:

1. Check whether your system meets the runtime requirements for the corresponding platform
2. On Windows, make sure the latest version of the WebView2 Runtime is installed; on Linux, make sure WebKitGTK 4.1 is installed
3. See the FAQ
4. Submit a GitHub Issue