Fission 0.6.2: accessibility, text input, and editor-grade focus

Fission 0.6.2 improves the parts of the framework that make an app usable day to day: accessibility, text input, input-method editor (IME) behaviour, editor…
2026-07-03
By Fission Team
Releases
Fission 0.6.2 improves the parts of the framework that make an app usable day to day: accessibility, text input, input-method editor (IME) behaviour, editor focus, and documentation authoring.
It also includes widget-state, layout, native overlay, and documentation-site fixes from the 0.6.2 cycle. These changes are now in published crates, so apps do not need to stay pinned to unreleased Git branches to use them.

Native accessibility bridge

The winit shell now publishes Fission semantics through the native accessibility path.
Screen readers, accessibility inspectors, remote-control tools, and native text tools need to understand the widget tree. Fission already had a semantics model; 0.6.2 connects it to the shell. Controls can now expose roles, labels, values, checked state, editable text, selection offsets, and supported actions through the host accessibility layer.
The bridge can report and update text values and selections. Platform tools can also inspect and operate buttons, checkboxes, radio buttons, sliders, and switches.
Bridge integration is not proof that every screen-reader path is complete on every target. For current Android TalkBack, Web canvas, and other limitations, use the accessibility matrix and test the actual controls with the target's assistive technology.

Text input and IME composition

Text input now keeps IME composition separate from committed text instead of flattening every incoming event into one value.
0.6.2 separates:
•
preedit updates;
•
preedit cursor movement;
•
cancellation;
•
committed text.
That distinction matters for CJK input, accented characters, emoji, autocorrect, and external keyboards that send composed text differently from ordinary key presses. Fission exposes preedit and selection ranges through semantics, renders preedit text distinctly, and keeps the IME cursor rectangle in sync after focus changes, edits, scrolling, and custom-editor events.
The cursor rectangle is how candidate windows and mobile keyboards know where the active edit point is.

Remote keyboard and custom winit packages

The release depends on the published Fission winit fork packages:
•
fission-winit 0.30.13-fission.1
•
fission-accesskit-winit 0.33.1-fission.1
The winit fork fixes a macOS text-input bug seen through Chrome Remote Desktop from Android. When the remote Android keyboard sent composed text in an event with a Space hardware key code, typed characters could arrive as spaces.
Fission now uses the text supplied by the platform instead of inferring it from a misleading hardware key. Publishing the forked package means apps can get the fix from crates.io while the upstream issue is handled separately.

Editor-grade focus policy

Rich editors often have toolbars, ribbons, sidebars, and palettes around the active text surface. A click on one of those controls should run its command without automatically moving focus away from the editor.
FocusPolicy::PreserveCurrentOnPointer handles that case. A ribbon button receives the pointer press and dispatches its command while the editor keeps focus. Editing commands, IME sessions, selections, and the caret stay with the editor; toolbar code does not have to restore focus after every click.
This is useful in word processors, code editors, and document tools where surrounding controls act on the editor.

Text selection fixes

The text-input path also fixes how selections are drawn and presented.
Single-character and partial selections now stay within the selected range instead of appearing to cover a whole line. Fission no longer shows drag handles as complete touch-selection controls when it cannot yet support the full drag interaction reliably.
That is deliberate. A native-looking handle that only partly works is worse than waiting until the interaction is ready.

Static-site tabs and framework learning docs

The documentation site now accepts Tabs and TabItem blocks in MDX. The Static site renderer emits static markup, and site JavaScript adds tab switching when the page loads in a browser.
This makes paired examples possible, including the new "Fission for React developers" guide. It builds a todo app in stages and places React and Fission side by side, so you can compare state, reducers, local widget state, theme-token styling, effects, routing, and tests without jumping between pages.
fission init now adds Fission app guidance at the repository root. It writes AGENTS.md, or AGENTS.fission.md if an agent file is already there. The generated file covers widget structure, state, routing, design systems, i18n, and validation.

Editor dogfooding and tests

The editor example now has a broader LiveTest for text input. It drives the editor through the work of writing a todo app: typing, correcting mistakes, undoing and redoing, selecting, copying and pasting text, using shortcuts, opening files from the tree, finding and replacing text, and saving.
This is broader than a unit test because it exercises the shell, runtime, text controller, semantics bridge, and custom editor together.

Other fixes included

0.6.2 also includes the recent layout and widget-state hardening work:
•
controlled widget interaction coverage for buttons, toggles, sliders, and text-adjacent controls;
•
layout panic fixes found during widget-state review;
•
rich text font fallback preservation;
•
native video and web overlay fallback paths for unsupported targets;
•
AppKit IME configuration guards for panic-prone platform calls.
These are not headline API features. They remove failures that app authors would otherwise encounter when building cross-target interfaces.

Migration notes

Apps on 0.6.1 can update the Rust dependency:
fission = { version = "0.6.2", default-features = false, features = ["desktop"] }
If your app has a ribbon, toolbar, or command surface around a text editor, use FocusPolicy::PreserveCurrentOnPointer on buttons that should act on the editor without taking focus.
If you use a generated Fission app, keep its AGENTS.md guidance under source control so future changes follow the same structure.

Verification

Before publishing, release preparation checks formatting and the workspace, then runs focused text-input, widget-state interaction, winit shell, editor LiveTest, and documentation-site tests.