The approach proposed here is probably not going to happen. If WebView2 drew into an enormous surface the width/height of the entire page, that would provide the desired smooth scrolling experience but would have a huge performance cost for that surface. That surface cost could be mitigated if WebView2 drew into a XAML VirtualSurfaceImageSource, which would require significant design changes and other complexities due to the WebView2 Runtime rendering outside of the app process.

Originally posted by @codendone in #5654 (comment)

We are in the process of migrating from WebView to WebView2. Our application allows a user to interact with HTML content (such as highlighting), and allows swiping to the previous or next content. Our implementation for this was, from a high level, a FlipView wherein each FlipViewItem contained a WebView.
Since WebView2 consumes all scroll and pan actions, we have lost our ability to swipe to content unless we disable the webview, in which case the user can't interact with the content.
To confirm your previous statement, there isn't a way presently to use a WebView2 (allowing user interaction) within a ScrollViewer? If that is the case, is there a possibility of adding this functionality?
Thanks very much!