Manual test on Windows: with Lotus minimised to the tray, click a matrix: link (and a chat.lotusguild.org permalink in the browser) → the window must reveal and land on the room/message, both when a second instance is spawned (single-instance forward) and when the running instance receives the deep link directly. Record results here; file a bug if either path only focuses.
Manual test on Windows: with Lotus minimised to the tray, click a `matrix:` link (and a chat.lotusguild.org permalink in the browser) → the window must reveal **and** land on the room/message, both when a second instance is spawned (single-instance forward) and when the running instance receives the deep link directly. Record results here; file a bug if either path only focuses.
jared
added this to the Desktop 2026-Q4 milestone 2026-09-17 16:52:00 -04:00
Automated in the Windows smoke test (PR #43, run 2812). A matrix: link opened through Windows while the window is hidden to the tray, and again while minimised, goes protocol handler → second cinny.exe → single-instance. It reaches the page (lotus-deeplink) and un-minimises the window. Both pass.
Not checked automatically: whether the window becomes visible. The windows runner has no interactive desktop (even a direct show() stays hidden there). Keeping this open for that half; it checks itself once the runner runs in a desktop session, or on a quick manual try.
**Automated in the Windows smoke test** (PR #43, run 2812). A `matrix:` link opened through Windows while the window is hidden to the tray, and again while minimised, goes protocol handler → second `cinny.exe` → single-instance. It **reaches the page** (`lotus-deeplink`) and **un-minimises** the window. Both pass.
Not checked automatically: whether the window becomes **visible**. The `windows` runner has no interactive desktop (even a direct `show()` stays hidden there). Keeping this open for that half; it checks itself once the runner runs in a desktop session, or on a quick manual try.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Manual test on Windows: with Lotus minimised to the tray, click a
matrix:link (and a chat.lotusguild.org permalink in the browser) → the window must reveal and land on the room/message, both when a second instance is spawned (single-instance forward) and when the running instance receives the deep link directly. Record results here; file a bug if either path only focuses.Automated in the Windows smoke test (PR #43, run 2812). A
matrix:link opened through Windows while the window is hidden to the tray, and again while minimised, goes protocol handler → secondcinny.exe→ single-instance. It reaches the page (lotus-deeplink) and un-minimises the window. Both pass.Not checked automatically: whether the window becomes visible. The
windowsrunner has no interactive desktop (even a directshow()stays hidden there). Keeping this open for that half; it checks itself once the runner runs in a desktop session, or on a quick manual try.