Skip to content

core: a write whose read-back was unavailable renders as "did not take" #522

Description

@xxx

Read from the code

crates/glass-core/src/error.rs (the AxValueNotApplied Display, ~:170-177): with observed: None the message opens "set_value on element #N did not take" and goes on to explain a value it never read. All three desktop readers can produce that case — a widget exposing a writable interface but no readable one (on Linux, EditableText without Text, now that set_value confirms by read-back in #517).

AxWriteUnconfirmed plus read_back_failed (crates/glass-core/src/set_value.rs) exist for exactly this situation, and docs/reference/tools.md tells the agent not to retry on it — the opposite of what the not-applied text invites.

Status

Theoretical. No widget with a writable-but-unreadable interface has been read on any platform; the shape was noticed while reviewing the Linux read-back. What would confirm it: a control that publishes EditableText (or Value's setter) without the matching getter, and the resulting message.

Fix direction

Return AxWriteUnconfirmed from every reader when the read-back is unavailable (as opposed to disagreeing), so the agent-facing text and the retry guidance match the case.

Metadata

Metadata

Assignees

No one assigned

    Labels

    theoreticalA bug theorized as possible by reading the code, but never reported or seen in actual use.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions