[Webkit-unassigned] [Bug 176896] Wrong caret position for input field inside a fixed position parent on iOS 11

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Dec 5 18:33:17 PST 2017


Simon Fraser (smfr) <simon.fraser at apple.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |ASSIGNED
           Assignee|webkit-unassigned at lists.web |simon.fraser at apple.com
                   |kit.org                     |

--- Comment #34 from Simon Fraser (smfr) <simon.fraser at apple.com> ---
There are a few things going on here.

* FrameView::updateLayoutViewport() is computing a new layout viewport rect in the web process if called at the end of a layout, when m_inProgrammaticScroll is true. This wasn't intended; the m_inProgrammaticScroll check was to detect actual programmatic scrolls.

* Normally we compute a layout viewport rect in the UI process and send it to the web process. When computed in the UI process, we normally take the keyboard into account for the visible rect (m_webPageProxy.unobscuredContentRectRespectingInputViewBounds()), but this rect isn't available in the web process, so when we compute a new layout rect there, we get a different answer.

We then compute a caret rect using layout viewport rect in the web process that doesn't match the one the UI process has, resulting in an offset caret.

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/20171206/5285e620/attachment-0001.html>

More information about the webkit-unassigned mailing list