Read URL from webView2 in vb

by

Summary

A Visual Basic application using WebView2 failed to read the current URL because the developer attempted to access webView.Source.ToString, which returned Nothing. The issue stemmed from misunderstanding how WebView2 exposes navigation state and when its properties become valid.

Root Cause

  • Source is not populated until navigation actually occurs
  • WebView2 initializes asynchronously, meaning its properties may be Nothing until the control is fully ready
  • Incorrect property used — the correct event-based pattern was not followed
  • NavigationCompleted or CoreWebView2InitializationCompleted events were not handled

Why This Happens in Real Systems

  • UI frameworks often initialize components out of order
  • Asynchronous components like WebView2 require event‑driven access, not direct property reads
  • Developers assume properties are populated immediately, but WebView2 loads its internal browser engine first
  • Real systems frequently expose state only after initialization callbacks

Real-World Impact

  • Applications fail to track navigation
  • Logging and analytics systems receive empty or incorrect URLs
  • Features depending on the current URL (auth flows, redirects, scraping) break silently
  • Debugging becomes difficult because the failure mode is simply Nothing

Example or Code (if necessary and relevant)

Below is the correct pattern to read the current URL from WebView2 in VB.NET:

Private Async Sub Form1_Load(sender As Object, e As EventArgs) Handles MyBase.Load
    Await WebView21.EnsureCoreWebView2Async()
    AddHandler WebView21.CoreWebView2.NavigationCompleted, AddressOf OnNavCompleted
End Sub

Private Sub OnNavCompleted(sender As Object, e As Microsoft.Web.WebView2.Core.CoreWebView2NavigationCompletedEventArgs)
    Dim currentUrl As String = WebView21.Source.ToString()
    Console.WriteLine(currentUrl)
End Sub

How Senior Engineers Fix It

  • Use event-driven patterns instead of reading properties prematurely
  • Wait for initialization using EnsureCoreWebView2Async
  • Attach handlers to NavigationStarting or NavigationCompleted
  • Validate assumptions by checking:
    • Whether the control is initialized
    • Whether navigation has occurred
    • Whether the property is documented as always available

Why Juniors Miss It

  • They assume UI controls behave synchronously
  • They expect properties like Source to always contain a value
  • They overlook initialization events in WebView2’s lifecycle
  • They may not read the API documentation closely enough to understand when values become valid

Leave a Comment