You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a7370b2
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ios): publish a windowed iPad app's capture in screen space (#3899)
An iPad window that does not fill the screen reports its own screen box
while its subtree arrives anchored at its own top-left. The capture
published a screen-space viewport around window-relative rects: the fold
clipped content to (w - x) x (h - y), a rect named no screenshot
position, and a synthesized tap landed at the point minus the window
origin.
SnapshotContentTranslation reads the one vector from a carrier's
(0,0)-anchored copy of the viewport box to the viewport itself, and
SnapshotGeometrySpace.normalized translates the subtree it declares in
the same pass that turns a quarter-turned subtree.
CoordinateSpaceRotation now turns axes only; the digitizer origin stays
where the display put it. Replayed from
contracts/fixtures/window-coordinate-space.json in both languages.
Refs #3899
Copy file name to clipboardExpand all lines: apple/runner/AgentDeviceRunner/AgentDeviceRunnerUITests/UnitTests/RunnerTests+SnapshotPresentationTests.swift
+127Lines changed: 127 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -662,6 +662,133 @@ extension RunnerTests {
662
662
XCTAssertNotNil(keyQ,"`q` key must be presented under --depth \(options.depth??-1)")
663
663
}
664
664
665
+
/// #3899: an iPad window that does not fill the screen publishes screen space. The measured shape is
666
+
/// iPad Pro 11-inch (M5, iOS 27.0) with Windowed Apps on and a Calendar window at (224,207,386x682):
667
+
/// the app's own window arrives as a (0,0)-anchored copy of that box and its subtree with it, so the
668
+
/// Add button reports (335,14,37,36) for a control drawn at (559,221). The one normalization pass
669
+
/// reads the declaration and publishes the subtree at its place on the screen, which is what lets the
670
+
/// fold keep every node instead of clipping each one to (w − x) × (h − y) and refusing the capture.
0 commit comments