WKWebView should support inputAccessoryItem in place of inputAccessoryView and expose it

Originator:craig
Number:rdar://21320159 Date Originated:10-Jun-2015 04:11 PM
Status:Open Resolved:
Product:iOS SDK Product Version:9.0
Classification:Enhancement Reproducible:Not Applicable
 
Summary:
For applications that use a WKWebView to provide a rich text editor experience (i.e. displaying HTML and allowing it to be edited) there is currently no proper way to hook into the inputAccessoryView which displays navigation controls by default, which are often redundant when a single ‘page’ is being displayed. It can be removed or replaced via swizzling, but this is not ideal.

It would be great if the new inputAccessoryItem functionality on UITextInput and its related classes were also available on WKContentView via WKWebView, so we could add our own buttons for custom functionality like image insertion and the like.

Steps to Reproduce:

Expected Results:

Actual Results:

Regression:

Notes:

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!