[Webkit-unassigned] [Bug 230360] New: REGRESSION [iOS15]: contentEditable text input traits not passed properly to the underlying control

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=230360

            Bug ID: 230360
           Summary: REGRESSION [iOS15]: contentEditable text input traits
                    not passed properly to the underlying control
           Product: WebKit
           Version: Other
          Hardware: iPhone / iPad
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P2
         Component: HTML Editing
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: carlos at blink.sh
                CC: wenson_hsieh at apple.com

* SUMMARY
Text input traits that controlled the behavior of the input, like spellcheck, autocorrect, autocomplete and autocapitalize, have been used in prior versions to control QuickType functionality on iOS. On iOS15 it is no longer possible to control the behavior of the QuickType bar, or to make it disappear. The API for UITextInputTraits has changed, but it looks like it has not propagated to the WKWebView control yet:
"""
In iOS 14 and iPadOS 14 and earlier, when autocorrectionType is set to UITextAutocorrectionTypeNo, the QuickType bar is disabled. For apps linked against iOS 15 and iPadOS 15 or later, the QuickType bar is enabled and shows spellchecking candidates. If the new behavior isn’t desirable for your use case, set spellCheckingType to UITextSpellCheckingTypeNo to hide the QuickType bar. (68874861)
""" UIKit section from - https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-15-release-notes

* STEPS (under iOS15)
1. Create a jsfiddle with a single <input type="text" autocorrect="off" autocomplete="off" autocapitalize="none" spellcheck="off"/>
2. Tap into the field. The QuickType bar should be hidden or shown without any suggestions.

* RESULTS
- Under iOS15, the QuickType bar is still shown and there is no combination to disable it, because it is not propagating the new fields properly.
- If linked under iOS14, everything will still work.

- It is expected to respect the same behavior as iOS14.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210916/056746e2/attachment.htm>