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
Freeze-frames, annotated screens and crops came out solid black in apps with a transparent
window above their content (UIKit's UITextEffectsWindow appears once any text input has been
used; toast windows). The capture context was opaque, which paints a transparent window black;
captures now use a non-opaque one.
The first tap after entering annotate mode fell back to a spot instead of the element: SwiftUI
builds its accessibility nodes only after the first query following the bootstrap. Annotate mode
now warms the tree as it starts (about 0.1 s) and holds a tap that arrives before it's ready.
With the comment keyboard up, SwiftUI keyboard avoidance slid the whole overlay (frozen image,
boxes and pins) up by about 140 pt, so the next tap landed on what was really lower on screen.
The overlay no longer avoids the keyboard: the comment card and toolbar sit above it, and the
card keeps clear of the selection chip. If the app itself re-lays out for the keyboard, a tap
waits for the keyboard to go before scanning.
A launch-time start (ANNOTATE=1) froze the launch screen or the app's splash. It now waits for
the first screen the app settles on (unchanged for 1 s, after at least 1.5 s and at most 8 s of
the app being active), so a permission alert holding the app inactive doesn't count. ANNOTATE_DELAY=<seconds> waits a fixed time instead.
Late keyboard input from a comment card that a tap had just replaced could land in the next
pin's comment; it's dropped now.
Changed
The screen's text outline is taken as annotate mode starts, once the accessibility tree is warm,
instead of on the first pin.