Zoom with Scroll + Modifier Key Not Working in Edge on macOS
Hello, I am using Microsoft Edge on macOS and I would like to zoom in and out of web pages using a modifier key (Command, Option, or Control) together with scroll Currently, Command + Scroll does not zoom the page. I understand that macOS may override this behavior through accessibility settings, but I would like to enable this functionality specifically in Edge without affecting system-wide behavior. Could you please advise: Is it possible to enable zoom using Scroll + Modifier Key in Edge on macOS? If not, are there any recommended workarounds or planned features for this? Thank you for your help DanceLens!
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.optional suggestion: new menu bar app for mac
i wish i could launch one of my edge profile (no matter from which edge) directly in the menu bar. so you create a profile launcher.app and then i can search a profile installed on my 4 browser, without need to launch a browser. at the moment we can do similar things once the browser is launched using the dock icon or using the sync icon or using the menu bar option inside edge. but there is still the limit that we can do it for one browser. we cannot search profiles installed on all 4 browser. plus every time you launch the browser, you open the last used profile. so we first need to close and then switch (which requires time). profile switching is slower in edge compared to google. now with this new app you would simply launch a profile inside an edge app, without launching the previous profile.
Microsoft Edge Profile Deleted
Hi, I wonder if someone could help me with a Microsoft Edge issue. Unfortunately, the profile that I set up for Microsoft Edge on my Mac was deleted and has now removed all of my saved history, bookmarks, passwords, etc. This profile was not synced to a Microsoft account and I need to restore the data somehow. Please could someone help me with this issue so that I can retrieve the deleted profile. Many Thanks.
Microsoft Edge Canary can't open Bing, settings and home page on macOS
With the Canary version (117.0.2023.0 (Hivatalos build) Canary (arm64)) after it loads a Bing search, it doesn't show the homepage, and I get an error when I try to access settings. It does it only in one of my profiles. If I switch profiles it works as normal. (I'm using the browser with Hungarian.)
macOS Screen Time support
To show up as individual sites instead of the whole app in macOS. ## example result from Chrome This feature seems to be supported in Chrome already as: chrome://flags/#screentime Also implemented in chromium for a while: https://chromium-review.googlesource.com/c/chromium/src/+/2585655SS48: don't remove MacOS Mojave support on Edge, even if Google now announced to us that they will
Suggestion (SS): 48 Classification: Browser Compatibility PRIORITY IN MY OPINION: 10 on a scale from 1 (low) to 10 (high) Few hours ago Senior Dev reported us the no interest of keeping MacOS Mojave support on Chrome. In 2 years they are removing the 2 best MacOS ever released, before Apple started to downgrade features in MacOS (and obviously adding some other too), especially related to all backup workflows, that now are more complex, but even to permissions and multiple other things. We reported the new downgrade for external drives implemented in MacOS 12/13 https://old.reddit.com/r/appledatahoarding/comments/11ikj38/next_macos_downgrade_available_with_monterey/, but this is not the point now. We explained already https://bugs.chromium.org/p/chromium/issues/detail?id=1413784&q=sierra%20chrome&can=1 why they should keep support for such MacOS, and later again https://bugs.chromium.org/p/chromium/issues/detail?id=1322548#c68 Now the point is: we are trying our best to revert such decision, like we wrote https://old.reddit.com/r/appledatahoarding/comments/11jufgo/google_chrome_support_will_end_in_few_months_for/, but it's important that other chromium based devs know about such problematic and evaluate to continue support, if this is technically possible. Remember that MacOS 10.14 is not like all other MacOS released by Apple, so removing such MacOS is not like removing Catalina, High Sierra etc. If there are question why MacOS Mojave support is so important, just write directly to us. We already experienced the direct consequence of removing MacOS on Chromium on all browsers and apps few months ago with Sierra. Please keep in mind that this is not just related to Chrome, but even Chromium based browsers, Mac Apps using Electron, and all other Mac Apps too (because if one is starting to remove support, especially big brands, the other will follow much easier*). So be open with your mind and don't write "i'm not using Chrome or Mojave, doesn't matter for me". There is the possibility that Google maybe know about some changes with Xcode, like we wrote https://old.reddit.com/r/appledatahoarding/comments/11jho7y/meanwhile_the_batch_deletion_of_other_2_macos_by/ but probably is not the case. If this is true, then the situation would be much worse, if now Apple really decides to remove multiple MacOS, like we previously reported with out https://old.reddit.com/r/appledatahoarding/comments/114o7zt/remember_2023_will_be_the_most_crucial_year_of/ *Keep in mind that almost 70%+ of all browsers available for MacOS (80+) are Chromium based. ------------ In case you will not doing that and Google will not keep support for Mojave, please provide directly link to download a browser version compatible with up to MacOS Sierra and one up to MacOS Mojave, instead of just download last version. Avoid auto update of the app too. So don't install new incompatible app automatically, which make no sense at all.
Finder launched by "Save As" in MacOS resizes Edge window
When doing "Save as" where a Finder window is opened to choose the save location, the Edge window gets resized so that there's space at the right-hand side of the window. I've only observed this behavior on MacOS (never happened on Windows 10 or Windows 11). In previous versions, the window used to resize back, but as of 107.0.1418.28, it stays stuck in the new smaller size.Edge browser 100% CPU, requires Force Quit (macOS Mojave and v91.0.864.48)
I'm reporting a problem I've experienced with Edge since I began using it six months ago. After using Edge for a few hours, it will begin using 100% CPU. According to the Task Manager, it is the "Browser" thread that is using this CPU. If I Quit the application, all the windows close but it doesn't fully quit; I have to do command-option-esc to open the Force Quit window (where it says "Microsoft Edge (not responding)" and then I'm able to Force Quit it. When I relaunch it and re-open the web pages I was using, it works fine (until later that day or the next day, when the process repeats). Does anyone know how I can troubleshoot this so I can file a useful bug report? This has happened many times over the past 6 months, over many different Edge versions (I'm always using the latest stable version). I'm not able to reproduce the issue when I want, but it happens regularly every or every-other day. I'm using macOS Mojave 10.14.6 on a 2015 MacBook Pro. Edit: It just happened again, so I took some screenshots and attached them below.
