xamarin/Xamarin.Forms

[iOS] Setting WebView Source to null/empty string isn't consistent between all three platforms

Open

#3,317 opened on Jul 16, 2018

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

Repository metrics

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

Description

Description

If a WebView source is set to a valid uri and then set back to null it just stays on the uri.

Steps to Reproduce

  1. WebView.Source = "http://www.xamarin.com"
  2. let it render
  3. WebView.source = null

Expected Behavior

WebView should now be blank

Actual Behavior

WebView still shows xamarin.com

Basic Information

  • Version with issue: 3.1 -Android: does nothing when set to null and clears out when set to empty -iOS: throws an exception when set to empty -UWP: does nothing when set to null or an empty string

Contributor guide

Research direction
Investigate the iOS WebView platform specific handler to understand why setting Source to null does not clear the current content; compare with Android and UWP handlers.
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.
1-3 hours
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
C#Xamarin.FormsGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75