microsoft edge bug
2 TopicsEdge 130.0.2849.46 (Official build) (64-bit) Broke Extension(s) - Ublock Origin in this case.
Hello, I know very well that Edge is also moving to MV3. But, there isn't any announcement about complete removal of MV2 yet. Since Edge updated to v130, it broke popular extension like Ublock Origin, for many people. We've reported the issue to extension devs, it but seems that while there are many people who are affected, there still be many that have extension working fine as expected. https://github.com/uBlockOrigin/uBlock-issues/issues/3419 Many people've reported this issue not only on github, but also on reddit as well. The extension was working fine before v130, so we suspect that the cause is Edge update itself. - Issue: The extension loads but cannot run, and its dashboard page cannot load, is completely empty. Turn on/off does not work. Removing/Reinstalling from MSEdge Store also does not work. The only "workaround" for this is setting up a completely new blank local profile, but that will cost all the synced settings and extensions data. Please help us looking into this issue, Thank you. --------------------------------- Browser: Edge 130.0.2849.46 (Official build) (64-bit) Extension: Ublock Origin v1.60.0 Extension source: MSEdge Store System: Windows 10 22H2 19045.5011 (I don't think system info matters because there're people who're on Win11 and have this issue as well)3.2KViews5likes5CommentsInconsistency of window's new Date() function returns invalid date in Microsoft Edge
We are facing some browser problem while using React as frontend for initialize new Date() object such that new Date().toLocaleString() gives empty string. As this is not the case with Chrome so raising it here. Looking forward to get a permanent solution as of now we have added retries for initialize new Date() object for work around.224Views1like0Comments