Globe image appearing when selecting an anchor tag in MAUI blazor & crash in VS2022 #26615
Labels
area-blazor
Blazor Hybrid / Desktop, BlazorWebView
platform/windows 🪟
s/triaged
Issue has been reviewed
s/verified
Verified / Reproducible Issue ready for Engineering Triage
t/bug
Something isn't working
Description
When attempting to highlight text in an anchor tag and then clicking anywhere, a globe appears with a disabled icon over it. My best guess is that this is the edge quickmenu, but im not sure why it appears or how to disable it. If you do nothing once the globe appears, after a short (but kinda random) amount of time, an exception will be thrown when running in visual studio which causes the application to crash. When deployed, the icon simply disappears.
For me this issue is more around how to stop the globe from appearing in the first place. The crash seems secondary seeing as that doesnt appear to happen in a deployed application, only when VS is connected, and might be a non issue if there is a way to prevent the globe appearing in the first place.
I first noticed this issue when using the MudBlazor library, and it persisted when I migrated to fluent-ui. After some playing around, I realised this can also be reproduced in the base maui blazor template, so I dont think its an issue with any specific UI library
Normal strange behaviour:
https://github.com/user-attachments/assets/b6c968a6-6432-42e7-b0c6-93571cd63f3f
Crash in Visual Studio:
https://github.com/user-attachments/assets/b58d5af6-4861-4a6c-a139-6db6975ab653
Build logs, but I dont think they show much at all:
BuildLogs.zip
Steps to Reproduce
Click Me
button on the counter pageLink to public reproduction project repository
N/A this can be reporduced with the out of the box template
Version with bug
8.0.82 SR8.2
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
No response
Affected platforms
Windows
Affected platform versions
No response
Did you find any workaround?
None so far
Relevant log output
The text was updated successfully, but these errors were encountered: