[FEATURE]: WebView.UnviewableContentIdentified Event

[mlipok]

What feature would you like, or what problem are you facing?

Please add support for:

https://learn.microsoft.com/en-us/uwp/api/windows.ui.xaml.controls.webview.unviewablecontentidentified?view=winrt-28000
also:
https://learn.microsoft.com/en-us/uwp/api/windows.ui.xaml.controls.webviewunviewablecontentidentifiedeventargs.mediatype?view=winrt-28000
and
https://learn.microsoft.com/en-us/uwp/api/windows.ui.xaml.controls.webviewunviewablecontentidentifiedeventargs.uri?view=winrt-28000

What's your proposed solution?

none

Screenshots

No response

Do you want to work on this issue/improvement?

Maybe

Any additional context?

No response

[ioa747]

Hello @mlipok,

The UnviewableContentIdentified event is a legacy EdgeHTML (UWP) feature and is not natively present in the Chromium-based WebView2 API.

Implementing a 1:1 custom replacement that triggers at the start of navigation would require monitoring every single web response header, which would introduce unnecessary overhead and complexity to the core engine.

However, in WebView2, this logic is effectively handled within the DownloadStarting event, which fires precisely when the browser identifies content it cannot render.

I am currently refactoring NetWebView2Lib (v2.1.0+) to an Object Oriented Event Model. Instead of adding extra events, I will upgrade OnDownloadStarting to return a complete Args Object ($oArg). This object will include the MimeType property, allowing you to manipulate it in AutoIt as follows:

Volatile Func Web_Events_OnDownloadStarting($oWebV2M, $hGUI, $oArg)
    ; Check the MimeType to identify "unviewable" content
    If $oArg.MimeType = "application/pdf" Then
        $oArg.Cancel = True ; Cancel the internal download
        ShellExecute($oArg.Uri) ; Launch the default system handler
    EndIf
EndFunc

Does providing the MimeType (and the ability to Cancel) within this object cover your specific use case, or do you have a different workflow in mind that requires detection at an earlier stage?

[mlipok]

Does providing the MimeType (and the ability to Cancel) within this object cover your specific use case, or do you have a different workflow in mind that requires detection at an earlier stage?

Nice