Builds one flat AccessKit tree (iris_core::ui::access::AccessTree) from
iris's own widget tree: a synthetic Role::Window root with every named
widget as a direct child, names from the existing `.label()`, roles from
a new Widget::access_role() (default Unknown, TextEdit overrides to
TextInput/MultilineTextInput), bounds from UiRenderState::window_region
so a moved subtree reports where it actually is. Modular the way input's
sense registry is: Widgets gained one HashSet<WidgetId> ("named"),
populated only by .label()/set_label and drained by free_next (the
existing removal path), and AccessTree walks only that set -- a widget
nobody named costs it nothing. Updates only when the named set's name,
role or bounds actually changed, with a rebuild counter mirroring
take_counters (confirmed 1/0/1 across first-draw/unchanged/moved in
access_tests.rs).
Pushed through accesskit_winit on the desktop (DefaultApp::new now
creates the window hidden, builds the adapter, then shows it, per that
constructor's requirement) and accesskit_android on Android
(IrisViewPeer now implements AccessibilityNodeProvider). Both action
handlers are inert on purpose: AGENTS.md's tap-by-name is a real touch
at the node's bounds, not an AccessKit action request, so the ordinary
pointer path already answers it once bounds are right. E1's
detach-abort mitigation is carried into android/access.rs's
raise_if_enabled, which gates every QueuedEvents::raise on
AccessibilityManager.isEnabled().
tabs-ui's five switch buttons now carry .label()s matching their
on-screen text, giving both the desktop run and the emulator step real
names to find.
Verified on host: cargo fmt/build/clippy/test all clean (28 tests, 3
new), cargo ndk build+clippy clean for iris and iris-android-app,
run-headless.sh tabs --shot byte-identical to I2's prior screenshot
(27266 bytes). Not run: the emulator step (ui-trace tap-by-name against
iris-android-app), held by another session this pass -- exact commands
recorded in RUST.md's I4 box.
Co-Authored-By: Claude Sonnet <noreply@anthropic.com>
9.3 KiB
iris: notable public API changes
For Iris to read on her own time. Each entry is a change to iris's public surface that a widget author or app author would notice: a trait method added, removed or re-shaped; a type that callers construct differently; a capability that moved. Small and trivial changes do not go here.
An entry gives the date, what changed, why, and a short before/after where it helps judge the change without the session that made it. Newest first.
2026-09-05: accessibility names via AccessKit (RUST.md's I4)
.label() (already in trait_fns.rs, previously unused anywhere in-tree)
is now load-bearing: it's the one thing that puts a widget in the AccessKit
tree iris_core::ui::access::AccessTree builds and both backends push
out. A widget author who wants a control to be findable by name (and
tappable by name, through ui-trace/a real screen reader) calls .label()
on it; nothing else is required, and a widget nobody labels is invisible
to this system at zero cost, not just zero UI.
let button = rect(Color::LIME)
.on(CursorSense::click(), move |_, rsc| { ... })
.label("Add task"); // now findable by uiautomator/AccessKit as "Add task"
Two new things a widget author might touch directly:
Widget::access_role(&self) -> accesskit::Role, defaultUnknown. Override it if your widget has a real platform equivalent —TextEditnow returnsTextInput/MultilineTextInputbyEditMode. Only consulted for a widget that also has a.label(); an unlabelled widget'saccess_roleis never called.Widgets::named() -> impl Iterator<Item = WidgetId>— every widget with an explicit label, for anything else that wants to walk the same setAccessTreedoes.
Nothing about Painter, draw, or the layout/move machinery changed —
this sits entirely beside them, reading resolved_region's output rather
than participating in producing it.
2026-09-05: List, a virtualised bottom-anchored list (RUST.md's I3)
A new widget, iris::widget::List (iris/src/widget/list.rs -- read its
module doc first), for the transcript's kind of screen: variable-height
rows, keyed by a u64, composed only while visible, moved rather than
re-laid-out on scroll, a scroll anchor that survives a row inserted above
it, "more" sentinels at each end, and "hold the edge nearest the tap" when
a row's height changes (note_tap, resolved in the layout pass).
let mut list = List::new(Axis::Y);
list.push_back(ListRow::new(key, row_widget)); // O(1)
list.push_front(ListRow::new(older_key, row)); // O(1), anchor unaffected
list.set_more_before(Some(spinner_widget)); // sentinel, drawn at the edge
list.note_tap(viewport_y); // before mutating a row's height
let (top, bottom) = list.extent(key).unwrap(); // last frame's on-screen box, if visible
Built entirely out of existing primitives (Painter::widget/widget_within/
reposition/draw_twice, and draw_inner's own old-children diffing) --
no new mechanism was added to the render core for it. One correctness
lesson worth reading even for other widgets: a row that fills whatever
region it is offered (Rect, is_size_independent) cannot be measured at
a throwaway oversized region and then merely repositioned into place --
reposition only ever writes an offset, never a size, so the oversized
primitive stays oversized. List fixes this by caching each row's real
height once measured and placing an already-known row directly at its
exact box; see list.rs's place for the full reasoning and
a_fill_shaped_background_is_not_left_oversized for the regression test.
2026-09-05: a second backend (android-view), and what moved to make room for it
RUST.md's I2. Three changes a widget or app author would notice, all in
service of the same thing: default (winit) and the new android
(android-view) backends sharing what does not depend on windowing.
Selector/Selectable's bound changed fromRsc::State: HasDefaultUiStatetoRsc::State: FocusHost(new trait,attr.rs).HasDefaultUiStatestill exists and still works —default/attr.rsnow implementsFocusHostfor anything that has it — so a winit app's existing code is unaffected. An Android app implementsFocusHostviaHasAndroidUiStateinstead. Affects only an app that referencedHasDefaultUiStatedirectly at aSelectable/Selectorcall site rather than through.attr::<Selectable>(()), which nothing in-tree does.Tasks::inittakesArc<dyn RequestRedraw>instead ofArc<winit::window::Window>.RequestRedraw(task.rs) is one method,fn request_redraw(&self);winit::window::Windowimplements it (default/render.rs), soTasks::init(window)at a call site is unchanged by inference. Only matters if something constructed aTasksdirectly rather than throughDefaultRsc/AndroidRsc.TextEdit::apply_event/TextInputResultare#[cfg(not(target_os = "android"))]— they take awinit::event::KeyEvent, which does not exist on Android;android/input.rsdrives the same primitives (backspace/delete/motion/insert, all still unconditional) fromndk::event::Keycodedirectly instead. New unconditional getters on the way:TextEdit::text()/selection_range()/caret(), andTextEditCtx::delete_byte_range/set_cursor_byte— the primitivesandroid/ime.rs'sInputConnectionbridge needed and that were not previously exposed publicly.
2026-09-04: Widget::draw reports the size it used; desired_width/desired_height are gone
A widget used to implement three methods (draw, desired_width,
desired_height); it now implements one, fn draw(&mut self, painter: &mut Painter) -> Size, which draws into painter.region() and returns how much
of it was used. Why: the two extra methods routinely re-simulated what
draw was about to do anyway (Span::desired_ortho copied its own draw
loop to get cross-axis sizing right) — one visit per widget per frame
instead of up to three. A container that needs a child's size before
placing it (alignment, centering) draws the child once at a provisional
region, reads the returned Size, and calls the new Painter::reposition
to move it into its final spot — an O(1) offset write, not a second draw. A
widget whose drawn output never depends on the size it's given (a
fixed-size Rect, a decoded Image) overrides the new fn is_size_independent(&self) -> bool { false } to true, which skips
redrawing it when only its offered region changes shape.
// before
fn draw(&mut self, painter: &mut Painter) { /* ... */ }
fn desired_width(&mut self, ctx: &mut SizeCtx) -> Len { /* ... */ }
fn desired_height(&mut self, ctx: &mut SizeCtx) -> Len { /* ... */ }
// after
fn draw(&mut self, painter: &mut Painter) -> Size { /* ... */ }
SizeCtx and Cache are gone with it — see LAYOUT.md for the full
design, the move-offset mechanism this shipped alongside, and the file
list.
2026-09-04: texture pipeline rebuilt off the binding array
Textures/TextureHandle, GlyphPrimitive, and UiRenderNode::new all
changed shape. Why: the old pipeline bound every texture ever drawn in one
binding_array<texture_2d<f32>> and asked every device, unconditionally,
for VK_EXT_descriptor_indexing — a real share of Android GPUs lack it,
and it failed outright on the Android emulator's software Vulkan. See
TEXTURES.md's "Recommended shape" and "Implemented, 2026-09-04".
UiRenderNode::newdrops itslimits: UiLimitsparameter, andUiLimitsis gone. Before:UiRenderNode::new(&device, &queue, &config, UiLimits::default()). After:UiRenderNode::new(&device, &queue, &config). Nothing replaces it — there are no more binding-array limits to size.src/default/render.rs's device request asks for no features and no binding-array limits. Before:required_features: Features::TEXTURE_BINDING_ARRAY | Features::PARTIALLY_BOUND_BINDING_ARRAY | Features::SAMPLED_TEXTURE_AND_STORAGE_BUFFER_ARRAY_NON_UNIFORM_INDEXINGplus twomax_binding_array_*limits. After:Features::empty()(theDeviceDescriptordefault) and onlymax_buffer_sizeset, which was never about the binding array.TextureHandlehas noprimitive()method any more; a caller outsideirisshouldn't have been calling it (it fed the old renderer's internals), but if something did: useimage_index()for a standalone image's bind-group index. There is no equivalent for a page — a page has no bind group of its own now, see below.GlyphPrimitivehas no public constructor from a struct literal. Before:GlyphPrimitive { uv_min, uv_max, view_idx, sampler_idx, color, flags }. After:GlyphPrimitive::new(uv_min, uv_max, layer, color, flags)— onelayer(the shared atlas array's layer) instead of aview_idx/sampler_idxpair, since a page is now a layer of one array texture rather than its own bound texture.- A widget author drawing images is unaffected:
Painter::texture/texture_at/texture_withinandTextures::addkeep their signatures. What changed underneath is that each standalone image now gets its ownwgpu::BindGroupand draw call instead of a slot in the shared array — invisible from the widget API, visible only inUiRenderNode's internals and iniris's device requirements.