There are some big (breaking) changes coming. I will make a blog post soon, but here's some brief info.
I'm adding CEF browser engine. It currently works fine on linux. Once CEF is done I will look deeper at adding Edge if that's possible at all. And we will be done with all modern browser engines.
Since it's becoming very hard to maintain webview - I'll make an API to expose native window handle and allow to pass your own window (or container) handle to embed a webview into.
This means that various API functions such as setting background color or window icon or resizing window or borderless/transparent windows etc will be all gone and will not be parts of this library.
I think we should make a wiki where all such code snippets would be stored. But they will not provided by the core library and it's up to the app developer to ensure that they work or to tweak them to his/her needs.
Even dialogs will be moved to a separate module and will not be part of the core webview library. They will still be in a separate header file and still includes in the Go package. I'm making this exception because I believe it's a very frequent feature. Same applies to
webview_set_title - I believe that every app needs to set a window title, so it remains. Everything else is to be removed and related issues closed as wontfix.
I'm sorry about this, but I'd rather have a small focused library with good code quality and automated test coverage than a bloated monster full of features that are seldomly used. If someone needs a transparent window - please implement it, test it and make a wiki page documenting your steps. Webview is all about running HTML5/JS inside a native app window. It's not about customizing the native window or interacting with the OS (tray or notifications). At least, not at the moment when I'm a single maintainer with a fulltime job. I hope you will understand.
It appears that IE is planned to be not supported in the future according to @zserge:
For each window toolkit there exists at least one corresponding browser engine. For GTK and Cocoa it's Webkit. For Win32 it's either MSHTML (aka IE), or EdgeHTML (since Windows 10), or Edge/Chromium (Windows 7/10, but needs to be installed separately as of now).
I suggest to drop the support of MSHTML, since it's not only hard to maintain, but also hard to use, as it does not match the expectations of a modern web developer.