MicrosoftEdge
Touchscreen not working after rapidly clicking while app startup
Issue moved from dotnet/maui#16251
- Please respond to @Letiz0.
From @Letiz0 on Thursday, July 20, 2023 10:33:49 AM
Description
https://github.com/dotnet/maui/assets/103472129/377c891b-18c5-47ca-ad27-354289b74a45
Just like the video shows, if I rapidly click anywhere inside the app while starting up and loading, the touchsrceen will be broken but the mouse is still working.
Steps to Reproduce
- Create a new Maui Blazor Project
- Deploy it on any tablet
- Repeatly touch the screen inside the app window as quickly as you can
Link to public reproduction project repository
https://github.com/Letiz0/MauiApp1
Version with bug
7.0.49
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
net7.0-windows10.0.19041.0
Did you find any workaround?
2023/08/01 update: I found that if I force reload the page (e.g. NavigationManager.NavigateTo(NavigationManager.Uri, forceLoad: true)), it would be solved.
Relevant log output
No response
Issue moved from dotnet/maui#16251
- Please respond to @trivalik.
From @trivalik on Thursday, July 20, 2023 11:34:39 AM
If the MAUI app could not be used, is the operating system still useable via touch?
Issue moved from dotnet/maui#16251
- Please respond to @Letiz0.
From @Letiz0 on Thursday, July 20, 2023 12:12:21 PM
If the MAUI app could not be used, is the operating system still useable via touch?
I can even close the MAUI app by touching the top-right "X" icon, it seems touchscreen is only broken inside the app.
Issue moved from dotnet/maui#16251
- Please respond to @msftbot[bot].
From @msftbot[bot] on Thursday, July 20, 2023 4:39:46 PM
We've added this issue to our backlog, and we will work to address it as time and resources allow. If you have any additional information or questions about this issue, please leave a comment. For additional info about issue management, please read our Triage Process.
Issue moved from dotnet/maui#16251
- Please respond to @Eilon.
From @Eilon on Tuesday, August 1, 2023 10:46:39 PM
Hi @Letiz0 , I wonder if this is the same as https://github.com/MicrosoftEdge/WebView2Feedback/issues/3003 (even though in your case it's touch actions instead of keyboard/mouse).
A fix for that bug is listed here: https://github.com/MicrosoftEdge/WebView2Feedback/issues/3003#issuecomment-1499349079
So it's probably worth trying that to see if it resolves your issue.
Issue moved from dotnet/maui#16251
- Please respond to @Letiz0.
From @Letiz0 on Wednesday, August 2, 2023 1:07:43 AM
Hi @Letiz0 , I wonder if this is the same as MicrosoftEdge/WebView2Feedback#3003 (even though in your case it's touch actions instead of keyboard/mouse).
A fix for that bug is listed here: MicrosoftEdge/WebView2Feedback#3003 (comment)
So it's probably worth trying that to see if it resolves your issue.
I've tried the solution you mentioned last month, unfortunately it seemed not solving the problem. Just like what you said it's about the touch screen instead of the mouse.
Issue moved from dotnet/maui#16251
- Please respond to @Eilon.
From @Eilon on Wednesday, August 2, 2023 5:42:10 PM
I've tried the solution you mentioned last month, unfortunately it seemed not solving the problem. Just like what you said it's about the touch screen instead of the mouse.
Alright thanks for trying it out. I guess we'll need to investigate further. I'd say there's a strong chance we'll end up redirecting this to the WindowsAppSDK (WinUI) or WebView2 team because it's unlikely there's any Blazor- or MAUI-specific issue here.
Issue moved from dotnet/maui#16251
- Please respond to @Eilon.
From @Eilon on Wednesday, August 2, 2023 7:48:41 PM
I've tried reproducing this on my Surface Book 3 with a touch screen and so far I am unsuccessful. I tried tapping the white part of the screen as much as possible while it loads but the app remains fully responsive to all input types. I'll keep trying.
Issue moved from dotnet/maui#16251
- Please respond to @Eilon.
From @Eilon on Wednesday, August 2, 2023 7:52:06 PM
Alright now I can repro it! I lowered the max CPU power settings to 25% and that seemed to slow everything down enough. I then launched the app, randomly tapped on it while it loaded, and then touch doesn't work at all in the app. Interestingly, both mouse and keyboard work fine.
Issue moved from dotnet/maui#16251
- Please respond to @Letiz0.
From @Letiz0 on Thursday, August 3, 2023 1:36:16 AM
Alright now I can repro it! I lowered the max CPU power settings to 25% and that seemed to slow everything down enough. I then launched the app, randomly tapped on it while it loaded, and then touch doesn't work at all in the app. Interestingly, both mouse and keyboard work fine.
Thanks for your efforts, and yes, the worse hardware is, the more often problem happens. It also happens when navigation and loading data from EF Core, and that's what actually annoying me. The video just shows the easiest way to reproduce it.
I found that if I force reload the page when the problem happened (e.g. NavigationManager.NavigateTo(NavigationManager.Uri, forceLoad: true)), the touch-screen would be resumed and everything worked fine, so I guess it's all about WebView2.
Issue moved from dotnet/maui#16251
- Please respond to @Eilon.
From @Eilon on Thursday, August 3, 2023 5:26:49 PM
I was able to repro something very similar in a pure WindowsAppSDK (WinUI) + WebView2 app:
- Create new WinUI default app in VS
- Replace the app's content with:
<WebView2 Source="https://microsoft.com/" /> - Set your tablet PC's CPU to some extremely low speed, like this:
- While launching the app w/ debugger from VS, tap the blank white app loading screen a lot
- Eventually the app "loads", but it remains entirely a blank screen
- Interestingly, the app did load the page because you can see it in the F12 dev tools!
So, I'm not quite sure if it's exactly the same bug, but it's super similar.
Hi @maurawinstanley this issue can be reproduced on blazer webview but not reproducible on .NET. May someone working on WinUI take a look?
I have same problem on my low end devices with touch screen. Is there any other workaround instead of force reload page?
@novac42 the repro I shared at https://github.com/MicrosoftEdge/WebView2Feedback/issues/3685#issuecomment-1664418104 uses only .NET + WinUI. It doesn't use Blazor at all.
I still encounter this, did anyone found a solution or is this still a bug or still being worked on?
I wonder if things are better now with the latest WASDK and WebView2 nugets...
What's the story on this then? Is anyone working on this? My issue got closed because it's a duplicate of this, but this seems to be dead, no? My issue was with Maui, but I got around the problems by using a webview2 component within a winforms app and I don't get the same issues. But then again my issue wasn't about startup.
Any update on this? My users just encountered the same issue when rapidly touching UI elements in our MAUI Blazor app. Gladly, minimizing the window and then restoring it works as a workaround to make the UI responding again.
I just updated everything to the most recent versions available (MAUI Controls, Webview2 etc.) and the issue is still there.
and
I dont think anyone is working on resolving this, this has been open for more than a year now.
I had to move away from Maui Blazor due to this
I Cannot belive there is still not a solution for this issue, it is so easily to overload the UI, we have self service kiosk in blazor maui, cannot release it because of this issue, freezing is so often, mostly happens if you use more than 1 finger, it is still resolved after minimizing and restoring the window, but who will be able to do that in self service kiosk. Is there any update on this or we have to move away from complete product basically? Project is .net8, migrated it to .net 9 same issue still. Will never choose to work with these products again!
I Cannot belive there is still not a solution for this issue, it is so easily to overload the UI, we have self service kiosk in blazor maui, cannot release it because of this issue, freezing is so often, mostly happens if you use more than 1 finger, it is still resolved after minimizing and restoring the window, but who will be able to do that in self service kiosk. Is there any update on this or we have to move away from complete product basically? Project is .net8, migrated it to .net 9 same issue still. Will never choose to work with these products again!
What i did was just switch to blazor web and put it on IIS. Then made a webview to display that page on our kiosk
@trajkovdimitar Weird. For me the issue with overloading the UI was already fixed a few versions back (webview2). Now with the release of v138 my final issue when using touchpad and scrolling is solved as well: https://github.com/MicrosoftEdge/WebView2Feedback/issues/5114
Perhaps you can try to update your webview2 as mentioned here: https://github.com/MicrosoftEdge/WebView2Feedback/issues/5114#issuecomment-3022082488
@char8t Not fixed definetely, we did everything, always updating and shipping the webview, but after clicking it few times with few fingers on the display, the issue is still easily reproduced. @gerardlardizabal It is really complicated, since there is only one single app now, that handles communication with peripheral devices, like bill acceptors, scanners, card readers, and many kiosks to be managed each individually trough iis, we wanted to avoid that, that is why we have chosen windows app, otherwise we would have selected different approach.
After updating to the latest version of the webview. Harder to reproduce now with regular taps, but if you put 5 fingers on the screen and do a swipe, it freezes the UI. Platform: Windows. I really hope that fix will come soon.
We are experiencing the same issue where the app freezes when the touchpad and touchscreen are used simultaneously, affecting over 500 customers.
