iOS 10 GM regression: WKWebView does not scroll when text input to contenteditable element intersects with on-screen keyboard

Originator:craig
Number:rdar://28300343 Date Originated:14-Sep-2016 04:13 PM
Status:Open Resolved:
Product:iOS SDK Product Version:10.0 (14A345)
Classification:Serious Bug Reproducible:Always
 
Summary:
Since iOS 10, any text typed into in a contenteditable element within a WKWebView will not trigger an automatic scrollview scroll to keep the caret on screen. So if the input text/caret goes underneath the on-screen keyboard, or off the bottom of the view, the user has to manually scroll the view to keep the input text in sight, which is a serious usability issue.

Steps to Reproduce:
See the attached project: tap the text to start editing and trigger the display of the on-screen keyboard, and type/press return until the caret goes underneath the keyboard.

Expected Results:
When text is input while the caret is not visible, the scrollview should automatically scroll so that the caret, and the input text, is visible.

Actual Results:
The input text is added to the content editable element but the scroll view does not scroll. To see the input text, the scroll view has to be scrolled by swiping.

Regression:
This issue does not occur in iOS 9.3 and lower. It does occur in the iOS 10.0 GM.

Notes:
I’ll attach a project to demonstrate this issue, which is also available from https://github.com/Bipsync/ios-wkwebview-scrolling.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!