Edge rendering inside a container that cuts off pixels
Hello. In Microsoft Edge version 145.0.3800.58 (Official Build) (64-bit), web pages are displayed by default within a container with rounded corners and padding on all sides. This results in pixels being lost in height and width. It also means that CSS definitions with a min-width for common resolutions such as Full HD (1920px in width) or WQHD (2560px in width) do not apply. Many front-end frameworks rely on these pixel thresholds to dynamically adjust container sizes. I'm sorry to be so blunt, but as so often in the long, sad history of Microsoft web browsers, common web standards are once again being ignored. This time it's for a feature that no one really needs, but which once again causes extra work for many web developers. Ever since I started working in web development, back when the dreadful Microsoft Internet Explorer was still widely used, it has always been extremely labour-intensive to adjust websites for Microsoft browsers. This has caused a great deal of frustration over the decades, and there seems to be no end in sight. Integrating the Chromium engine into Edge was a promising first step. But perhaps Microsoft could also start respecting web standards outside of the engine? I'm sure that hundreds of millions of web developers would be grateful. I suppose hope dies last 😉
Edge Security breaks SQLite WASM loading
Edge with "Enhance your security on the web" toggled on, either Balanced or Strict breaks loading of the Sqlite WASM package. Believe this may have started with 144, but also appears to be in Dev/Canary 145. It looks as if it is somehow corrupting the WASM binary, although I am not an expert on this. You can confirm this by toggling the setting on and visiting projects using this library, eg. https://sqlime.org/Edge browser crashes after file download / open
Hello, I am using Edge browser Version 142.0.3595.80 (Official build) (64-bit), on Linux. When downloading a file , and trying to open the downloaded file from wihin browser, it causes edge browser instances to close. I have been using other browsers to get around the problem. Is this a known problem, and are there a solution to this problem? Thanks, Jay
Persistent issues with Read Aloud in Edge
I have Windows 11. Today I began having an issue wherein the Read Aloud feature built into Edge doesn't work. I was initially trying to use a similar function on Internet Archive, and noticed that while all the Microsoft voices seemed to be available in the onsite dropdown, the only voices that made any sound were David, Mark, and Zira---none of the "Online (Natural)" voices. I tried to use Read Aloud as a workaround, and found all the buttons greyed out completely. Mind you, everything worked fine yesterday, and I made no changes to my computer in the intervening time. I've opened up two support tickets, but neither live chat agent was able to resolve the issue. Here are the things I've tried with their help: trying the feature on different websites updating & restarting Edge resetting Edge settings to defaults updating & restarting computer switching wifi networks connecting to a hotspot using InPrivate mode using a new Edge profile (rule out interference from extensions) checking that English tts is downloaded in Time & language > Language & region turning Online speech recognition off and back on again resetting experimental features checking sound systems (they work, but just in case) doing a system reset (?) to 24 hours ago, which took about an hour and undid all the updates I just mentioned maybe something else I don't remember? The next thing I am going to try is give my computer a long nap. It's been a while, so maybe it just needs some shut eye. Otherwise, help????
[Wayland] PWAs no longer appear as separate app windows — all group under main Edge icon
Hi, Since around 2025-09-07 to 2025-09-10, I’ve noticed that on GNOME (Wayland) all installed PWAs (even across different profiles) now appear grouped under the main Edge browser icon in the GNOME Shell dash/taskbar. Previously, each PWA would open in its own window group with its own icon. This is still the behavior in Chromium/Brave/Chrome, and can be restored there by editing the PWA’s .desktop file to set: StartupWMClass=<same value as Icon> However, Edge now seems to ignore StartupWMClass completely on Wayland, breaking workspace separation and making task switching hard. Environment: Ubuntu 25.04 GNOME 48.0 / Mutter (Wayland) Kernel 6.14.0-29 Intel Iris Xe GPU Edge (latest stable, observed post 2025-09-13) Repro steps: Install any PWA (e.g. Outlook, Teams, Spotify) from Edge Launch it (from any profile) Observe that it appears grouped under the main Edge browser icon Expected: PWA shows under its own icon and window group like in Chromium-based browsers Actual: All PWAs are bundled into the main Edge window group Editing StartupWMClass in the .desktop file no longer helps This regression makes PWAs much harder to manage on Wayland. Please route to the Linux/Wayland team if possible. Thanks!
Installation Issue in Microsoft Edge
In my Machine i currently have Microsoft Edge for MAC 143.0.3650.80, and I am trying to update the app Microsoft Edge for MAC 143.0.3650.96 through the PKG installer from the website. https://www.microsoft.com/en-us/edge/business/download?form=MA13FJ https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/39c16afe-6ffe-42f8-aa82-4dd057fcf1d5/MicrosoftEdge-143.0.3650.96.pkg The installation appears to be successful, but the app has not been updated. Upon checking the logs, it seems the installation was not completed and skipping PackageKit: Skipping component "com.microsoft.edgemac" (143.0.3650-143.0.3650-*) because the version 143.0.3650-143.3650.25121080-* is already installed at /Applications/Microsoft Edge.app. Is there any issue in above PKG installer? Can anyone help with this issue?
Edge pdf text addition = massive file size increase
As of today, when I add just a small amount of text (20-30 characters) to a pdf and save, the file size increases from 66KB to 55,000KB ... never happened before. I've reported to Microsoft but they have no solutions. Any ideas to get around? Saving as a separate file has same result. Thanks
