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 85 of 107 · windows-ui-state-lowlevel

Built History Graph tab with its real tab strip and ancestry graph

1443 × 992 px · 138,835 bytes · batch windows-ui-state-lowlevel

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

History Graph view from the built Windows app
Built History Graph tab with its real tab strip and ancestry graph

What the sources record

Asset file
docs/assets/screenshots/material-history-view-tabs-graph.png
Pixel dimensions
1,443 × 992 px, read from the PNG IHDR header
File size
138,835 bytes on disk
PNG encoding
8-bit truecolour (IHDR colour type 2)
Gallery output id
material-history-view-tabs-graph
Scene
history-view-tabs-graph
Capture batch
windows-ui-state-lowlevel
Platform
windows-headless
Feature Gallery section
Search, history, accounts, and automation
Guided workflow caption
Built History Graph tab with its real tab strip and ancestry graph
Publication status
Published target in the current Windows guided gallery

Alternative text

History Graph view from the built Windows app

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

Open the built History surface in the isolated production profile, select its Graph tab, and preserve the real tab strip, ancestry graph, and accessible selected state at the reviewed capture size.

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

No dated receipt under docs/verification/ names material-history-view-tabs-graph.png. The frame is published without its own dated acceptance document; the build, interaction and privacy evidence for its batch is recorded in HANDOFF.md and in the Feature Gallery's refresh notes instead.

Where else this frame appears