When using touch mode, clicking the "extension" button on the toolbar causes Edge to crash
Version 146.0.3844.0 (Official build) dev (64-bit) When using touch mode, clicking the extensions button on the toolbar causes Edge to freeze for two to three seconds before crashing. Accessing edge://extensions/ displays normal functionality, I can open extension detail pages and configure settings without issue. Reinstalling Edge or uninstalling all extensions resolves the problem. Disabling touch mode restores normal behaviour.
Extension ID: gdndpilddmlahjjcfmknlmindbklnbel Meeting Scheduler
Meeting Scheduler The extension is flagged with a warning that it contains malware. I am not aware how it got installed although The source of the extension is the "Microsoft Edge Add-ons Store but not able to find it on store. Can someone help with the triage how it could have got installed and what is this extension
Adblock extensions stop working Edge iOS on clearing browsing data
Ghostery and uBlock Origin Lite are available on Edge iOS as MV3 extensions for ad blocking but they stops working when Clear Browsing Data option is clicked for either time period, Last hour or All Time For making them work, Edge needs to be restarted or extensions need to be re-enabled I request Edge iOS team to fix this issueFeature 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 You
Edge Extension Publish/Upload API returns 500
I've just migrated from v1 to v1.1 of the https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/api/using-addons-api?tabs=v1-1#uploading-a-package-to-update-an-existing-submission. Since then I'm only receiving HTTP 500 responses from the API. All credentials are correct since I've also received some 4xx before that. The following is a curl req & res. All sensitive params are redacted. The exact same extension package gets distributed to the Chrome store. Nothing really changed in the extension package from v1 to v1.1. > POST /v1/products/.../submissions/draft/package HTTP/1.1 > Host: api.addons.microsoftedge.microsoft.com > User-Agent: curl/8.7.1 > Accept: */* > Authorization: ApiKey ... > X-ClientID: ... > Content-Type: application/zip > Content-Length: 345344 > * upload completely sent off: 345344 bytes < HTTP/1.1 500 Internal Server Error < Content-Length: 0 < Strict-Transport-Security: max-age=31536000; includeSubDomains < x-ms-middleware-request-id: ... < Request-Context: appId=... < Date: Tue, 04 Feb 2025 17:59:14 GMTNew Feature: CORS for extension content scripts | Manifest V3 next phase
It's behind a flag: edge://flags/#cors-for-content-scripts CORS for content scripts Prevent content scripts of Extensions from bypassing CORS. – Mac, Windows #cors-for-content-scripts Microsoft Edge Version 83.0.477.0 (Official build) canary (64-bit) Overview When web pages request cross-origin data with fetch or XHR APIs, the response is denied unless CORS headers allow it. In contrast, extension content scripts have traditionally been able to fetch cross-origin data from any origins listed in their extension's permissions, regardless of the origin that the content script is running within. As part of a broader Extension Manifest V3 effort to improve extension security, privacy, and performance, these cross-origin requests in content scripts will soon be disallowed. Instead, content scripts will be subject to the same request rules as the page they are running within. Extension pages, such as background pages, popups, or options pages, are unaffected by this change and will continue to be allowed to bypass CORS for cross-origin requests as they do today. https://www.chromium.org/Home/chromium-security/extension-content-script-fetchesAdd SOCKS5 (+ Authentication) support to Edge insider browser
Hi, Please consider adding SOCKS5 proxy support and Authentication (username and password) to the new Edge browser. currently only Firefox has that capability (without Auth). Microsoft Edge insider is using the same networking settings as google chrome which is not ideal and heavily relies on extensions and 3rd party programs. please create a separate proxy settings page that only effects Edge browser (like Firefox) and Not the whole Windows OS, and add SOCKS5 support to it. Thanks
