xamarin/Xamarin.Forms

WebView losing selection on iOS on button tap

Open

#5,175 opened on Feb 8, 2019

View on GitHubContributor guide
 (6 comments) (0 reactions) (0 assignees)C# (1,926 forks)batch import
a/webviewe/3 :clock3:help wantedp/iOS 🍎t/bug :bug:up-for-grabs

Repository metrics

Stars
 (5,644 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Description

When we tap on a button with selected text on a webview, the keyboard closes and the text looses the selection.

It's working perfectly on Android but not on iOS.

This behavior doesn't happen by default on native iOS.

The native implementation is the following: alt text

Steps to Reproduce

  1. Create a content page with a webview with a content editable html page and a button
  2. Tap on the content editable element
  3. Write some text
  4. Select the text
  5. Tap on the button on the content page

Expected Behavior

The keyboard shouldn't close and the text shouldn't loose it's selection nor should the keyboard close.

Actual Behavior

The text looses selection and the keyboard closes.

Basic Information

  • Version with issue: 3.4.0.1008975

  • Last known good version: None, never worked well.

  • IDE: Visual Studio 2017,Visual Studio 2019 Preview

  • Platform Target Frameworks: iOS

    • iOS: 12.1

  • Nuget Packages:

    • Prism.Forms - Version 7.1.0.431
    • Prism.Unity.Forms - Version 7.1.0.431
    • Xamarin.Forms - Version 3.4.0.1008975

  • Affected Devices: iPhone SE, iOS Simulator

Screenshots

Working:

alt text

Not working

alt text

Reproduction Link

https://github.com/carlos-ferreira/bug-reports/tree/master/Xamarin/Webview

Contributor guide

Research direction
Inspect the custom renderer for WebView in Xamarin.Forms.iOS, specifically the methods related to keyboard handling and focus. Check how the UIResponder chain is managed when a button is tapped, and compare with native iOS behavior.
Tech stack
csharp
Domain
mobile
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Xamarin.FormsiOS development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60