[Webkit-unassigned] [Bug 258415] New: REGRESSION (iOS 17 beta): Custom UITextField / inputView broken on WKWebView form elements
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Jun 22 12:40:10 PDT 2023
https://bugs.webkit.org/show_bug.cgi?id=258415
Bug ID: 258415
Summary: REGRESSION (iOS 17 beta): Custom UITextField /
inputView broken on WKWebView form elements
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Forms
Assignee: webkit-unassigned at lists.webkit.org
Reporter: ajuma at chromium.org
CC: cdumez at apple.com, justincohen at google.com,
wenson_hsieh at apple.com
Created attachment 466800
--> https://bugs.webkit.org/attachment.cgi?id=466800&action=review
Sample project
Steps to reproduce (also see the attached sample project):
1. Setup a WKWebView to use a UITableView as its inputView.
2. Open a web form with multiple fields. The sample project uses https://rsolomakhin.github.io/autofill/ but any html form with multiple inputs will work.
3. Tap on a field to trigger the inputView on the WKWebView.
4. Navigate between fields using the input accessory view.
Expected behavior:
The UITableView is visible at all times as the inputView of the WKWebView.
Actual behavior:
The UITableView is displayed the first time a field is focused but disappears when navigating to the next field, then it's visible again, and so on. This is breaking the autofill UI in Chrome on iOS.
It's unclear if this is a WebKit bug (e.g., a regression from bug 254236) or a bug in UIKit, given the large changes in iOS17 pulling the keyboard out-of-process.
This bug is also filed as FB12419714.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230622/c18a63e8/attachment.htm>
More information about the webkit-unassigned
mailing list