Dolby stereo audio playback failure on Windows 10 since Edge 141
Hi there, I'd like to report a regression I recently discovered: Dolby Stereo is failing to play in Edge, but Dolby 5.1 channel doesn't experience this issue. The issue can be reproduced using AC3 audio generated by FF.mpeg. Run the following FF.mpeg command to encode a short AC3 stereo audio clip containing noise into an MP4 file. Drag and drop the file into Edge; you'll observe playback failure, and you can also find the failure log in edge://media-internals/. ff mpeg -f lavfi -i anoisesrc -c:a ac3 -ac 2 -y 2ch.mp4 Changing the encoding channel in the FF.mpeg command -ac to 6 (5.1) will allow the audio to be played in Edge. ff mpeg -f lavfi -i anoisesrc -c:a ac3 -ac 6 -y 6ch.mp4 The same is true for EAC3 audio. Just need to change the -c:a parameter to eac3. For more contexts, I'm not on a fresh installation of Windows 11. I'm still on Windows 10, so https://learn.microsoft.com/en-us/windows/win32/medfound/dolby-audio-decoder is still available. I'm currently on 142.0.3595.53 (stable). I've also tested 144.0.3658.0 (canary), but the issue persists. Please let me know if you need more information. Thanks in advance.
Edge Read Aloud feature fails on landscape PDF documents with tables.
I've encountered an issue with the Read Aloud feature in Microsoft Edge when opening PDF documents in landscape orientation that contain tables. The Read Aloud option is available and can be activated, but it gets stuck loading indefinitely and never starts reading. No error message is shown. In contrast, the same feature works perfectly with portrait-oriented PDFs, even when those PDFs include tables. I tested this on both Windows and macOS with up-to-date Edge versions. The issue appears to be consistent and not OS-specific. My clients use tables in landscape PDFs for better readability and formatting. It’s unclear whether the problem is due to the landscape orientation alone or the combination of landscape + tables. However, tables in portrait PDFs do not cause any issues. Has anyone else experienced this behavior? Is there a known fix or workaround? Would appreciate any feedback or confirmation from the Edge team.--js-flags=--noexpose_wasm launch flag causes STATUS_BREAKPOINT
Version 135.0.3179.73 (Official build) (64-bit), Windows 11 Education, also occurs on Windows 10 Education and Windows 10 Pro, been testing this since probably version 129 of Edge. --js-flags=--noexpose_wasm as a launch flag causes STATUS_BREAKPOINT, this is regardless of default configuration and with or without extensions. WASM can be used to discover privileged information about a machine, and this seems to be working in the past according to some users online, but no longer does now. Please can someone advise?
