Benchmarks
JSON โAMD Ryzen 5 5600X ยท AMD 9060XT 16GB ยท 144hz
Loading chartsโฆ
Binary sizes
JSON โProduction executable size (MiB) ยท Lower is smaller.
Linux ยท x86_64 ยท cargo build --profile production --locked ยท LTO ยท 1 codegen unit ยท Stripped ยท Collected .
Loading binary size chartโฆ
Values (16 executables)
| Framework | Executable | Size (MiB) | Bytes |
|---|---|---|---|
| Blinc | blinc-scroll | 15.0683 | 15,800,240 |
| Dioxus Native | dioxus-native-scroll | 17.5522 | 18,404,784 |
| Dioxus Native Vello Hybrid | dioxus-native-vello-hybrid-scroll | 18.6722 | 19,579,184 |
| egui | egui-scroll | 5.5143 | 5,782,128 |
| Floem | floem-scroll | 12.7393 | 13,358,072 |
| Freya | freya-scroll | 24.8357 | 26,042,112 |
| Freya (Optimized) | freya-optimized-scroll | 24.8321 | 26,038,344 |
| GPUI | gpui-scroll | 12.9436 | 13,572,384 |
| GPUI Fast | gpui-fast-scroll | 21.0165 | 22,037,392 |
| Iced | iced-scroll | 8.1722 | 8,569,224 |
| Makepad | makepad-scroll | 5.8069 | 6,088,984 |
| Rune | rune-scroll | 21.7297 | 22,785,256 |
| Slint | slint-scroll | 11.4155 | 11,970,024 |
| Vizia | vizia-scroll | 25.9519 | 27,212,536 |
| Whisker | whisker-scroll | 19.5574 | 20,507,472 |
| zgui | zgui-scroll | 26.3733 | 27,654,384 |
Features
| Feature | Freya | GPUI | Vizia | Iced | egui | Slint | Floem | Dioxus Native | Makepad | GPUI Fast | Rune | zgui | Blinc | Whisker |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Recent downloads | | | | | | | | | | | Not published | | | |
| License | MITMetadata and features describe the inspected development source, not benchmark adapter pins. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Apache-2.0Metadata and features describe the inspected development source, not benchmark adapter pins. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | MITMetadata and features describe the inspected development source, not benchmark adapter pins. main@9231260010d5 ยท reviewed 2026-11-06 Source | MITMetadata and features describe the inspected development source, not benchmark adapter pins. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | MIT OR Apache-2.0Metadata and features describe the inspected development source, not benchmark adapter pins. main@91b5712dd617 ยท reviewed 2026-11-06 Source | GPL-3.0-only OR LicenseRโฆGPL-3.0-only OR LicenseRef-Slint-Royalty-free-2.0 OR LicenseRef-Slint-Software-3.0 Metadata and features describe the inspected development source, not benchmark adapter pins. master@b3be5c22781d ยท reviewed 2026-11-06 Source | MITMetadata and features describe the inspected development source, not benchmark adapter pins. main@1351ffb162fa ยท reviewed 2026-11-06 Source | MIT OR Apache-2.0Metadata and features describe the inspected development source, not benchmark adapter pins. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | MIT OR Apache-2.0Metadata and features describe the inspected development source, not benchmark adapter pins. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Apache-2.0Metadata and features describe the inspected development source, not benchmark adapter pins. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | MITBenchmark dependency and feature citations use the same pinned commit. Linux native windows are exercised by this adapter. Other platform APIs are source-reviewed, not execution-validated here. The agent-oriented contribution workflow is not a quantified declaration of authorship for the existing codebase. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Apache-2.0Metadata, features and the benchmark adapter use the same pinned development commit. Platform capabilities are source-reviewed, not execution-validated here. Creation year uses the repository's first commit date. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Apache-2.0Metadata, feature claims and benchmarks use the same pinned source. Platform claims are source-reviewed, not execution-validated. Creation year uses the repository's first commit date. Latest release is Blinc v0.6.0, published on GitHub. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | MIT OR Apache-2.0Source-reviewed at the same commit pinned by the scroll benchmark. Latest release is whisker-release-20261111.1, published on GitHub. Creation year uses the repository's first commit date. Desktop capabilities are distinguished from mobile and web Hosts. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Creation year | 2022Metadata and features describe the inspected development source, not benchmark adapter pins. First available repository commit: 2022-07-28. This is not necessarily the project start. main@11cd62a248bf ยท reviewed 2026-11-06 Source | 2021Metadata and features describe the inspected development source, not benchmark adapter pins. First available repository commit: 2021-02-20. This is not necessarily the project start. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | 2021Metadata and features describe the inspected development source, not benchmark adapter pins. First available repository commit: 2021-09-17. This is not necessarily the project start. main@9231260010d5 ยท reviewed 2026-11-06 Source | 2019Metadata and features describe the inspected development source, not benchmark adapter pins. First available repository commit: 2019-05-29. This is not necessarily the project start. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | 2018Metadata and features describe the inspected development source, not benchmark adapter pins. First available repository commit: 2018-12-23. This is not necessarily the project start. main@91b5712dd617 ยท reviewed 2026-11-06 Source | 2020Metadata and features describe the inspected development source, not benchmark adapter pins. First available repository commit: 2020-05-04. This is not necessarily the project start. master@b3be5c22781d ยท reviewed 2026-11-06 Source | 2023Metadata and features describe the inspected development source, not benchmark adapter pins. First available repository commit: 2023-01-31. This is not necessarily the project start. main@1351ffb162fa ยท reviewed 2026-11-06 Source | 2023Metadata and features describe the inspected development source, not benchmark adapter pins. First available repository commit: 2023-11-30. This is not necessarily the project start. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | 2025Metadata and features describe the inspected development source, not benchmark adapter pins. First available repository commit: 2025-05-06. This is not necessarily the project start. main@506ec05105b9 ยท reviewed 2026-11-06 Source | 2026Metadata and features describe the inspected development source, not benchmark adapter pins. First available repository commit: 2026-09-22. This is not necessarily the project start. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | 2026Benchmark dependency and feature citations use the same pinned commit. Linux native windows are exercised by this adapter. Other platform APIs are source-reviewed, not execution-validated here. The agent-oriented contribution workflow is not a quantified declaration of authorship for the existing codebase. First available repository commit: 2026-10-22. This is not necessarily the project start. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | 2026Metadata, features and the benchmark adapter use the same pinned development commit. Platform capabilities are source-reviewed, not execution-validated here. Creation year uses the repository's first commit date. First available repository commit: 2026-08-02. This is not necessarily the project start. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | 2022Metadata, feature claims and benchmarks use the same pinned source. Platform claims are source-reviewed, not execution-validated. Creation year uses the repository's first commit date. Latest release is Blinc v0.6.0, published on GitHub. First available repository commit: 2022-04-10. This is not necessarily the project start. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | 2026Source-reviewed at the same commit pinned by the scroll benchmark. Latest release is whisker-release-20261111.1, published on GitHub. Creation year uses the repository's first commit date. Desktop capabilities are distinguished from mobile and web Hosts. First available repository commit: 2026-05-12. This is not necessarily the project start. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Latest release | 2026-11-08Metadata and features describe the inspected development source, not benchmark adapter pins. main@11cd62a248bf ยท reviewed 2026-11-06 Source | 2026-11-04Metadata and features describe the inspected development source, not benchmark adapter pins. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | 2026-04-23Metadata and features describe the inspected development source, not benchmark adapter pins. main@9231260010d5 ยท reviewed 2026-11-06 Source | 2025-12-07Metadata and features describe the inspected development source, not benchmark adapter pins. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | 2026-10-15Metadata and features describe the inspected development source, not benchmark adapter pins. main@91b5712dd617 ยท reviewed 2026-11-06 Source | 2026-09-21Metadata and features describe the inspected development source, not benchmark adapter pins. master@b3be5c22781d ยท reviewed 2026-11-06 Source | 2024-11-15Metadata and features describe the inspected development source, not benchmark adapter pins. main@1351ffb162fa ยท reviewed 2026-11-06 Source | 2026-10-16Metadata and features describe the inspected development source, not benchmark adapter pins. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | 2025-05-13Metadata and features describe the inspected development source, not benchmark adapter pins. main@506ec05105b9 ยท reviewed 2026-11-06 Source | 2026-11-09Metadata and features describe the inspected development source, not benchmark adapter pins. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | UnknownBenchmark dependency and feature citations use the same pinned commit. Linux native windows are exercised by this adapter. Other platform APIs are source-reviewed, not execution-validated here. The agent-oriented contribution workflow is not a quantified declaration of authorship for the existing codebase. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | 2026-10-15Metadata, features and the benchmark adapter use the same pinned development commit. Platform capabilities are source-reviewed, not execution-validated here. Creation year uses the repository's first commit date. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | 2026-11-04Metadata, feature claims and benchmarks use the same pinned source. Platform claims are source-reviewed, not execution-validated. Creation year uses the repository's first commit date. Latest release is Blinc v0.6.0, published on GitHub. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | 2026-11-11Source-reviewed at the same commit pinned by the scroll benchmark. Latest release is whisker-release-20261111.1, published on GitHub. Creation year uses the repository's first commit date. Desktop capabilities are distinguished from mobile and web Hosts. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| AI involvement | AI-assistedAI-assisted. Classification by the site maintainer. 11cd62a248bf ยท reviewed 2026-11-07 | AI-assistedClaude was used for a GPUI list-padding change. 78fde14d124d ยท reviewed 2026-11-07 Source | AI-assistedAI-assisted. Classification by the site maintainer. 9231260010d5 ยท reviewed 2026-11-07 | AI-assistedClaude co-authored an iced_wgpu triangle-index fix. 478c363df6cb ยท reviewed 2026-11-07 Source | AI-assistedClaude co-authored an epaint text-wrapping fix. 91b5712dd617 ยท reviewed 2026-11-07 Source | AI-assistedClaude co-authored a Skia WGPU snapshot-rendering change. bce7351a92bc ยท reviewed 2026-11-07 Source | AI-assistedClaude co-authored native window drag-and-drop changes. 10b706f906fe ยท reviewed 2026-11-07 Source | AI co-developedAI co-developed. Classification by the site maintainer. 61dccec2536e ยท reviewed 2026-11-07 | AI-ledAI-led. Classification by the site maintainer. 0637212218e2 ยท reviewed 2026-11-07 | AI co-developedAI co-developed. Classification by the site maintainer. 80baa3c7cb0f ยท reviewed 2026-11-09 | AI-ledAI-led. Classification by the site maintainer. 2ca5f509e736 ยท reviewed 2026-11-10 | AI-ledAI-led. Classification by the site maintainer. 536dd4949e69 ยท reviewed 2026-11-10 | ||
| State Management | Component signals | Entities | Fine-grained signals | Elm | Immediate mode | Property bindings | Fine-grained signals | Component signals | Events | Entities | Shared state | Fine-grained signals | Component signals | Fine-grained signals |
| Platforms | ||||||||||||||
| Linux | Yes (built-in) Winit desktop shell with Linux X11/Wayland features. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) Linux platform selection includes Wayland and X11 backend features. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) Linux is an explicitly supported desktop target. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Linux is explicitly listed as a supported target. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Linux desktop and embedded Linux are explicitly supported. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) Linux native browser/app shell builds are explicitly listed. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) Linux setup and desktop app execution are documented. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) Linux platform selection includes Wayland and X11 backend features. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Native Winit X11/Wayland shell and Vulkan backend. This benchmark validates real Linux windows. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Native Linux support with Wayland and X11 backends, not execution-validated here. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Documented desktop Winit/WGPU Vulkan backend, not execution-validated here. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) A native Winit/WGPU desktop Host and a separate GTK4 Linux Host are supplied. main@536dd4949e69 ยท reviewed 2026-11-10 Source | ||
| Windows | Yes (built-in) Winit desktop shell includes Windows dependencies and renderer configuration. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) Native Win32 platform implementation is present. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) Windows is an explicitly supported desktop target. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Windows is explicitly listed as a supported target. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Windows is an explicitly supported desktop target. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) Windows native browser/app shell builds are explicitly listed. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) The platform layer contains a Windows backend. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) Native Win32 platform implementation is present. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Windows-specific DirectWrite, WGPU DX12 and AccessKit adapters are present. No Windows execution validation here. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Winit backend supports Windows, not execution-validated here. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Documented WGPU DX12/Vulkan desktop backend, not execution-validated here. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) The shared desktop Host selects Winit and WGPU DX12 on Windows. main@536dd4949e69 ยท reviewed 2026-11-10 Source | ||
| macOS | Yes (built-in) Winit desktop shell and platform renderer selection include macOS. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) Native macOS platform implementation is present. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) macOS is an explicitly supported desktop target. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) macOS is explicitly listed as a supported target. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) macOS is an explicitly supported desktop target. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) macOS native browser/app shell builds are explicitly listed. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) The platform layer contains Apple native backends. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) Native macOS platform implementation is present. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Apple-specific native shell, Metal renderer and accessibility dependencies are present. Not executed here. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Winit backend supports macOS, not execution-validated here. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Documented WGPU Metal desktop backend, not execution-validated here. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) The shared desktop Host selects Winit and WGPU Metal on macOS. main@536dd4949e69 ยท reviewed 2026-11-10 Source | ||
| Web | Yes (built-in) An in-repository web backend exists behind the web feature. Do not assume desktop API or accessibility parity. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Partially (partial) A web platform implementation exists at this commit. This is not a claim of desktop feature or renderer parity. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Unknown Support for Web was not established for this specific backend at the inspected commit. Platform-agnostic dependencies or a sibling renderer are not sufficient evidence, and this is not an unsupported declaration. main@9231260010d5 ยท reviewed 2026-11-06 Source | Partially (partial) The project lists Web support, but this is not a claim that every native shell service or widget feature works identically on Wasm. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Official Eframe supports Wasm/browser applications, with a web demo and backend code. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) The repository includes WebAssembly/browser demos and build integration. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Partially (partial) Wasm-specific dependencies and a WebGPU example exist. Complete desktop/browser API parity is not established. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) Wasm build/run tooling is explicitly documented. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Partially (partial) A web platform implementation exists at this commit. This is not a claim of desktop feature or renderer parity. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Wasm bindings and WebGPU with optional WebGL are present. This adapter does not exercise web output. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Unknown The inspected platform documentation establishes desktop and headless support, not a browser backend. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Partially (partial) WebGPU/WASM backend is explicitly preview and requires a WebGPU-capable browser. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) The Web Host projects retained Rust frames into DOM nodes. main@536dd4949e69 ยท reviewed 2026-11-10 Source | |
| Android | Yes (built-in) An Android integration crate and Android examples exist. Desktop feature parity is not established. main@11cd62a248bf ยท reviewed 2026-11-06 Source | No The platform dispatcher implements iOS, macOS, Windows, Linux/FreeBSD and Web targets, but has no Android implementation. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Unknown Support for Android was not established for this specific backend at the inspected commit. Platform-agnostic dependencies or a sibling renderer are not sufficient evidence, and this is not an unsupported declaration. main@9231260010d5 ยท reviewed 2026-11-06 Source | Unknown Support for Android was not established for this specific backend at the inspected commit. Platform-agnostic dependencies or a sibling renderer are not sufficient evidence, and this is not an unsupported declaration. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Android activity features are provided by the official Eframe integration. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) Android is explicitly supported, with platform-specific setup requirements. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Unknown Support for Android was not established for this specific backend at the inspected commit. Platform-agnostic dependencies or a sibling renderer are not sufficient evidence, and this is not an unsupported declaration. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) Android builds of the Blitz browser shell are listed. This does not prove complete Dioxus Native application/platform parity. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) Android toolchain installation and application execution are documented. main@506ec05105b9 ยท reviewed 2026-11-06 Source | No The platform dispatcher implements iOS, macOS, Windows, Linux/FreeBSD and Web targets, but has no Android implementation. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Unknown No Android support or completeness conclusion is established by this benchmark addition. Target-specific dependency exclusions alone are not proof of support. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Unknown Android application support was not established by this source review. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Native Android NDK backend with WGPU Vulkan is documented, not execution-validated here. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) An Android native-view Host is part of the documented cross-platform architecture. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| iOS | Unknown Support for iOS was not established for this specific backend at the inspected commit. Platform-agnostic dependencies or a sibling renderer are not sufficient evidence, and this is not an unsupported declaration. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Partially (partial) An iOS platform crate and examples/tests exist. The desktop setup guide is not evidence of full mobile parity. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Unknown Support for iOS was not established for this specific backend at the inspected commit. Platform-agnostic dependencies or a sibling renderer are not sufficient evidence, and this is not an unsupported declaration. main@9231260010d5 ยท reviewed 2026-11-06 Source | Unknown Support for iOS was not established for this specific backend at the inspected commit. Platform-agnostic dependencies or a sibling renderer are not sufficient evidence, and this is not an unsupported declaration. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) The eframe changelog records native iOS build fixes, CI coverage, safe-area support and suspend handling. Not execution-validated on an iOS device here. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) iOS is explicitly supported, with Apple toolchain/platform constraints. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Unknown Support for iOS was not established for this specific backend at the inspected commit. Platform-agnostic dependencies or a sibling renderer are not sufficient evidence, and this is not an unsupported declaration. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) The build tool explicitly supports Apple iOS targets. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Partially (partial) An iOS platform crate and examples/tests exist. The desktop setup guide is not evidence of full mobile parity. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Partially (partial) Apple mobile backend paths are described, but desktop tooling and hot editing have separate target restrictions. Not validated on a device here. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Unknown iOS application support was not established by this source review. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Native UIKit/Metal backend is documented, not execution-validated here. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) An iOS UIKit Host is supplied through the native platform distribution. main@536dd4949e69 ยท reviewed 2026-11-10 Source | |
| Rendering | ||||||||||||||
| GPU/software rendering | Yes (built-in) Skia GPU support is feature-gated. The Winit crate also contains software rendering paths. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) Platform selection uses GPU renderers. A generally available CPU software fallback is not established. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) The native shell uses Skia with GPU/windowing integration. General software-renderer parity is not established here. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) WGPU provides GPU rendering and TinySkia provides a software fallback. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Core emits textured triangles. Official GPU renderers are WGPU and Glow, not a built-in general software renderer. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) Skia and FemtoVG provide GPU paths, with a separate CPU software renderer. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) GPU options include Vger, Vello and Skia. TinySkia is documented as the CPU fallback. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) Frontend features select Vello, Vello hybrid, Skia, or CPU Vello/Skia raster output paths. Availability is renderer/feature-dependent and does not describe the older benchmark baseline configuration. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) GPU-accelerated 2D and 3D rendering is explicit. A generally equivalent CPU-only UI renderer was not established. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) Platform selection uses GPU renderers. A generally available CPU software fallback is not established. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Different model Custom GPU rendering through WGPU or native Metal. This source review does not establish a separate production CPU raster backend. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Partially (partial) Retained WGPU and Vello GPU rendering. A software renderer was not established. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Partially (partial) Custom WGPU SDF renderer. A software fallback was not established. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Partially (partial) The desktop Host uses WGPU. Equivalent software-only desktop rendering was not established in this review. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Custom drawing | Yes (built-in) RenderCallback supplies custom drawing through Freya's render context and Skia canvas. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) Canvas exposes prepaint/paint closures, and custom Element implementations can issue paint operations. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) Custom View drawing can access the drawing context and Skia canvas. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Painter exposes custom 2D shapes and paint callbacks. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Partially (partial) Custom drawing can use path/image content and rendering integration hooks. This is not an unrestricted portable Canvas widget on every renderer. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) Canvas gives applications custom 2D painting within the view tree. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Partially (partial) Custom widget hooks are available. They are not equivalent to supporting arbitrary browser Canvas/WebGL APIs. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) The drawing crate exposes custom GPU-oriented drawing primitives. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) Canvas exposes prepaint/paint closures, and custom Element implementations can issue paint operations. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Canvas paths, polygons and stroke primitives have a public API, alongside a custom compositor hook. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Canvas drawing and custom elements are provided by the framework. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Canvas element provides custom paint callbacks. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Partially (partial) Desktop native-element raster callbacks provide custom painting. A portable immediate-mode drawing API was not established. main@536dd4949e69 ยท reviewed 2026-11-10 Source | |
| Images/SVG | Yes (built-in) Native image element, with decoded image data and asset support. main@11cd62a248bf ยท reviewed 2026-11-06 Images sourceSVG: Yes (built-in) SvgViewer uses the Skia SVG rendering path. This is not a complete browser SVG DOM. main@11cd62a248bf ยท reviewed 2026-11-06 SVG source | Yes (built-in) Image elements and image-source loading are included. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Images sourceSVG: Yes (built-in) SVG elements are supported. Do not infer complete browser SVG feature coverage. main@9a8ab54db4f9 ยท reviewed 2026-11-06 SVG source | Yes (built-in) Built-in Image view supports repository image resources. main@9231260010d5 ยท reviewed 2026-11-06 Images sourceSVG: Yes (built-in) Built-in SVG view is present, including the bundled icon use case. main@9231260010d5 ยท reviewed 2026-11-06 SVG source | Yes (built-in) The image widget and image handles are built in. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Images sourceSVG: Yes (built-in) SVG widget/rendering support is supplied. master@8ff48c42b0d5 ยท reviewed 2026-11-06 SVG source | Yes (built-in) Image widget and texture/image-source abstractions are included. Decoding/loaders can require egui_extras features. main@91b5712dd617 ยท reviewed 2026-11-06 Images sourceSVG: Yes (built-in) The official egui_extras SVG loader supports SVG image loading when enabled, rather than a browser SVG DOM. main@91b5712dd617 ยท reviewed 2026-11-06 SVG source | Yes (built-in) Image resources and rendering are built into the core. master@b3be5c22781d ยท reviewed 2026-11-06 Images sourceSVG: Yes (built-in) SVG image loading/rendering is implemented. SVG script/DOM parity is not implied. master@b3be5c22781d ยท reviewed 2026-11-06 SVG source | Yes (built-in) An image view and image sources are supplied. main@1351ffb162fa ยท reviewed 2026-11-06 Images sourceSVG: Yes (built-in) SVG view rendering is included. main@1351ffb162fa ยท reviewed 2026-11-06 SVG source | Yes (built-in) The paint pipeline renders DOM images and drawing content using the configured rendering abstraction. main@5be96ed0e621 ยท reviewed 2026-11-06 Images sourceSVG: Yes (built-in) Inline SVG handling and repository SVG rendering tests exist. This does not establish complete browser SVG compatibility. main@5be96ed0e621 ยท reviewed 2026-11-06 SVG source | Yes (built-in) Image widgets and image loading/display infrastructure are supplied. main@506ec05105b9 ยท reviewed 2026-11-06 Images sourceSVG: Yes (built-in) SVG widget/drawing support is present in the toolkit. main@506ec05105b9 ยท reviewed 2026-11-06 SVG source | Yes (built-in) Image elements and image-source loading are included. main@4a4a89af7c7f ยท reviewed 2026-11-06 Images sourceSVG: Yes (built-in) SVG elements are supported. Do not infer complete browser SVG feature coverage. main@4a4a89af7c7f ยท reviewed 2026-11-06 SVG source | Yes (built-in) Content-addressed image handles, asynchronous decoding and mip generation. The benchmark loads all ten shared PNG fixtures. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Images sourceSVG: Yes (built-in) The default svg feature uses resvg for SVG and SVGZ image loading. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 SVG source | Yes (built-in) Framework image loading and decoding crate. main@80baa3c7cb0f ยท reviewed 2026-11-09 Images sourceSVG: Yes (built-in) SVG content is supported by the native drawing stack. main@80baa3c7cb0f ยท reviewed 2026-11-09 SVG source | Yes (built-in) Framework image loading and decoding crate. main@2ca5f509e736 ยท reviewed 2026-11-10 Images sourceSVG: Yes (built-in) Framework SVG parsing and rendering, not a full browser SVG DOM. main@2ca5f509e736 ยท reviewed 2026-11-10 SVG source | Yes (built-in) The first-party image module supplies image elements and desktop or web Host implementations. main@536dd4949e69 ยท reviewed 2026-11-10 Images sourceSVG: Yes (built-in) The first-party SVG module supplies SVG construction and replay support. main@536dd4949e69 ยท reviewed 2026-11-10 SVG source |
| Clipping and transforms | Yes (built-in) Rectangles support overflow/clipping and visual transformation properties. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) Styles expose overflow and transformation controls for elements. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) Style modifiers include clipping, overflow and transforms. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Renderer interfaces expose layers/clipping and transformations. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Partially (partial) Painter supports clipping and shape transforms. Arbitrary transformed interactive subtrees are not implied by mesh transformation support. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) Core items include clipping and transform-related behavior. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) Renderer contracts include clipping and transforms. Renderer-specific limitations still apply. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) The DOM paint pipeline supports clipped and transformed drawing. CSS coverage remains a beta engine's subset. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) The drawing layer handles draw-list clipping and transformations. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) Styles expose overflow and transformation controls for elements. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Rounded clipping, offsets, scaling, rotation and layer compositing are documented APIs. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) CSS transforms and nested clipping regression coverage in the framework. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Div exposes overflow clipping, rotation, scale and translation. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) The desktop scene carries transforms and clipping through retained presentation and painting. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Fractional scaling | Yes (built-in) The Winit shell combines the floating-point display scale with a custom scale and updates layout when it changes. Not execution-validated across platforms. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) Layout explicitly handles fractional display scales such as 125% and 150%, converting between logical and device pixels. Not execution-validated across platforms. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) The window integration multiplies the floating-point system scale by an arbitrary user scale and updates the context. Not execution-validated across platforms. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) The Winit integration combines floating-point window and application scales and updates the viewport on scale changes. Not execution-validated across platforms. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) The official Winit integration stores the native display scale as floating-point pixels per point and updates it on scale changes. Not execution-validated across platforms. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) The Winit backend explicitly accounts for fractional display scales when converting requested logical window sizes to physical pixels. Not execution-validated across platforms. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) The window integration uses the floating-point OS scale to convert surface dimensions and initialize rendering. Not execution-validated across platforms. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) The Blitz shell passes floating-point Winit scale changes into the document viewport's HiDPI scale. Not execution-validated across platforms. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) The Wayland backend implements the fractional-scale protocol and handles the compositor's preferred scale. Not execution-validated across platforms. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) The Wayland backend implements preferred fractional-scale events, and layout handles non-integer device scales. Not execution-validated across platforms. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) The Winit web platform handles floating-point scale changes and resizes its rendering surface accordingly. Native-platform parity was not execution-validated. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Source regression tests cover surface coverage at 1.2x and 1.25x and pointer hit testing at fractional scales. These tests were source-reviewed, not run here. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) The desktop event loop carries the floating-point Winit display scale into layout and rendering. Not execution-validated across platforms. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) The desktop host passes the floating-point display scale and logical viewport dimensions to the style environment. Not execution-validated across platforms. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Pixel snapping | Yes (built-in) Layout snaps authored metrics and resolved box edges in device-pixel space before returning logical bounds. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Partially (partial) The layout cache rounds relative x/y positions, but preserves widths and heights. This is not a complete shared-edge snapping policy. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Quads expose a snap flag for pixel-grid alignment. Its default follows the crisp feature, so snapping is configurable rather than unconditional for every primitive. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) GuiRounding provides scale-aware rounding to physical pixel boundaries and pixel centers for scalar and geometry types. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Partially (partial) The FemtoVG renderer snaps text selection x coordinates and text y coordinates when the transform permits it. Framework-wide box-edge snapping across renderers was not established. master@b3be5c22781d ยท reviewed 2026-11-06 Source | No Taffy layout rounding is explicitly disabled. No replacement framework-wide physical-pixel snapping policy was established in the reviewed source. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) Blitz rounds resolved layout box edges before painting while preserving unrounded text origins for subpixel text placement. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Partially (partial) The Finish shader helpers include a function to snap an edge to whole device pixels. Automatic framework-wide layout snapping was not established. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) Layout snaps authored metrics and resolved box edges in device-pixel space before returning logical bounds. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Paint-time snapping aligns box edges, borders and clips to device pixels while keeping layout fractional. Moving or rotated content has explicit exceptions, and subtrees can opt out. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Layout, painting and hit testing share a device-pixel policy for edge rounding, covering bounds and nonzero stroke widths. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Partially (partial) Scroll offsets are rounded in device-pixel space. A framework-wide shared-edge snapping policy for all layout boxes was not established. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | No Layout disables Taffy rounding. No replacement framework-wide device-pixel snapping policy was established in the reviewed source. main@536dd4949e69 ยท reviewed 2026-11-10 Source | |
| Shaders | ||||||||||||||
| Custom shaders | Yes (built-in) ShaderFill accepts a compiled Skia RuntimeEffect and a provider for shader uniforms. Custom fills use SkSL RuntimeEffect, not arbitrary WGSL or GLSL pipelines. They are tied to the Skia rendering model. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Unknown Canvas exposes framework paint operations. An arbitrary user-defined GPU shader/pipeline API was not established, and internal backend shaders are not evidence of one. Internal WGPU shaders use WGSL while Apple paths use Metal. Internal shader files are not a portable public custom-shader API. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Partially (partial) Custom View drawing receives a Skia Canvas and can issue Skia paint operations. Using Skia shader effects is custom native drawing, not a portable shader widget API. Custom draw integration uses Skia APIs and their RuntimeEffect/SkSL model when needed. Internal gradients do not establish a WGSL shader-injection API. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Shader widget exposes a WGPU-backed custom rendering primitive/pipeline interface. Custom shader primitives use the WGPU renderer path. This is not portable shader execution on the TinySkia fallback. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) The repository demonstrates custom WGPU rendering via paint callbacks. The WGPU example uses WGSL. Glow/OpenGL callbacks require their own integration and shader setup. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Partially (partial) Custom WGPU rendering can supply a texture for display. This is renderer-specific interop, not a shader language embedded in every Slint item. The WGPU texture example uses WGSL. OpenGL rendering hooks and software rendering have different capabilities. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Unknown The renderer exposes painting operations, but an arbitrary application shader/pipeline hook was not verified. The example named webgpu is a browser counter, not evidence of custom shader injection. Drawing targets the selected renderer abstraction. Its concrete backend may use GPU shaders internally, but that does not provide a portable user shader language. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Partially (partial) The native example embeds a custom WGPU widget and shader-rendered content in the DOM. This is renderer-specific integration, not a portable CSS shader property. DOM painting targets AnyRender. Custom shader capabilities depend on a chosen concrete renderer and are not the same as browser WebGL support. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) The script/shader system compiles custom shader code for GPU rendering. Makepad uses its own shader/script representation with backend lowering. Applications cannot assume raw WGSL, GLSL and Metal source are interchangeable across targets. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Unknown Canvas exposes framework paint operations. An arbitrary user-defined GPU shader/pipeline API was not established, and internal backend shaders are not evidence of one. Internal WGPU shaders use WGSL while Apple paths use Metal. Internal shader files are not a portable public custom-shader API. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Compositor hooks expose WGPU frame rendering and effect slots. This is an explicit custom GPU rendering hook, not a WebGPU-named counter example. WGPU uses WGSL, while native Metal has separate precompiled shaders and feature constraints. Backend capabilities are not interchangeable. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Application shaders and embedded WGPU surfaces are exposed. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Flow shader language compiles custom effects to WGSL for the framework renderer. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Unknown Internal WGSL pipelines exist, but a public custom-shader API was not established in the inspected source. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Layout and widgets | ||||||||||||||
| Layout model | Torin (custom)Torin (custom) Torin supplies directional, sized and positioned layout. Do not equate this API with a complete browser CSS implementation. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Taffy (CSS)Taffy (CSS) Element styles provide flex/grid and sized/positioned layout through the framework layout engine. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Morphorm (custom)Morphorm (custom) Morphorm supplies flexible layout. This is not a promise of full browser CSS layout compatibility. main@9231260010d5 ยท reviewed 2026-11-06 Source | Custom (rows and columns)Custom (rows and columns) Layout nodes underpin rows, columns, containers and custom widgets. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Custom (immediate mode)Custom (immediate mode) Immediate-mode horizontal/vertical/wrapping layouts are built in. This is not a retained CSS layout tree. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Custom (declarative)Custom (declarative) The core implements layout algorithms for declarative layout items. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Taffy (CSS)Taffy (CSS) Taffy-backed flexbox and grid layout are explicitly documented. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Taffy (CSS)Taffy (CSS) Stylo resolves CSS, Taffy handles box layout and Parley handles inline text. Browser compatibility is not assumed for every CSS feature. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Custom (flow layout)Custom (flow layout) Views expose toolkit layout, sizing, flow and positioning behavior, rather than browser CSS layout. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Taffy (CSS)Taffy (CSS) Element styles provide flex/grid and sized/positioned layout through the framework layout engine. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Taffy (CSS)Taffy (CSS) Taffy-backed flex, grid and block layout capabilities with retained measurement caches. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Cephal (CSS)Cephal (CSS) Stylo CSS cascade with cephal block, flexbox and grid layout. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Taffy (CSS)Taffy (CSS) Declarative layout through Taffy with flexbox and sized/positioned elements. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Taffy (CSS)Taffy (CSS) The Rust runtime uses Taffy layout and structured CSS styling. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Virtualization | Yes (built-in) VirtualScrollView builds visible items from a logical item count and builder. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) uniform_list builds a visible range rather than constructing the entire logical list. A separate list implementation supports variable-sized entries. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) VirtualList constructs the required visible item range. main@9231260010d5 ยท reviewed 2026-11-06 Source | Partially (partial) Lazy widgets defer cached content construction. Lazy alone is not list viewport virtualization, and a complete built-in arbitrary-row virtual-list API was not verified. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) show_rows/show_viewport allow viewport-based list rendering. A plain show closure is not automatically virtualized. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) Model-backed repeaters implement viewport/list virtualization, not just a full list hidden by clipping. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) Virtual stacks and lists construct visible content from a larger logical sequence. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Unknown The native DOM engine is not itself a virtual-list component. A general built-in Dioxus Native viewport virtualizer was not verified. The benchmark's custom virtualizer is not toolkit evidence. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) PortalList provides visible-item list rendering rather than a widget for every logical row. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) uniform_list builds a visible range rather than constructing the entire logical list. A separate list implementation supports variable-sized entries. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) virtual_rows lazily builds a toolkit-managed mounted window. A key-set version avoids rescanning stable keys on later commits. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) zgui-ui exports VirtualList, VirtualWindow and Virtualize. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) VirtualList mounts a reactive window with spacers and measured variable-height rows. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) The dedicated List component virtualizes keyed items. ScrollView itself is non-virtualized. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Menus, tables and trees | Partially (partial) Menus and table components are included. A complete built-in tree-view family is not established by this module inventory. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Partially (partial) Platform menu abstractions and list primitives exist. Complete table/tree widgets are not implied by those low-level APIs. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) The view inventory includes menu, virtual table and virtual tree/table families. main@9231260010d5 ยท reviewed 2026-11-06 Source | Partially (partial) Menu overlays and table-related widgets exist. A complete built-in tree widget was not established. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Partially (partial) Menus and collapsing sections are built in, while tables are in official egui_extras. Rich trees can require custom composition or another crate. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Partially (partial) Native/styled menu support and table/list widgets exist. A complete tree-view widget family was not verified. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Partially (partial) Context/platform menus and list composition are provided. A complete built-in table/tree widget family was not established. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Partially (partial) Native HTML table layout and a Muda menu integration exist. A complete Rust table/tree widget library is not implied. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Partially (partial) The widget inventory includes menus and collections/tree-related components. Feature-rich table/tree parity across every widget family was not established. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Partially (partial) Platform menu abstractions and list primitives exist. Complete table/tree widgets are not implied by those low-level APIs. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Partially (partial) Popup and context-menu APIs are documented. This bundled claim does not establish a complete specialized table and tree widget suite. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Partially (partial) Menus and data tables are provided. A general tree widget was not established. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Partially (partial) Context/dropdown menus and table primitives are included. General tree-widget support was not established. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Unknown A dedicated cross-platform menu, table, or tree widget set was not established in this source review. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Text | ||||||||||||||
| Selection and editing | Yes (built-in) freya-edit provides cursor movement, selection and editable text state, also used by input and editor components. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Partially (partial) The input example implements selection, cursor movement and editing. Core paintable text alone is not a full editor widget. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) Textbox handles cursor movement, selection and edits. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) TextEditor supports editing actions and selection. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) TextEdit supports cursor state, selection and editable text. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) Text input includes selection, cursor movement and edit handling. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) The text editor view implements selection and editing through editor state. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) Native selection state is implemented, alongside form editing handlers. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) TextInput manages selection, cursor behavior and editing. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Partially (partial) The input example implements selection, cursor movement and editing. Core paintable text alone is not a full editor widget. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) TextEdit supports selection, clipboard editing, undo and redo. Selectable text also has documented APIs. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Framework text editing is implemented in zgui-edit. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Text input data provides cursor movement, selection, editing and undo/redo. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) The desktop Host routes text selection, editing commands and clipboard shortcuts to focused text controls. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| IME | Yes (built-in) Core IME state and positioning API is supplied. Platform behavior still depends on the selected shell. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Partially (partial) Input handlers expose marked text and replacement ranges for platform IME. Applications must implement the contract correctly. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) The Winit shell forwards enabled, preedit, commit and disabled IME events. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) The native shell enables input methods and manages preedit display/positioning, with enabled/preedit/commit/disabled events converted in the Winit integration. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) The integration/input API includes explicit IME events, consumed by text editing. Shell support remains relevant. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) The Winit backend handles input-method events and positioning for focused inputs. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) TextInput explicitly handles preedit, surrounding-text deletion and commit IME events. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) IME events are applied to focused text-input data and forwarded as DOM events. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) The platform layer has an explicit IME abstraction used by editable input. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Partially (partial) Input handlers expose marked text and replacement ranges for platform IME. Applications must implement the contract correctly. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Winit preedit and commit are routed to focused text fields or an app editor hook. Not tested with every platform input method. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Native platform integration documents IME support. Cross-platform behavior was not execution-tested. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Partially (partial) IME bindings and platform bridges exist. Cross-platform composition and candidate-window parity were not execution-validated. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) The desktop Host routes Winit IME commit and preedit events and updates the candidate cursor area. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| RTL and bidirectional text | No RTL and bidirectional text are not supported, per the maintainer's clarification. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Partially (partial) RTL wrapping is implemented and tested, but the line-layout source explicitly states that UAX #9 bidirectional support is incomplete. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Partially (partial) Paragraph direction and RTL textbox handling are implemented. The shared movement routine still assumes left-to-right order, so mixed-direction navigation is limited. main@9231260010d5 ยท reviewed 2026-11-06 Source | Partially (partial) The text renderer handles RTL runs and advanced text editing delegates motion to cosmic-text. Basic and advanced shaping paths differ, so this is not uniform bidi behavior across all text controls. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | No The text layout source explicitly says RTL/bidi support is still to be added. Font shaping does not provide bidirectional layout on its own. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Partially (partial) RTL text elision and bidi-aware selection are implemented, but the RTL regression fixture explicitly excludes the software embed-assets path because that path lays out text left to right. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Partially (partial) Text layout uses Parley, but TextInput left/right movement advances backward/forward through logical grapheme indices rather than visual bidi order. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Partially (partial) CSS direction and unicode-bidi are passed to the inline text layout builder. RTL text layout is implemented, but full mixed-direction editing was not established. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Partially (partial) The shaper resolves bidi runs, but TextInput left/right navigation uses previous/next logical grapheme boundaries rather than visual bidi movement. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Partially (partial) RTL wrapping is implemented and tested, but the line-layout source explicitly states that UAX #9 bidirectional support is incomplete. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Partially (partial) Caret affinity, hit testing and selection geometry explicitly handle RTL visual clusters. This is more than a Parley dependency, but complete mixed-direction editing was not established. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Mixed Arabic/Latin regression tests cover bidirectional shaping, hit testing, caret affinity at direction boundaries and split selection geometry. Not execution-validated here. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Unknown Rustybuzz shaping is present, but complete bidirectional layout, editing and navigation were not established. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) Paragraph shaping carries text direction into Parley and preserves bidirectional paragraph geometry. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Animation | ||||||||||||||
| Transitions | Yes (built-in) use_animation drives timed animated values and rerendering. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) AnimationExt applies timed interpolation/easing and requests animation frames. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) The toolkit has an animation system and property interpolation. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Animation provides time-based value interpolation and easing. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) AnimationManager interpolates widget state over time. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) Property animation is part of the runtime and declarative language. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) Interpolatable style properties can have timed transitions. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Partially (partial) The DOM tracks active CSS animations/transitions. Beta feature coverage and repaint behavior need per-property verification. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) Widget animator infrastructure drives animated state transitions. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) AnimationExt applies timed interpolation/easing and requests animation frames. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Presence transitions and animated layout/color tracks are documented. Benchmark dummy changes disable animation. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) CSS transitions and keyframe animations are included. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Keyframe animation, timelines and CSS motion support. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) Rust-owned animation supports CSS transitions and keyframes while scheduling frames only during active work. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Spring animation | Yes (built-in) Spring-like motion is available through Elastic and Bounce easing, with custom easing functions also supported. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) SpringConfig, SpringState and SpringAnimation provide an explicit physics-based spring API. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Partially (partial) Custom cubic-bezier easing can overshoot and settle. A reusable oscillating spring or elastic/bounce preset was not established. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Animation exposes elastic, bounce and custom easing through lilt, allowing spring-like motion without a dedicated physics solver. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Public back and bounce easing functions can animate spring-like motion through the animation APIs. Scroll overshoot also uses a critically damped spring. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) The declarative language test demonstrates easing: spring with bounce parameters and retargeting. This is evidence for the inspected source, not every older published version. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) Spring implements a physics-based easing API with tunable parameters. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Unknown CSS animation is present, but a reusable spring, elastic or bounce easing API was not established in the inspected native backend. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) The tween easing implementation includes spring-based motion. This is a development-commit feature, not a claim about every published release. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) SpringConfig, SpringState and SpringAnimation provide an explicit physics-based spring API. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Analytic springs are a core motion primitive. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Spring motion model supports retargeting and frame-by-frame integration. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) First-class spring physics with configurable damping and stiffness. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) Animation configuration includes a stateful spring integrator and spring constructors. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Accessibility | ||||||||||||||
| Semantic tree | Yes (built-in) Core accessibility tree tracks semantic nodes and updates. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) AccessKit semantic roles and stable global element IDs are documented. Custom elements must expose their own semantics. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) The accessibility system builds semantic AccessKit tree updates. main@9231260010d5 ยท reviewed 2026-11-06 Source | No Upstream Iced does not provide an OS accessibility semantic tree. AccessKit integration exists in the separate COSMIC fork. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) The core constructs AccessKit semantic nodes. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) Core accessibility representation is implemented. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Unknown Semantic tree was not established in the inspected core, widget and shell APIs. Keyboard handling or widget IDs are not evidence of an OS semantic accessibility bridge. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) DOM roles and HTML/ARIA attributes are translated into accessibility nodes. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) Widgets expose semantics backed by a shared accessibility tree. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) AccessKit semantic roles and stable global element IDs are documented. Custom elements must expose their own semantics. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Element roles, labels and state feed a semantic tree and platform accessibility adapters. This is not a screen-reader completeness certification. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Framework accessibility projection is implemented in zgui-a11y. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Partially (partial) Platform-neutral accessibility nodes and actions exist. README still lists screen-reader semantics as ongoing work. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) The retained desktop scene projects semantic nodes into AccessKit tree updates. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Keyboard navigation | Yes (built-in) Focus navigation is integrated with keyboard interaction. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) Action/key binding dispatch supports keyboard interaction. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) Keyboard events and focus navigation are handled by the event system. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Focus operations support keyboard traversal of focusable widgets. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) UI memory manages keyboard focus and widget interaction state. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) Window/input handling manages keyboard focus and dispatch. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) The event system dispatches keyboard interactions and focus navigation. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) Native keyboard events are translated into DOM/input behavior. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) Button behavior explicitly handles keyboard focus and keyboard activation. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) Action/key binding dispatch supports keyboard interaction. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Tab navigation, focus groups, activation and key routing are documented runtime APIs. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Components document keyboard controls, tab confinement and focus return. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Partially (partial) Keyboard focus routing exists. README identifies keyboard navigation in menus, overlays and OTP fields as ongoing work. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Partially (partial) Desktop keyboard handling covers text-editing commands. General Tab traversal across arbitrary controls was not established. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Focus handling | Yes (built-in) Accessibility focus handles and focus requests are provided. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) FocusHandle and window focus management are available. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) Event context exposes focus management for interactive views. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Focusable widget operations expose focused state and traversal. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Focus state, requests and traversal are part of UI memory. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) Focused item tracking and focus changes are part of the core runtime. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) Views can request and track keyboard focus through view IDs. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) The engine implements native focus changes and focused element tracking. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) Widgets can request, retain and respond to key focus. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) FocusHandle and window focus management are available. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Focusable elements, focus groups, modal trapping and focus restoration have public APIs. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Headless primitives provide focus, dismissal and roving selection. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Event router tracks focused nodes and keyboard-visible focus rings. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Partially (partial) Focus state and AccessKit focus actions are provided. General traversal policy was not established. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Assistive technology integration | Yes (built-in) The optional desktop accessibility integration uses AccessKit. This does not certify all widgets or every platform/backend. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Partially (partial) AccessKit integration is implemented. This does not establish equivalent support in every platform backend or application widget. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Partially (partial) AccessKit has tree/action handling, but AccessibilityDeactivated still reaches todo! in the inspected Winit source. Do not label the integration complete. main@9231260010d5 ยท reviewed 2026-11-06 Source | No Upstream Iced does not provide assistive technology integration. AccessKit integration exists in the separate COSMIC fork. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Partially (partial) AccessKit support and manual integration testing are documented. Support depends on the host integration and widget coverage, not merely enabling a label. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) The Winit backend bridges semantic state to AccessKit. Support depends on target, feature selection and widget semantics. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Unknown Assistive technology integration was not established in the inspected core, widget and shell APIs. Keyboard handling or widget IDs are not evidence of an OS semantic accessibility bridge. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Partially (partial) The shell bridges DOM semantics to AccessKit. Beta status and per-control/platform gaps prevent a blanket completeness claim. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Partially (partial) The HAL maintains semantic trees for native adapters, announcements and OS self-checks. Equivalent support across all mobile/web backends is not established. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Partially (partial) AccessKit integration is implemented. This does not establish equivalent support in every platform backend or application widget. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Default accessibility feature includes AccessKit platform adapters for Windows, macOS and Linux. Not end-to-end screen-reader tested here. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) AccessKit Winit integration is included. Screen reader behavior was not execution-tested here. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Partially (partial) An iOS semantic snapshot bridge exists. Equivalent desktop screen-reader integration was not established and accessibility remains roadmap work. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) AccessKit adapters are selected for desktop platforms, including Unix accessibility support on Linux. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Integration | ||||||||||||||
| Clipboard | Yes (built-in) Clipboard abstraction has platform implementations, separate from ordinary text state. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) Platform clipboard contracts support reading and writing clipboard content. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) Clipboard support is a default feature, with a platform clipboard dependency. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Runtime clipboard tasks read/write supported clipboard content through the shell. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) The official Winit integration implements platform clipboard operations. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) The native backend provides clipboard integration, with a separate iOS implementation. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) Clipboard operations are part of platform integration. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) Clipboard behavior is covered by native DOM regression tests. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) The HAL provides clipboard integration with platform implementations. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) Platform clipboard contracts support reading and writing clipboard content. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Native clipboard copy and paste include rich text and image hooks with platform-specific behavior. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Native clipboard integration is documented. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Desktop text clipboard integration uses arboard, with native mobile bridge paths. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) The desktop Host uses arboard for text copy, cut and paste shortcuts. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Drag and drop | Partially (partial) In-application drag/drop components are implemented. Full OS cross-application data-transfer parity was not established. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) An in-repository drag/drop example exercises the core API. Platform data formats remain backend-dependent. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Partially (partial) In-app drag/drop is demonstrated. This does not establish arbitrary native cross-app data transfer. main@9231260010d5 ยท reviewed 2026-11-06 Source | Partially (partial) The shell handles native file drop events. This is not proof of a complete reusable cross-widget and cross-application drag/drop framework. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Core drag/drop state supports in-app transfers. Native file drops are integration dependent. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Partially (partial) DragArea and DropArea provide in-window data transfer. Native drag-and-drop to other applications is implemented on the Qt backend, not established uniformly across backends. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) The event system tracks in-app drag state. This is not a promise of OS cross-application data-format parity. main@1351ffb162fa ยท reviewed 2026-11-06 Source | No The native shell explicitly ignores WindowEvent::DragDropped, so native file drops are not delivered to the DOM. Pointer-based interactions do not provide OS drag-and-drop integration. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) The event layer includes explicit drag/drop data/events. Data formats and platform integration remain target-dependent. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) An in-repository drag/drop example exercises the core API. Platform data formats remain backend-dependent. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Native drag-out and file-drop APIs are documented, with platform-specific behavior. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Native drag and drop integration is documented. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Partially (partial) Native file-drop callback is provided. Arbitrary cross-application drag-source/data-format support was not established. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Unknown A public cross-platform drag-and-drop API was not established in the inspected desktop event routing. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Dialogs | Partially (ecosystem) The shell depends on rfd for native dialogs. This does not imply a cross-backend Freya dialog widget API. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) Platform prompt and path-selection interfaces are provided, with OS-specific implementations. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Partially (ecosystem) The example integrates an external file-dialog crate rather than establishing a universal Vizia-native file picker. main@9231260010d5 ยท reviewed 2026-11-06 Source | Partially (ecosystem) The official editor example uses rfd::AsyncFileDialog for native file selection. This is an external dialog integration, not an Iced-native file-picker widget. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Partially (ecosystem) Native file pickers use an external crate such as rfd, rather than core egui itself. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Partially (partial) The language includes a Dialog abstraction. Native OS file pickers are a separate integration and are not implied by this widget. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Partially (ecosystem) Native file dialog integration depends on rfd, not a renderer-native file-picker widget. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) The native shell implements single/multiple native file selection through rfd on desktop, behind the default-enabled file-dialog feature. File-input click handling calls this shell API. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) Platform file dialog interfaces are present, with native backend implementations. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) Platform prompt and path-selection interfaces are provided, with OS-specific implementations. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Opt-in native-file-dialog feature uses rfd or Linux portals. It is not enabled by this benchmark. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Partially (partial) In-window Dialog and AlertDialog components. Native OS file dialogs were not established. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Feature-gated native file dialogs through rfd and in-window component dialogs. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Unknown A built-in cross-platform dialog API was not established in the inspected public application API. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Multiple windows | Yes (built-in) Platform manages multiple windows by ID and provides per-window handles. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) App opens and manages multiple native windows. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) The Winit host tracks and dispatches events for multiple windows. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Daemon applications can manage multiple windows rather than only a single application window. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Viewport APIs support additional native windows through a supporting integration, not just painted in-app windows. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) Multiple component windows are supported through the runtime and backend. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) Window configuration and creation support multiple windows. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) The shell application manages multiple views/windows. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) Window widgets and platform infrastructure support multiple native windows. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) App opens and manages multiple native windows. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) App windows, retained hidden windows and overlays have explicit lifecycle APIs. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Native multi-window application support is documented. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Desktop context opens additional native windows and exposes per-window actions. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Unknown The standalone desktop application configuration owns one window. A public multi-window API was not established. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Embedding | Yes (built-in) Supported through Freya's core crates with a custom host shell. The host handles rendering, event delivery and lifecycle instead of using the Winit launcher. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Partially (partial) Platform interfaces expose native-window integration hooks. Embedding capabilities vary by backend and are not a generic cross-platform compositor contract. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) The Baseview backend provides host-window/audio-plugin integration. main@9231260010d5 ยท reviewed 2026-11-06 Source | Partially (partial) The renderer-agnostic runtime is reusable in existing systems. Native host embedding still needs a suitable integration. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) The core is designed to be embedded anywhere that supplies input and renders textured triangles. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) The Platform/WindowAdapter abstraction supports custom platform integration, including embedded systems. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Partially (partial) Rendering is abstracted into reusable renderer interfaces. Turnkey arbitrary host-window embedding was not verified. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Partially (partial) The example embeds custom WGPU content inside Blitz/Dioxus Native. It does not by itself prove that the entire DOM UI can be dropped into any foreign native window host. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Partially (partial) The HAL separates host/platform services and rendering. This does not certify arbitrary foreign-toolkit embedding on every target. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) Opt-in native composition is documented for macOS AppKit views, Windows WebView2 composition, Wayland subsurfaces and X11 child windows. The overlay strategy differs by platform. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Partially (partial) LayerHost embeds a Rune runtime and Metal renderer into an existing CAMetalLayer owned by UIKit, SwiftUI or AppKit. This is Apple-specific hosting, not a cross-platform arbitrary-window embedding API. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Unknown Embedding WGPU surfaces inside zgui is documented, but embedding zgui in a host application was not established. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Partially (partial) RenderTree and text measurement are exported for custom hosts. A drop-in cross-platform native-window embedding contract was not established. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Partially (partial) Platform module definitions can supply native desktop elements and raster content. Embedding the entire Host into an existing application was not established. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Tooling | ||||||||||||||
| Inspector | Yes (built-in) Feature-gated developer tools inspect the component tree. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) The inspector supports element selection, picking and registered inspector states. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Partially (partial) Environment events enable a layout-debug overlay highlighting views that underwent layout. This is a diagnostic overlay, not a full interactive property inspector. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) The in-repository devtools/debugging subsystem provides UI diagnostics. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) The official inspection feature integrates the in-repository inspection tooling. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) Live preview includes item/property inspection. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) An in-repository element inspector is included. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) The devtools feature implements Chrome DevTools Protocol integration, document inspection and element picking. This is native DOM tooling, not an embedded WebView inspector. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) Studio and UI automation/inspection tools are explicitly part of the development environment. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) The inspector supports element selection, picking and registered inspector states. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Element-tree inspection and playground tooling are documented. These are separate from OS accessibility validation. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Window inspector exposes document, styles, layout and frame statistics. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Partially (partial) Standalone debugger inspects recorded UI sessions. README still lists live visual inspection as future tooling work. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Unknown Hot reload is documented, but an interactive UI or layout inspector was not established. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Hot reload | Partially (partial) The hotreload feature integrates Subsecond and dx. Patches reset hook state and cancel tasks, and structural Rust changes require a restart. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Partially (partial) A hot-reload integration exists. Availability is feature/toolchain dependent, not unconditional live replacement of arbitrary Rust changes. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Partially (partial) Stylesheets support hot reloading. This does not imply hot replacement of arbitrary Rust application logic. main@9231260010d5 ยท reviewed 2026-11-06 Source | Partially (partial) The hot feature enables explicitly very experimental hot reloading. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Unknown Live mutable UI state and immediate-mode redraw are not source hot reload. A general official source-reload contract was not verified. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) The viewer supports auto reload and the language server provides live preview. This covers Slint UI source, not arbitrary Rust hot patching. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Unknown Hot reload was not established as a supplied toolkit facility in the inspected source. Internal unit tests, redraws and ordinary rebuilds do not imply a public interactive test harness or live source reload. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) The hot-reload feature connects Dioxus RSX hot reload in debug builds. Arbitrary Rust structural changes still require rebuilding/restarting. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) The live-editable UI scripting/design language supports iteration without full application rebuilds. Arbitrary Rust code changes are a different concern. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Partially (partial) A hot-reload integration exists. Availability is feature/toolchain dependent, not unconditional live replacement of arbitrary Rust changes. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Partially (partial) Opt-in hot feature uses subsecond and Dioxus development tooling. Platform, edit-compatibility and restart restrictions are documented. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Unknown Live code or stylesheet reloading was not established by this review. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Partially (partial) Opt-in debug hot-reload runtime integrates Subsecond and dx, with source/file watching. Not arbitrary structural live replacement. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) The development runtime hot-patches edited components while preserving unrelated component state. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| UI testing | Yes (built-in) TestingRunner offers component/input assertions and optional rendered snapshots without a native window. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Yes (built-in) TestAppContext supports UI state and simulated platform/input operations. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Partially (partial) Repository tests cover core internals. A general public end-user GUI interaction/snapshot harness was not verified. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) The repository includes a tester interface for widget interactions and assertions. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Official egui_kittest supports input-driven UI testing, accessibility queries and snapshots. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) A dedicated testing backend and public testing facilities support simulated UI interaction and assertions. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) The repository includes a dedicated UI testing crate, with interaction/layout/animation tests. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) The repository contains a DOM/layout/painting test harness and dedicated regression suites. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) The repository exposes UI find/act/type/wait, semantic snapshots/diffs and OS checks for automation. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) TestAppContext supports UI state and simulated platform/input operations. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Deterministic headless runtime input and rendering support UI tests. These benchmarks instead use real native windows. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Framework provides a view testkit and headless probes. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Framework test-suite crate supplies UI regression tooling. API existence does not establish coverage of every platform. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Partially (partial) Host-conformance fixtures cover layout, painting and interaction contracts. A general headless user-application UI runner was not established. main@536dd4949e69 ยท reviewed 2026-11-10 Source |
| Documentation and examples | Yes (built-in) Repository documentation and runnable examples are available. Their existence does not imply complete documentation for every API. main@11cd62a248bf ยท reviewed 2026-11-06 Source | Partially (partial) Repository documentation and runnable examples exist, but guides are limited and learning often requires reading Zed source code. main@9a8ab54db4f9 ยท reviewed 2026-11-06 Source | Yes (built-in) Repository documentation and runnable examples are available. Their existence does not imply complete documentation for every API. main@9231260010d5 ยท reviewed 2026-11-06 Source | Yes (built-in) API documentation and runnable examples are available, but the book is sparse and guided documentation is incomplete. master@8ff48c42b0d5 ยท reviewed 2026-11-06 Source | Yes (built-in) Repository documentation and runnable examples are available. Their existence does not imply complete documentation for every API. main@91b5712dd617 ยท reviewed 2026-11-06 Source | Yes (built-in) Repository documentation and runnable examples are available. Their existence does not imply complete documentation for every API. master@b3be5c22781d ยท reviewed 2026-11-06 Source | Yes (built-in) Repository documentation and runnable examples are available. Their existence does not imply complete documentation for every API. main@1351ffb162fa ยท reviewed 2026-11-06 Source | Yes (built-in) Repository documentation and runnable examples are available. Their existence does not imply complete documentation for every API. main@5be96ed0e621 ยท reviewed 2026-11-06 Source | Yes (built-in) Repository documentation and runnable examples are available. Their existence does not imply complete documentation for every API. main@506ec05105b9 ยท reviewed 2026-11-06 Source | Yes (built-in) GPUI architecture/setup documentation and runnable examples live in the repository. main@4a4a89af7c7f ยท reviewed 2026-11-06 Source | Yes (built-in) Repository includes API explanations and runnable native and web examples. Source presence is not a guarantee that every example works on every target. dev@a9da7e3ebf5a ยท reviewed 2026-11-07 Source | Yes (built-in) Documentation website, getting-started guide and runnable Rust examples. main@80baa3c7cb0f ยท reviewed 2026-11-09 Source | Yes (built-in) Documentation book, API reference and desktop/WebGPU examples are provided. main@2ca5f509e736 ยท reviewed 2026-11-10 Source | Yes (built-in) Public documentation, framework guides and example applications are provided. main@536dd4949e69 ยท reviewed 2026-11-10 Source |