BlazorWebView and question on wrapping native controls returned from native sources #2373
Unanswered
somelinguist
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
A few months ago, I started working on Eto Forms control to wrap BlazorWebView. The code is at https://github.com/somelinguist/Eto.Blazor. I was able to make a lot of progress, but there are still some (probably a lot of) loose ends.
One specific thing is that the official BlazorWebView components on Windows Forms, WPF, and MAUI let you configure and access the internal webview during and after initialization of the control, but I haven't figured out the best way to do this using Eto.Forms' WebView control.
The WinForms and WPF implementations just wrap the official, native BlazorWebView control. Once initialized, it’s possible to get the underlying WebView2 control. My custom macOS implementation is based on the MAUI iOS one, which would return the underlying WKWebView.
I’m not sure if it’s possible to wrap a native control returned in such a way. Even if it were, would it allow configuration changes in any helpful way?
For the official BlazorWebview, it’s also possible to pass some configuration arguments to the underlying webview while the BlazorWebView is in the process of initializing. These options vary even more depending on the implementation. I’m not sure what would be helpful here at all.
Do you have any thoughts?
Also, any other feedback on the control would be welcome.
I’m not a professional programmer, so I unfortunately don’t have a lot of time to work on it. But the control is proving helpful in one of my hobby projects. I’m on vacation this week, so I’ve had a little more time to work on it. :)
Beta Was this translation helpful? Give feedback.
All reactions