From 560e542c5395f403909ecdf15f51b8a122fb5f29 Mon Sep 17 00:00:00 2001 From: LGUG2Z Date: Fri, 6 Nov 2026 13:56:27 -0800 Subject: [PATCH] docs(e2e): stacks and fullscreen are how macOS works, not defects of the daemon The reasons of the two marks said the daemon fails to put a stack's windows away and has no fullscreen detection. Both are how macOS is meant to work here: a stack is the focused window raised over the others, and a fullscreen window is a Space of its own that the daemon does not tile. The checks stay marked, because the shared scenarios ask what Windows and KDE do, but the reasons say that. --- e2e/platforms/tart_macos/run.py | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/e2e/platforms/tart_macos/run.py b/e2e/platforms/tart_macos/run.py index 5ca9929b..594529e2 100644 --- a/e2e/platforms/tart_macos/run.py +++ b/e2e/platforms/tart_macos/run.py @@ -62,12 +62,14 @@ UNSUPPORTED = { # what the macOS daemon does differently, which checks of a scenario are about, and the difference DIFFERENCES = { "stack": ( - "the macOS daemon stacks by raising the focused window over the others: the other windows " - "of a stack stay on the display, at the same place, where Windows and KDE put them away" + "by design: the macOS daemon stacks by raising the focused window over the others, so the " + "other windows of a stack stay on the display at the same place, where Windows and KDE " + "put them away" ), "fullscreen": ( - "the macOS daemon has no fullscreen detection: it tiles a window that covers the whole " - "display with the others" + "not applicable: macOS fullscreen is a Space of its own, which the daemon does not tile, " + "so there is no fullscreen window for it to leave alone; the test window's borderless " + "stand-in is tiled like any window" ), "margins": ( "the daemon tiles 10 px below the top of the work area the system reports and 12 px above "