Desktop Material Screenshot documentation

JavaScript is off, so the preference controls and the screenshot search are inactive. Every screenshot, every recorded fact and every link on this page still works. 而家冇 JavaScript,所以設定同搜尋唔會運作。相片、記錄同連結全部照樣睇得到。

Frame 87 of 147 · windows-ui-state-lowlevel

Merge into main preview opened from a linked worktree context menu

960 × 660 px · 91,483 bytes · batch windows-ui-state-lowlevel

呢一頁只講一張相:邊個 scene 出,邊個 batch 收,尺寸、指令、憑證全部照抄記錄,冇記錄就照直講冇。

Merge into main preview opened from a linked worktree menu
Merge into main preview opened from a linked worktree context menu

What the sources record

Asset file
docs/assets/screenshots/worktree-merge-preview-from-context-menu.png
Pixel dimensions
960 × 660 px, read from the PNG IHDR header
File size
91,483 bytes on disk
PNG encoding
8-bit truecolour (IHDR colour type 2)
Gallery output id
worktree-merge-preview-from-context-menu
Scene
linked-worktree-context-menu-merge-preview
Capture batch
windows-ui-state-lowlevel
Platform
windows-headless
Feature Gallery section
Search, history, accounts, and automation
Guided workflow caption
Merge into main preview opened from a linked worktree context menu
Publication status
Published target in the current Windows guided gallery

Alternative text

Merge into main preview opened from a linked worktree menu

The alternative text above is the Feature Gallery's own Markdown alt text for this frame, so the image describes itself identically in the wiki and here.

The interaction the harness performs

Activate Merge from the linked worktree context menu and leave the reviewed Merge into main sheet showing the exact feature branch and one pending commit without executing the merge.

Fixture the capture batch requires

Fresh throwaway repositories and isolated renderer profile; all persisted UI state is created through app-owned interactions or an explicitly named app-native state hook.

Privacy gate the capture must pass

Run the pre-capture renderer privacy gate used by script/capture-app.js and inspect the original client-only PNG.

Regenerating this capture

Run these commands in order, exactly as the capture batch records them. Placeholders in angle brackets are the verifier's own run root, fixture path and CDP port.

  1. Step 1 of 2
    npx --no-install cross-env RELEASE_CHANNEL=development DESKTOP_SKIP_PACKAGE=1 yarn build:prod
  2. Step 2 of 2
    Lowlevel launch the production bundle with isolated user data and the entry fixture, perform the entry interaction exactly, then capture_screenshot(client_only=true, hwnd=<resolved-app-hwnd>, path=<owned-temp-run-root>\captures\<output>.png)

Dated acceptance receipt

One dated acceptance receipt names this exact PNG:

Where else this frame appears