Changeset 187768 in webkit
- Timestamp:
- Aug 3, 2015 2:49:28 PM (9 years ago)
- Location:
- branches/safari-601.1.46-branch/Source/WebKit2
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/safari-601.1.46-branch/Source/WebKit2/ChangeLog
r187671 r187768 1 2015-08-03 Matthew Hanson <matthew_hanson@apple.com> 2 3 Merge r187751. rdar://problem/22018044 4 5 2015-08-03 Wenson Hsieh <wenson_hsieh@apple.com> 6 7 Inputs with the autofocus attribute cause the keyboard to not deploy 8 https://bugs.webkit.org/show_bug.cgi?id=147555 9 <rdar://problem/22018044> 10 11 Reviewed by Andreas Kling. 12 13 Upon submitting a form by pressing "Go" on the keyboard, an <input> on the next page with the 14 autofocus attribute may become non-interactible. When attempting to tap on the input, nothing 15 seems to happen. This is because the state of WebPage upon invoking WebPage::elementDidFocus 16 indicates (incorrectly) that the input element is already focused, and therefore hits an early 17 return. To solve this, we explicitly reset m_hasFocusedDueToUserInteraction upon transitioning 18 to a new page. 19 20 * WebProcess/WebPage/WebPage.cpp: 21 (WebKit::WebPage::didStartPageTransition): On iOS, resets m_hasFocusedDueToUserInteraction as 22 well. It was previously thought that this would be handled by blur() called on the assisted 23 element when submitting a form. However, pressing "Go" on the iOS keyboard is an implicit 24 submission and does not trigger a blur event. 25 1 26 2015-07-31 Matthew Hanson <matthew_hanson@apple.com> 2 27 -
branches/safari-601.1.46-branch/Source/WebKit2/WebProcess/WebPage/WebPage.cpp
r187390 r187768 2427 2427 { 2428 2428 m_drawingArea->setLayerTreeStateIsFrozen(true); 2429 #if PLATFORM(IOS) 2430 m_hasFocusedDueToUserInteraction = false; 2431 #endif 2429 2432 } 2430 2433
Note: See TracChangeset
for help on using the changeset viewer.