[Feature Request] Edge for Business-Extension Policy-blank minimum version breaks ExtensionSettings.
Hi, I have a Core Edge for Business policy, where I manage settings and extensions for majority of users in my company. I was adding an extension to it to Allow an extension being installed. By default when You choose extension from a store it is getting added to GUI with setting "Allow". After that when I edit entry for this addon and tried to add minimum version (8.6 in Edge store, while schema is #.#.#) I decided not to add it to not overcomplex settings. I have saved the settings. Few second later all my extensions were gone, some users reported same problems. Luckly I have quickly reverted the changes so policies did not update for everyone. Replication steps: Under Edge://policy I have identified that ExtensionSettings report Error: Error at ExtensionSettings.hfaciehifhdcgoolaejkoncjciicbemc.minimum_version_required: Schema validation error: Invalid value for string Json shows: "hfaciehifhdcgoolaejkoncjciicbemc": { "installation_mode": "allowed", "minimum_version_required": "", "override_update_url": false, "toolbar_state": "default_hidden" }, In GUI there is no clue about it, looks like not configured, when saving all goes "green". Extensions are getting uninstalled. Once reverted some extensions are back and require reconfiguration. I.e. Passsbolt asks for recovery key. Please if possible add a feature to validate such settings to not allow saving : "minimum_version_required": "" as in some cases in production it might be a nightmire ( Imagine reconfiguring ## addons times #### Users ).Block Microsoft from running experiments in the Microsoft Edge browser
Browsers like Firefox, Chrome or Microsoft Edge come with built-in functionality to run experiments. Browser makers like Mozilla or Google may enable or disable features or changes in select browsers; this is often used to A-B test features or get early feedback on new implementations. While most users may not even notice that experiments are running in their browsers, it happened in the past that experiments caused issues. The latest case was revealed in November when administrators from around the world reported that a Chrome experiment would crash browsers in organizations worldwide. Negative side-effects of experiments are a problem for home users and business users alike, and it is often desirable to disable or block experiments from being downloaded and run. Microsoft distinguishes between controlled feature rollouts and experiments in the company's new Chromium-based Microsoft Edge web browser. Both are made available to part of the user base when they start to roll out but similarities end here. Microsoft notes: Microsoft Edge builds have features and functionality that are still in development or are experimental. Experiments are like CFR, but the size of the user group is much smaller for testing the new concept. These features are hidden by default until the feature's rolled out or the experiment's finished. Experiment flags are used to enable and disable these features. System administrators may use the "Control communication with the Experimentation and Configuration Service" on pro and Enterprise editions of Windows 7, 8.1 or 10 to prevent experiments in the browser. Here is what is needed for that: Get the latest Microsoft Edge policy file from the Microsoft Edge Insider website. It is likely that the policies will become available natively eventually when Edge is released and integrated in Windows. Extract the file (first a cab, then a zip). Open Windows > Admx. Copy the two .admx template files to C:\Windows\PolicyDefinitions\. Open the language folder that matches the system language and copy the .adml files to the corresponding language folder of C:\Windows\PolicyDefinitions\ Open Start, type gpedit.msc and hit the Enter-key to open the Group Policy Editor. Consult this Docs page on the Microsoft website for additional scenarios, e.g. when domain controllers are used. Open Computer Configuration > Administrative Templates > Microsoft Edge. Open the policy "Control communication with the Experimentation and Configuration Service" policy. Set the policy to Enabled. Set it to either "Retrieve configurations only" or "Disable communication with the Experimentation and Configuration Service". Retrieve will download configuration payloads only, disable won't download or enable them. The behavior of not configuring the policy differs depending on whether it is a managed or unmanaged device. Managed devices will download the configuration only while unmanaged devices will retrieve configurations and experiments. Source
How to disable confirmation pop-up in Edge Browser when opening many tabs
I have bookmarks arranged in multiple folders, varying from 10 to 500 or more links per folder. Whenever I try to click on the bookmark folder to open all of them at once, I always get this Pop-up, which is very annoying to me (I was ignoring that pop-up for more than a year). Is there any built-in setting to disable or increase the limit? P.S: FYI, I am on a very high-end laptop(M4 pro with increased RAM & SSD) and due to my use case, I have to regularly, almost every day open many links
--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?
Edge error RESULT_CODE_MISSING_DATA or RESULT_CODE_KILLED_BAD_MESSAGE even in the settings menu.
After the KB5050021 (Windows 11 (23H2)) update, Edge stopped working. The same error appears on all tabs and even in the settings: Error code: RESULT_CODE_MISSING_DATA. I deleted the update, but Edge still didn't work. Edge only partially worked in compatibility mode with Windows 8. Does anyone know what the problem could be? Without compatibility, the error is either RESULT_CODE_MISSING_DATA or RESULT_CODE_KILLED_BAD_MESSAGE, and on any tabs and even in the settings menu. Edge Version 134.0.3124.93 (Official Build) (64-bit) DEV/BETA/CAN also don't work with the same errors. UDP. After the KB5053602 (Windows 11 (23H2)) update, Edge still not working. Is there a solution to this problem?Feature Request - Collections & Etc.
I would like the ability to add all open tabs in a window to a collection instead of having to individually add them one by one. And also maybe some extra customization/tweaks like what Vivaldi has (Different methods of grouping; Stacked, Two Level, or Compact Fitted to single tab width, Tab Tiling; Multi-Window tabs in a single browser window, Lots more UI customization/configuration; completely custom theme(s), and a Toolbar Editor). I know this isnt stuff that can just be added on a whim, but i would like to see if any Edge devs see this post. My main request so far is just the collections one i mentioned. Thank youNew 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-fetches
