I salute you for this effort, it won’t be trivial! For example, WKWebView doesn’t allow use of service workers… <i>unless</i> the domain you’re loading is included in the WKAppBoundDomains key of your app’s Info.plist file. Would be great to have all this info in one centralized place though!
Would be nice to have webkitgtk.
We have been shipping a Tauri app for the past couple years and while the idea of not shipping a chromium seems nice in practice it is very hard to have a nice experience across all OS. Linux being the hardest because webkitgtk is really not that great to be polite.
Hi Niklas here. I'm the other Co-Chair of the W3C WebView Community group that built this site. We took heavy inspiration and code from caniemail.com and are still discussing and working on building up this site. It's a very early stage with very little content. If you want to help us feel free to check out the GitHub repository: <a href="https://github.com/WebView-CG/Compatibility-Data-Project">https://github.com/WebView-CG/Compatibility-Data-Project</a>
Howdy friends,<p>Ben here, one of the co-chairs for the WebView CG. Super chuffed to see this pop up on hackernews today!<p>For a little context, our group is currently focusing our efforts this year on improving WebView compatibility data. The project is still very young and we’ll keep chipping away at it but please feel free to reach out and engage! You can find the repository here:
<a href="https://github.com/WebView-CG/Compatibility-Data-Project/tree/main">https://github.com/WebView-CG/Compatibility-Data-Project/tre...</a><p>If you’re interested in joining in on the broader community discussions, you can find our group here:
<a href="https://www.w3.org/community/webview/" rel="nofollow">https://www.w3.org/community/webview/</a><p>I’m currently working hard at keeping a new born alive but will be happy to answer any questions if I can a moment between diapers :)
One feature I look for in any webview is the ability to make parts of the UI transparent while still allowing mouse events over transparent pixels to seamlessly fall through to the window below while those events (not just clicking but hovering) over non-transparent pixels be intercepted as usual.<p>IMO the old ActiceX IE browser control had an exceptionally good (most performant
and natural) implementation of this feature. Unfortunately replicating it in chromium based webviews appears to be a lot trickier.
what is the webview here, is it the webview librariers on each platform instead of the browser?<p>I tried to do some UIs with OS specific webviews and it's kind of lacking, so I ended up with EletronJS in the end which contains a full blown browser, but it's resource hungry.<p><a href="https://github.com/webui-dev/webui">https://github.com/webui-dev/webui</a> is another light weight option, it is a thin layer to provide you with a cross platform UI, and invokes browser to render everything, it's small yet has all the features of a true browser.
I was sincerely hoping this would just be the static answer "No"<p><a href="https://shouldiwebview.com/" rel="nofollow">https://shouldiwebview.com/</a> doesn't yet resolve...
Feedback: Was looking around all the site to find a section who explains what is Webview and can't find it. Should be some explanation.<p>What is that? Like a hidden browser that comes with the different OSs?
How timely. I was just trying to figure out how Webviews handled browser notifications yesterday (they don't which is obvious in hindsight I guess). That one doesn't yet resolve on this site, but I've bookmarked it
This is great. I want to add WebWebView to the list and show 100% compatibility, because we run Chrome on the server and open a portal to it via an iframe. You can see it running here: <a href="https://browse.cloudtabs.net/signupless_sessions" rel="nofollow">https://browse.cloudtabs.net/signupless_sessions</a> and code here: <a href="https://github.com/BrowserBox/BrowserBox">https://github.com/BrowserBox/BrowserBox</a> - But we have yet to release a developer API. Seeing this, we will double our efforts!
Cool idea. Seems a little lacking. All of the following resolve on caniuse, but return nothing on this: quic, http3, webrtc, nesting (css), :not<p>edit... I see this page seems to include everything that is supported ( <a href="https://caniwebview.com/features/" rel="nofollow">https://caniwebview.com/features/</a> ). Looks like a total of 7 pages. Hope to see this page evolve over time.