306569 2026-01-29 14:36:18 -0800 [Form Controls][iOS] Form controls in cross-origin subframes have incorrect interaction rects 2026-04-14 13:54:00 -0700 1 1 1 Unclassified WebKit New Bugs WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED InRadar P2 Normal --- 1 zakr webkit-unassigned webkit-bug-importer oldest_to_newest 2176336 0 zakr 2026-01-29 14:36:18 -0800 When a form control (such as a <select> or <input>) is focused inside a site-isolated cross-origin iframe, the `FocusedElementInformation` struct sent from the WebContent Process contains coordinates relative to that subframe's viewport. On iOS, `WebPageProxy` passes this information to `PageClient` (and eventually `WKContentView`) to manage native UI overlays such as the form accessory bar, keyboard interactions, and selection handles. Because the UIProcess expects these coordinates to be relative to the main frame, the UI elements are positioned incorrectly. They are usually offset by the iframe's position within the main page, causing the form assistant to appear in the wrong location or not appear at all. This patch introduces `convertFocusedElementInformationRectsToMainFrameCoordinates` in `WebPageProxy`. This helper asynchronously converts the `interactionRect`, `nextNodeRect`, and `previousNodeRect` from the focused frame's coordinate space to the main frame's coordinate space using the existing geometry mapping logic in `WebFrameProxy`. We now wait for this conversion to complete before calling `pageClient->elementDidFocus` or `pageClient->updateFocusedElementInformation`. 2176337 1 zakr 2026-01-29 14:36:37 -0800 <rdar://168716669> 2176339 2 zakr 2026-01-29 14:39:06 -0800 Pull request: https://github.com/WebKit/WebKit/pull/57510 2200345 3 ews-feeder 2026-04-14 13:53:58 -0700 Committed 311229@main (4597139ad795): <https://commits.webkit.org/311229@main> Reviewed commits have been landed. Closing PR #57510 and removing active labels.