Navigation parameter is missing from NavigationFailedEventArgs

[sjb-sjb]

Describe the bug

In the Frame.NavigationFailed event, the NavigationFailedEventArgs does not contain a Parameter property that provides the navigation parameter.

This is inconsistent with the other navigation events and makes it impossible to manage the navigation parameter consistently with the other navigation events. For example, if the navigation parameter may refer (directly or indirectly) to an object that needs to be informed of the navigation failure event.

Steps to reproduce the bug

Subscribe to the event and try to examine the Parameter property of NavigationFailedEventArgs.

Expected behavior

Should have the parameter there.

Screenshots

No response

NuGet package version

None

Windows version

No response

Additional context

No response

[DarranRowe]

One issue with calling this a bug is that Microsoft.UI.Xaml.Navigation.NavigationFailedEventArgs matches Windows.UI.Xaml.Navigation.NavigationFailedEventArgs.
Another thing here is that windows.ui.xaml.navigation.idl in the Windows SDK only has a single interface for this runtime class. The rules of COM, which are also the rules of WinRT components, means that once an interface is defined, it can't be redefined. Especially not without changing the UUID.
The WinRT components have also been very careful about extending functionality using numbered interfaces. An example of this is the Windows.UI.Xaml.Navigation.NavigatingCancelEventArgs. This has a INavigatingCancelEventArgs interface, and an INavigatingCancelEventArgs2 interface. As a side note, when NavigatingCancelEventArgs was ported to WinUI 3, these interfaces were combined into one.
Anyway, the lack of Parameter from the NavigationFailedEventArgs was apparently part of the original UWP/WinUI design. So I feel as if this would be better as a feature request.