[Feature Request] Please allow hiding the Extensions button in Edge toolbar
I am using Microsoft Edge version 140.0.3485.66 on macOS. In this version, the Extensions menu button (the puzzle icon) is forced to stay visible on the toolbar, and the toggle in Appearance / Customize toolbar settings to hide this button has disappeared. I use some extensions, but I don't want the extension (puzzle) icon to show on the browser interface. You just need to roll back this feature to the state it was in the previous version. Keeping the Edge interface clean is a very good reason why I prefer Edge. I like using Edge instead of Google Chrome, and this is an important reason! I don't want you to make it more and more like Chrome!Feature Badge Request
Hello, How can I request a feature badge for my extension on the Edge Add-ons Store? My extension, https://microsoftedge.microsoft.com/addons/detail/free-vpn-proxy-1vpn/dalhgafbhpdolibignjckpmiejgfddjp, follows Microsoft’s best practices for privacy, security, and user experience. It has more users and a higher rating than many VPN proxy extensions that currently have a feature badge. Without the badge, it doesn’t even show up when https://microsoftedge.microsoft.com/addons/search/1vpn, which seems like a poor experience for users. Thank YouRestoring extensions and the invenient experience.
Hello Everyone! How are you? You've all gone through or will go through the experience of launching a Chromium-based browser at some point (especially Edge in this case) And see that when you reinstall your extensions through the automatic process (importing from your browser or your account) You're faced with THOUSANDS of extensions in your browser, with settings for extensions or welcome or anything like that! This isn't really a problem, but it can be really inconvenient sometimes when you're typing a text or looking for something and suddenly you're moved to a new tab or something. The question is: Why not just put a floating bubble under the extensions icon warning you that "Hey you have new extensions, click here and configure it!" This could be a great idea and would aid in a smoother and smoother experience that is less invasive and clearer! But let me know, what do you think of it?[FIXED] Legacy Edge extensions on Windows store after installing the new Edge
Today I came across this extension when browsing Windows store https://www.microsoft.com/store/productId/9P59WXTBHZZM I could install it without any issue but the thing is it doesn't work when I have the Stable version of Chromium based Edge installed. clicking "launch" opens the new Edge only, nothing else happens. I think the proper way to handle this situation is to either hide these extensions from Windows store once the new Edge is installed, OR show a message to user that: "it's not compatible with the current installed version of Edge browser". My suggestion is to add the new Chromium based Add-ons to the Windows store to be easily available and installed by users. https://microsoftedge.microsoft.com/
Edge behaviour difference on Windows Server vs Windows 10
Hi, I notice that Edge appears to be behaving differently when run on Windows Server against standard Windows 10 PC's, with regards to extensions particularly. We have used "Enable local file links" extension on a clients Windows 10 PCs to allow access from an internal web application to some internal documents from the Browser. This works well, and giving the option to open the files, which then are then launched in the correct application within windows. However having deployed the same Extension on servers in this environment (and my own fairly vanilla VM environment without any special Edge or other GPO's) it seems to be ignored. Clicking the links to the files results in the text content of the file being displayed in Edge, rather than the option to open the file. In our setup, it is a refence file for a document management system, the contents of which are plain text, but with a .drf extension, but the issue can be re-created with just a plain .txt file. I can find no documents that explain this difference in behaviour. It also occurs with Chrome too. Any suggestions appreciated. Many thanks.
Extension Sync with work profiles
Hello folks, i'm wondering how extension sync is implemented with work profiles? Assuming there are managed clients with GPOs to restrict the installable extensions. These policies affect all profiles on the client including the sync-enabled work profile. Imagine a user is signing-in into her M365 work profile from an unmanaged client (which at time of writing can not be prevented!), now she would be able to install any extension. These extensions would possibly have access to all websites she is able to access/logon with her work profile. I assume the additionally installed extensions would then also be synced but would be disabled on the managed client through the policies. Is my assumption correct? How to prevent users from accessing websites through the work profile on unmanaged clients with enterprise blocked extensions? Best regards JoeExtensions Sync Enable/Disable per Machine
Hi The extensions have started syncing between my machines (which is great), but I actually want to have slightly different configs for some extensions between the machines, but sync the others. Is this possible? For example, I would like to sync all extensions, but keep 1password disabled on one machine and instead have 1passwordX running. The sync engine has downloaded both extensions to all machines (that's fine), but if I flip the switch to disable it on one, it gets disabled everywhere, which is not what I want. Some way of keeping the extension Enabled/Disabled status local to the machine, but keeping the syncing going for everything else would be great.
Extension loads late in Edge
I noticed in my Edge browser (ver. 87.0.664.75) that upon browser startup, the extensions loads late. But when I update my browser to version 88.0.705.50, it works fine and the extensions runs on startup. I would like to know what may caused this bug and what upgrade/fixes are made on the latest version that may have caused the fix on this bug? Thanks for answering!
