Bug 201195
| Summary: | REGRESSION(iOS 13): Can't type in fields on united.com sign-up form in WKWebView | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ali Juma <ajuma> |
| Component: | Forms | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ap, cdumez, dbates, justincohen, megan_gardner, rniwa, thorton, webkit-bug-importer, wenson_hsieh, zalan |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://www.united.com/ual/en/US/account/enroll/default | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=200531 | ||
Ali Juma
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
Do quirks not work in WKWebView? We would have plenty of regressions if so!
Radar WebKit Bug Importer
<rdar://problem/54772036>
Wenson Hsieh
(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.
Ryosuke Niwa
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.
Ali Juma
(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.
Ryosuke Niwa
(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>.