This repository tracks the roadmap for the Microsoft Edge web platform. This data is used on https://status.microsoftedge.com/ to provide implementation status and forward-looking plans for web standards in Edge and other browsers.
I am facing a weird issue from Microsoft Edge 119 (119.0.2151.97) on a windows VM, that some part of the website getting blank on moving the mouse over the browser toolbar buttons.
Website having a lot of text, date, dropdown fields. As per my observation this happens when a scroll bar is available in the website. Attaching the screenshot for reference
Normal Website view
Issue Screenshot
When I mouse over through the browser tabs, I can see this issue but this recovers automatically when I move the mouse over to the blank area.
I tried switching of the Hardware accelation, Sleep for inactive tab options. But still was able to reproduce the issue. This issue was only reproducible in a VM machine connected using an RDP connection. I was able to reproduce the same issue in browserstack environment too.
I am facing a weird issue from Microsoft Edge 119 (119.0.2151.97) on a windows VM, that some part of the website getting blank on moving the mouse over the browser toolbar buttons.
Website having a lot of text, date, dropdown fields. As per my observation this happens when a scroll bar is available in the website. Attaching the screenshot for reference
Normal Website view
Issue Screenshot
When I mouse over through the browser tabs, I can see this issue but this recovers automatically when I move the mouse over to the blank area.
I tried switching of the Hardware accelation, Sleep for inactive tab options. But still was able to reproduce the issue. This issue was only reproducible in a VM machine connected using an RDP connection. I was able to reproduce the same issue in browserstack environment too.
I could see the issue was not in version 118. So I tried installing the Dev channel build https://www.microsoft.com/en-us/edge/download/insider?form=MA13FJ of Microsoft Edge, which is 121 (121.0.2248.1) and the issue is not reproducible.
Is there any workaround to get this fixed in 119 as most of our customers are using 119 version of edge. Or do I need to wait for 121 to be released ?