201195 2019-08-27 12:53:09 -0700 REGRESSION(iOS 13): Can't type in fields on united.com sign-up form in WKWebView 2019-08-29 12:54:20 -0700 1 1 1 Unclassified WebKit Forms WebKit Nightly Build Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=200531 https://www.united.com/ual/en/US/account/enroll/default InRadar P2 Normal --- 1 ajuma webkit-unassigned ap cdumez dbates justincohen megan_gardner rniwa thorton webkit-bug-importer wenson_hsieh zalan oldest_to_newest 1565475 0 ajuma 2019-08-27 12:53:09 -0700 This bug reproduces on iOS 13 beta 8 in WKWebView (tested in Chrome, Firefox, and Edge) but for some reason doesn't reproduce in Safari. Steps to reproduce: 1. Visit https://www.united.com/ual/en/US/account/enroll/default 2. Scroll down to the form and tap on a field (e.g., "First name") Expected result: The field is focused and the keyboard is shown. Actual result: Can't focus the field, and the keyboard is not shown. 1565603 1 ap 2019-08-27 17:53:16 -0700 Do quirks not work in WKWebView? We would have plenty of regressions if so! 1565604 2 webkit-bug-importer 2019-08-27 17:53:53 -0700 <rdar://problem/54772036> 1565612 3 wenson_hsieh 2019-08-27 18:35:51 -0700 (In reply to Alexey Proskuryakov from comment #1) > Do quirks not work in WKWebView? We would have plenty of regressions if so! That’s right — quirks are disabled by default (NeedsSiteSpecificQuirks in WebPreferences.yaml), but enabled in Safari via SPI. It looks like Quirks::shouldIgnoreContentChange might be relevant here. 1565644 4 rniwa 2019-08-27 22:05:54 -0700 FWIW, you can probably implement a site specific quirk on united.com in Chrome for iOS by hiding the content mentioned in https://trac.webkit.org/changeset/248463/webkit using `display: none`. Obviously, reaching out to united.com would work too. 1566255 5 ajuma 2019-08-29 08:58:50 -0700 (In reply to Ryosuke Niwa from comment #4) > FWIW, you can probably implement a site specific quirk on united.com in > Chrome for iOS by hiding the content mentioned in > https://trac.webkit.org/changeset/248463/webkit using `display: none`. Thanks for pointing this out! (In reply to Wenson Hsieh from comment #3) > (In reply to Alexey Proskuryakov from comment #1) > > Do quirks not work in WKWebView? We would have plenty of regressions if so! > > That’s right — quirks are disabled by default (NeedsSiteSpecificQuirks in > WebPreferences.yaml), but enabled in Safari via SPI. I've filed feedback FB7155444 for getting quirks enabled or for changing the SPI to public API. 1566340 6 rniwa 2019-08-29 12:52:36 -0700 (In reply to Ali Juma from comment #5) > (In reply to Ryosuke Niwa from comment #4) > > FWIW, you can probably implement a site specific quirk on united.com in > > Chrome for iOS by hiding the content mentioned in > > https://trac.webkit.org/changeset/248463/webkit using `display: none`. > > Thanks for pointing this out! > > > (In reply to Wenson Hsieh from comment #3) > > (In reply to Alexey Proskuryakov from comment #1) > > > Do quirks not work in WKWebView? We would have plenty of regressions if so! > > > > That’s right — quirks are disabled by default (NeedsSiteSpecificQuirks in > > WebPreferences.yaml), but enabled in Safari via SPI. > > I've filed feedback FB7155444 for getting quirks enabled or for changing the > SPI to public API. That would be <rdar://problem/54838486>.