Qualify read-only owned-dialog observations for native Save/reopen checks

Open
#375 5 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@DeandreT is already working on this.

Since Oct 11, 2026.

Assessment

This issue has not been assessed yet.

Description

The native Save/reopen qualification currently captures the isolated desktop but lacks a complete read-only observation of the exact owned dialog. Live window ownership, message, button, focus and capture associations remain unqualified.

Scope:

  • Add a separate read-only observation adapter for one owned window on the alternate test display.
  • Join the window identifier to current process identity, display server, transient parent, geometry and a complete window-specific image.
  • Retain independently verified message/button/default-focus observations and the original raw records.
  • Refuse unsupported, missing, stale or mismatched observations; preserve existing controller/helper bytes.
  • Add independently defined acceptance and refusal controls before any live qualification.

Depends on #291's isolated native workflow. Input delivery, dialog acknowledgement, native mapping changes and production GUI behavior are outside this issue.

Acceptance:

  • Raw observations identify one exact owned window and remain bound to its complete capture.
  • Missing native semantics or ownership evidence produces an explicit refusal.
  • Positive and negative observation controls retain complete records.
  • Read-only observation children close without desktop input.

Qualification remains synthetic, with independent review of complete decoder inputs/results and owned-process closure. Live window semantics, native ownership, image association and Save/reopen remain unqualified.

Dominant language
Rust
Stars
1
Forks
0
Avg merge
2h 50m
Merged PRs (30d)
571

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DeandreT/ferrule

All issues in DeandreT/ferrule

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.