Forum Widgets
Latest Discussions
Chrome extension managed storage policy
Hi there, I've developed a chrome extension and now we want to deploy it using Intune. Force install of extension works great but I can't pass managed data to the extension. Here is the scheme: { "type": "object", "properties": { "apiKey": { "title": "API Key", "description": "An API key to communicate with server.", "type": "string" } } } This is the policy that I created in Intune: OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~3rdparty~extensions~eagefwefpbjpewefliifpgfgoewfknnmk~policy Data type: String Value: {"apiKey":"mykey123"} But it doesn't appear in chrome://policy and when I get policies in my code with: const result = await chrome.storage.managed.get(null); The result is empty! What is the problem here? And how to fix it?
Edge Dev > Enterprise State Roaming / Sync Broke
I noted in Edge DEV my profile stopped syncing even though its set by policy to be on the journey took me to edge://settings/profiles/sync where turn on sync is presented - so i turn it on a confirm and cancel button appear as well as the expected other areas (but showing as off by policy???) hitting confirm just makes confirm and cancel disappear with no changes these are not new? what gives or is changing? is sync just broke in dev for now? Edge Beta and Stable are not impacted.
Starting Edge as a process immediately fires exited event
Hi! Recently I have encountered a rather annoying bug on Windows 11 IoT LTSC where I launch an edge as a process from my .net 9.0 C# code. I need to track Edge and if it exits for some reason I have to relaunch it. I'm tracking whether it has exited by subscribing to the Process.Exited event, but on the beforementioned operating system this event immediately fires even though the Edge itself visibly does not close and stays functional without any problem. This results in infinite edge processes getting launched, since every new instance also exits. Interestingly this issue does not occur when tested with other browsers nor it occurs on Windows 11 Pro, everything works completely fine in these two scenarios. I'm guessing IoT version has some kind of different power plan to reduce battery drainage and CPU usage if possible. My other assumption is that the msedge.exe available with default windows is just a parent process on the IoT version, and it just starts the actual processes needed to present the content of my web app. It'd be great if you could check this and come back to me. Thank you! Kind regards, Gallusz.Manifest V2/V3 timeline update?
Google/Chromium announced at the end of March that MV2 would be completely removed from Chrome in v139, meaning that v138 will be the last version that can run MV2 extensions even using the policy override. Since v139 is expected sometime in July, that time is coming up fast! In Microsoft's timeline, it is stated: Manifest V2 extensions will continue to be supported through Enterprise policies at least until the date in the Chromium Manifest V2 support timeline. Since Google will be removing it as of v139, can we expect the same for Edge? Just trying to plan out notification to some groups who use custom extensions (ie: from vendors or internally created) that they will see the older extensions be removed/disabled. Thank you!Microsoft Editor does not work
As the title states, if you have the Microsoft Editor enabled in Edge (this appears to be any version from Stable to even Canary), no spell or grammar check will work at all. If you enable the standard editor, you will get at least spell check back. This screenshot is with the MS Editor enabled - it seems to know what is spelled incorrectly but gives you zero suggestions. And here is the standard spell check working as it should. Testing in Edge stable 136.0.3240.50 + Dev 137.0.3282.1OrgBrandingCustomName no longer working in Dev/Canary
The latest Dev/Canary builds have moved the profile icon from the top left back to the address bar near the extension/plugin list. We have the OrgBrandingCustomName cloud policy enabled which no longer works due to this change. Is this expected behavior? Current stable channel behavior: New Dev/Canary behavior:
