Closed applefanbois closed 1 year ago
The lack of updates is troubling to say the least
Hi all, this bug is set as top priority issue right now for owner team and as of today the owner team has narrowed down the root cause and they are working on a fix for this and setting a goal to get it fix as soon as possible.
Thanks!
I remember webview worked before, because I have an application built with MAUI.Blazor that works, if you are fixing a problem that's blocking everyone maybe provide alternative solutions for example how to switch to the webview that works for my MAUI.Blazor project or maybe release a hot fix for Visual studio to use it for now
If this was a free software, that's another story. I would've respected you for just implemented the idea because you put your reputations on the line but open source shows you are less serious
Meanwhile, if we all wanted to solve this problem so bad isn't there a open source repository for MAUI + Blazor that we can look at
@Xyncgas I can check with WinUI team to see if there is any workaround they recommend, but for now from Webview2 perspective, switching WindowsAppSDK back to version before v1.2 will make it work again.
This bug was reported on Nov 15! On 21 Dec, someone complains that there are only 3 people on the planet who have just reported this problem (probably because there are really very few of us who use MAUI Blazor and therefore rely on WebView. XAML does not have this problem).
It shouldn't matter how many people have reported it or how many people have upvoted something. Those kinds of scales are used for resource management, not for deciding how critical something is. A simple ticket triage process would have highlighted the severity problem within minutes.
A member of the relevant team looks at newly opened tickets, reads the high level description and tags it with the appropriate severity / priority. A ticket what describes "user input being blocked permanently after typing too fast" should have anyone whos sensible, marking this as high priority and high severity for the following factors:
Even if only one person reports the issue, if the issue is verifiable, its easy to see how wide of an impact this is is having / going to have, on users.
The problem lies in the fact that this isn't a repository nor an issue tracker. This is a closed source project, that they've used a blank GitHub repo to host "feedback", thus there isn't an triage, and these posts aren't even considered bug tickets.
Oh my world. I was hoping to find what I'm doing wrong, but not this. It's WebView2 major major issue. It prevents us shipping Blazor Hybrid app no matter if it is WPF, winforms, MAUI... we're stuck. Please prioritise. Thanks.
This is an unacceptable level of testing. We now know that the people making WebView2 do not even use it. They did not even bother to load any web page and type something in a search engine or anywhere else.
Just creating a WebView2 and typing crash everything within 10 seconds of normal usage. MS did not even bother to even try it. We also know that MS are not using their own stuff, they prefer electron.
And the list of important features missing are huge : like extracting the HTTP code (404 for example). I have over 30 bugs and important limitations that I have provided to our shareholder.
I estimate that the cost of making an app with MS stuff is 10x bigger than Android, Linux or Apple. We lost 300 000$, the app was completed 3 years ago, I am still working hard to make it work.
Every MS framework call can and will crash the entire app at any time (even inside a try catch block). Nothing is working, absolutely nothing : sliders are not working, events are not working, buttons are not working, multi-threading is always re-entering the same code before it complet on the main thread....
We even found a bug yesterday where if somebody change their Windows Server language, the app will start missing words here and there at random. Deleting the app settings (create by MS, not me) solve the problem. There is not a single day without one of our customer reporting a bug or a crash (not related to my code).
And I am not even talking the performance, everything is 400x slower than android and apple (tested with the same code). MS is so slow, I had to disable animation and sound. It took me 3 months to be able to memorize window position and size with display scaling because MS removed the feature. In fact I am the only one on the internet who managed to make it work in all circonstances.
MS Frameworks are development hell. My employer is a huge Windows fan and he is used to stuff never working, he suffer like all Windows user from Stockholm syndrome where the unacceptable becomes normal. People on other OS don't have crashes every day, on other OS stuff is always working by default.
As a Linux, Android and Apple user, I am appalled by the way Windows behave, I am not used to stuff not working. I tasted the sugary fruit and I can't stand this rotten sour thing that is Windows and native development on Windows.
Do you think it is normal for a windows port to only have 1/10 of the features of the Android, iOS and macOS version? MS does not even offer any dev tools to deal with PDF (like Linux, Android and Apple does). Windows in 2023 still has no screen recorder??? What is this, the 90's?
@applefanbois Dude, seriously. Knock it off. The situation is bad, but posting rant after rant at a place that is most likely not even read by the team responsible for WebView is just wasting everybody's time.
I don't want other people to suffer as much as we did/are.
I want future generations to remember how MS made our lives miserable.
@BieleckiLtd It works in WPF. We migrated our app from maui to wpf VebView and haven’t had any freezes yet.
My app is not just a small calculator project, but the app is almost as complex as a 3D software like Blender. I have almost 1 million lines of code and zero code repetition, every call to framework and os fully wrapped. My app use many complex things like web context isolation, multi viewports and multi language (text, voice, speech) at the same time... And nothing is blocking.
I could copy/paste here everything that does not work with WinUI3 and all of them are basic things. The basic stuff do not work, sliders don't trigger onRelease events for example. Actually, they did but that was 2 years ago.
And most stuff that do work are so low in quality that I removed the feature.
Like I said, because you are used to being disrespected on Windows, you cannot grasp how things can truly be amazing on Linux, Android and Apple. Apple product are more expensive, but even at lower specs, they run faster because their code is better. For example unzipping a 1gig file on windows can take up to 5 minutes while on macOS it is 5 seconds. You would not know that because you did not test it. I am a multi-platform dev, so I not only experience these things, I can mesure it. My app on iOS/macOS is 16 meg, the exact same app on Windows is 96 megs.
You think it is normal for a webview to not support any typing from the keyboard? Typical abnormal windows user reaction.
Is it too much to ask for things to work like they do on Android and Apple?
MS made an event for onSliderReleased, but it does not work? Why doing stuff that does not work is beyond me.
It is not liking or taste here. Can you imagine buying a car that does not start, wipers that do not work when it rains, brakes that sometimes accelerate the car randomly or a steering wheel that only turn left? This is what MS is doing. Nothing to do with me, these things have been reported. I could past 30 links of major problems with WinUI3.
WinUI3 multiple windows is not working or way too unstable to implement. WinUI3 camera does not work. WinUi3 voice and speech do not work. WinUI3 cannot print without dialog out of your control, so it is impossible to make a ticket distributer or invoice printing app.
Forums are packed with missing and broken feature. You never see that elsewhere.
But the problem is that Microsoft told us what was their priority and it was not related to technology. https://youtu.be/q32b3_O_3oc
It seems that the problem would not occur until I set the following values:
WebView.CoreWebView2.Settings.AreBrowserAcceleratorKeysEnabled = false;
WebView.CoreWebView2.Settings.AreDefaultContextMenusEnabled = false;
WebView.CoreWebView2.Settings.AreDevToolsEnabled = false;
WebView.CoreWebView2.Settings.IsGeneralAutofillEnabled = false;
WebView.CoreWebView2.Settings.IsPasswordAutosaveEnabled = false;
WebView.CoreWebView2.Settings.IsPinchZoomEnabled = false;
WebView.CoreWebView2.Settings.IsStatusBarEnabled = false;
WebView.CoreWebView2.Settings.IsSwipeNavigationEnabled = false;
WebView.CoreWebView2.Settings.IsZoomControlEnabled = false;
I have not set anything and the problem is there.
Just an empty project with 1 webview navigating to google.com
Same issue on .NET MAUI Blazor App (.net 7), if the keyboard buttons are pressed fast enough it totally freezes the UI.
How to reproduce: keep right click pressed, press keys(WASD) fast randomly.
Hi all, this bug is set as top priority issue right now for owner team and as of today the owner team has narrowed down the root cause and they are working on a fix for this and setting a goal to get it fix as soon as possible.
Thanks!
Any updates on the status of the fix?
I left only one text field in my poc hoping it wont be rejected
If you have only one text field this can still happen
is @tofuandeve still the guy assigned to this, is this guy the only person who's working on this
is @tofuandeve still the guy assigned to this, is this guy the only person who's working on this
Its been assigned to another team and is being tracked here: https://github.com/microsoft/WindowsAppSDK/issues/3266 But don't expect to get any updates. I've been trying for weeks.
It's fixed allegedly
It's fixed allegedly
Source? @Xyncgas
When will this fix be released?
@tofuandeve Any news about an update possibility?
no
Just to make everyone aware but a fixed is being tested it seems https://github.com/microsoft/WindowsAppSDK/issues/3266#issuecomment-1458501446 🤞
Good News
I had same issue in Blazor Hybrid MAUI (video demonstration) and when I removed OnAfterRenderAsync on my MainLayout, it started working smoothly again. Logic had StateHasChanged();, which I think was the issue.
I had same issue in Blazor Hybrid MAUI (video demonstration) and when I removed OnAfterRenderAsync, it started working smoothly again. Logic had StateHasChanged();, which I think was the issue.
That's my example video and the issue has nothing to do with Blazor thus "removing OnAfterRenderAsync" wouldn't do anything to prevent the problem. The cause has been fixed with a new version of WinAppSDK which will come to MAUI Blazor when the MAUI team upgrade the template version, or you can force it by manually specifying the NuGet package reference in the CSProj file.
I had same issue in Blazor Hybrid MAUI (video demonstration) and when I removed OnAfterRenderAsync, it started working smoothly again. Logic had StateHasChanged();, which I think was the issue.
That's my example video and the issue has nothing to do with Blazor thus "removing OnAfterRenderAsync" wouldn't do anything to prevent the problem. The cause has been fixed with a new version of WinAppSDK which will come to MAUI Blazor when the MAUI team upgrade the template version, or you can force it by manually specifying the NuGet package reference in the CSProj file.
I saw the video, it applied to me as well, which is why I referenced your video. The issue was in the Blazor which I used. And removing the OnAfterRenderAsync on my mainlayout did fix my issue I had for a while. That's only good if they've fixed it in the next release.
The latest update is working fine for now.
Tell me, nobody noticed that the file drag & drop does not work in WebView2? It has never work, even when reported 2 years ago by many people. Another day, another basic feature not working.
1 problem fixed, now go fixe the remaining 100 000 broken and missing features in WebView2.
I noticed the same problem with WinUI3.
The latest update is working fine for now.
Tell me, nobody noticed that the file drag & drop does not work in WebView2? It has never work, even when reported 2 years ago by many people. Another day, another basic feature not working.
1 problem fixed, now go fixe the remaining 100 000 broken and missing features in WebView2.
@applefanbois which update is working for you? I thought I had a newest WinUI and it is still not working.
@applefanbois I take it back. I did update everything to the latest and I could not reproduce the issue any more. So seems like it's been resolved.
How is it possible that the file drag and drop is not working in a modern web engine? Do I really need to report it? Am I the only one using it? Maybe MS should have used the Safari WKWebView engine instead? WebView2 is using the Chrome engine. Is the chrome engine so limited and unreliable out of the box? 2 years and it lacks all the basic features expected from a webview and most stuff that is there is not working correctly.
I remember the good old days of MFC and Win32, programmed in C. Those things were working great. Never had a problem with them. Sad that the new generation of MS programmers are not able to come close to their predecessors.
How is it possible that the file drag and drop is not working in a modern web engine? Do I really need to report it? Am I the only one using it? Maybe MS should have used the Safari WKWebView engine instead? WebView2 is using the Chrome engine. Is the chrome engine so limited and unreliable out of the box? 2 years and it lacks all the basic features expected from a webview and most stuff that is there is not working correctly.
After MS killed Silverlight - a great product from my point of view, I am very cautious about MS UI packages. Though I still consider C# the best existing language for development (especially now after it became multiplatform and open source).
There is ASM, C and all the other cheap programming languages that are basically C for dummies. C# is ok, but nothing more than a c++ that generate bytecode instead of Assembly.
Can you close this issue as resolved now @applefanbois or @tofuandeve ? Thanks!
The problem is still there.
The problem is still there.
If you create a new MAUI.Blazor project does this problem still exist
If you create a new MAUI.Blazor project does this problem still exist
To get the fix in a .NET MAUI app, please upgrade the Microsoft.WindowsAppSDK dependency like this:
<ItemGroup>
<PackageReference Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'windows'" Include="Microsoft.WindowsAppSDK" Version="1.2.230313.1" />
</ItemGroup>
Note that you will need to do this manually by editing the project file instead of using the NuGet Package Manager UI.
To get the fix in a .NET MAUI app, please upgrade the Microsoft.WindowsAppSDK dependency like this:
<ItemGroup> <PackageReference Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'windows'" Include="Microsoft.WindowsAppSDK" Version="1.2.230313.1" /> </ItemGroup>
Where does that go? My MAUI Hybrid Blazor app project file does not seem to have an an entry containing "WindowsAppSDK"
To get the fix in a .NET MAUI app, please upgrade the Microsoft.WindowsAppSDK dependency like this:
<ItemGroup> <PackageReference Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'windows'" Include="Microsoft.WindowsAppSDK" Version="1.2.230313.1" /> </ItemGroup>
Where does that go? My MAUI Hybrid Blazor app project file does not seem to have an an entry containing "WindowsAppSDK"
That's because the reference is being imported as part of the MAUI framework. By specifying a package reference in your project file, the MAUI implicit reference will be overridden.
This is the reason why I raised a ticket, so that MAUI can upgrade the implicit reference rather than developers having to manually import a specific version.
That's because the reference is being imported as part of the MAUI framework. By specifying a package reference in your project file, the MAUI implicit reference will be overridden.
Thanks for clarifying. Where do I find what WindowsAppSDK version MAUI currently uses?
[EDIT] Sorry, found it in packages ( is 1.2.221209.1 )
is this included inside 1.3.230502000
@Eilon
can you please find out that issuse
Referenece Ticket
https://github.com/dotnet/maui/issues/25791
https://github.com/user-attachments/assets/57319bea-f36a-451e-91bb-a5ec9d5c3ace
There are 2 ways to replicate the problem. It is new to the latest version stable version of WebView2.
-Click in an web page input box and type super fast. or -Select text in a page and Ctrl + c multiple times super fast.
The webview2 and the app will look like it is crashed and froze. It is not frozen, keyboard is still working. You can continue to type in the input box. You can tab to change inputs. You can even zoom with the keyboard. CPU usage is zero. The mouse does not work at all in the whole app, giving the illusion it is frozen. So you can click in the webpage or the app part and it will do nothing. I have not found a way to unstuck it.
The problem happens 5 times per hours for a normal user. Typing fast is jus a way to make do the problem faster. WebView2 is now unusable.
-Latest update of Windows 10 Pro version 22H2 build 19045.2311 -Also happening on Windows server 2022 -Microsoft.Windows.SDK.BuildTools 10.0.22621.755 -Microsoft.WindowsAppSDK 1.2.221116.1 -Microsoft Edge WebView2 Runtime 107.0.1418.42
--------------------- 2 cents PS : If you are a developer and you are planning on using webview2 or any Microsoft SDK... don't We already lost 200 000$ trying to make the MS SDK work and it never does. Go with QT or anything else. I wish I could go back in time and tell my younger self to stay away from any MS SDK. If you do go with MS SDK, you will forever loose your sanity. We have the exact same app with almost exact same code on iOS and macOS and never had any problems.
Pleas MS or anyone working on this : just make it work like QT, iOS, macOS, Android SDK. I do not deserve this mental torture. My boss is so depressed that the app 4 years later is still not functional on Windows. We are forced to ask our customers to buy Apple product to use our app.
AB#43086528