Bug 195819

Summary: REGRESSION (r242173): Programmatically focusing <select> after user dismisses it does not open it again and leaves view in bad state
Product: WebKit Reporter: Daniel Bates <dbates>
Component: WebKit Misc.Assignee: Wenson Hsieh <wenson_hsieh>
Status: ASSIGNED    
Severity: Normal CC: thorton, webkit-bug-importer
Priority: P2 Keywords: InRadar, PlatformOnly, Regression
Version: WebKit Local Build   
Hardware: iPhone / iPad   
OS: iOS 12   
Bug Depends on: 195118, 196272    
Bug Blocks:    
Attachments:
Description Flags
Test none

Daniel Bates
Reported 2019-03-15 13:53:08 PDT
Created attachment 364836 [details] Test Seen on iPad. Steps to reproduce: The following assume you have a hardware keyboard attached. 1. Open the attached test case. 2. Follow the instructions. The test fails following <https://trac.webkit.org/changeset/242173/> (bug #195118). Prior to the change, it passed. Notes: When the bug occurs the WKContentView is *NOT* the first responder. If you then tap somewhere on page we make the WKContentView first responder and the popover opens!
Attachments
Test (583 bytes, text/html)
2019-03-15 13:53 PDT, Daniel Bates 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2019-03-15 13:53:25 PDT
<rdar://problem/48937037>
Radar WebKit Bug Importer
Comment 2 2019-03-15 13:53:25 PDT
<rdar://problem/48937038>
Wenson Hsieh
Comment 3 2019-03-15 14:54:27 PDT
This is because of my new first responder restriction when determining whether to allow programmatic focus to present an input view. Namely, after r242173, when WKContentView is not first responder, we’ll no longer allow programmatic focus to show an input view (this is to prevent web content from stealing focus away from page chrome using programmatic focus). Need to think more about what our policy should be in this scenario...any change that would prevent users from being able to switch tabs or type in the unified field and navigate away in this case is a non-starter.
Daniel Bates
Comment 4 2019-03-26 21:26:13 PDT
I will fix this issue in the patch for bug #196272. Keeping this bug open to remind myself to add a test for this bug.
Note You need to log in before you can comment on or make changes to this bug.