Browser
60 TopicsSuggestion: add Progress Bar and Next/Prev options to the PiP (Picture in Picture) in Edge browser
Suggestion: add Progress Bar and Next/Prev options to the PiP (Picture in Picture) in Edge browser Here is a video of my side by side comparison of PiP in Edge Canary Version 83.0.461 and PiP in Windows 10 Movies & TV app which is the superior one. Also allow to control that progress bar in PiP. use the same small minimal style from the app on Windows 10 but on mouse hover, the progress bar needs to get bigger and come Up so user can control it and click on it. Thanks. https://streamable.com/rocr2Solved5.9KViews7likes12CommentsPin tab groups in edge
Hello, I'm in love with Edge's new tab Group feature, but there is one issue with it. usually, People want those groups to open whenever the browser starts up. so I have a suggestion to add Pin group feature where it works just like pin tab. What do you think insiders?13KViews12likes10CommentsCopilot or Discover browser extension not working as expected for managed Edge browser
If your organization manages the MS Edge browser or has decided to limit the availability of Copilot (previously known as Discover in Edge) until administrators have a handle on its capabilities and risks, then this post may be helpful. You will find in the following article -- Copilot in Edge | Microsoft Learn -- Microsoft suggests for Admins who want to manage Copilot in Edge, they can "use multiple group policy settings to manage the behavior of the Copilot in Edge sidebar:" # I have found it very strange, especially when referencing brand new tools like Copilot, that Microsoft documentation suggests admins are still using, or should use group policy as opposed to more modern management tools like Intune # The article suggests the below "group policy settings" can be used to manage Copilot behavior in Edge: To allow or block Copilot in Edge from using browsing context, use the DiscoverPageContextEnabled policy. This prevents Copilot from using webpage or PDF content from being used to respond to prompts. To disable Copilot in Edge entirely, use the HubsSidebarEnabled policy. Blocking Copilot in Edge automatically blocks all Edge sidebar apps from being enabled. Now according to these instructions, you would use the DiscoverPageContextEnabled policy to allow Copilot in Edge to use browsing context and seemingly (since HubsSidebarEnabled is used to disable Copilot) you would set HubsSidebarEnabled to enabled in order to force Copilot to appear and be available for your users. To an admin still using group policy to set these maybe everything works fine -- In previous testing I have hacked my registry to create the above keys and can't remember the results, but it was kind of a pointless test since I personally use Intune to manage our Edge browser. If you're like me and use Intune to manage Edge's browser configuration at your organization, then seeing the keys above may prompt you to head to the Intune settings catalog to look for equivalent settings that you can use to set similar policy. Next, I'll share my findings from diving into how I might use something available in the Intune settings catalog. My findings are as follows: Show Copilot -- you will find this setting if you nav down through edge://settings/sidebar. With no settings configured related to Copilot you will see this in the off state and when you hover the briefcase icon where you would usually see "this setting is managed by your organization," you will just see a blank textbox. Right out of the gate this is a weird behavior and the only thing I have been able to chalk it up to so far is a bug -- my thinking is if your browser is managed by the organization then by default the Show Copilot setting will be in the off state. Ok, so now how do we actually get this thing on if we are ready for our users to use it? Discover feature In Microsoft Edge -- this is a setting you can find in the Intune settings catalog. Previously Copilot in Edge was called Bing Discover and it had a "B" icon. If you configure this setting today and set it to enabled you might expect it to display Discover or Copilot, however, when you check the edge://policy report you will find that EdgeDiscoverEnabled (as it shows up on the report) actually errors out and is described as an "unknown policy," and there will be no effect to the browser or to the Show Copilot setting I discussed above. HubsSidebarEnabled -- now back to the HubsSidebarEnabled setting referenced in the linked Microsoft documentation. Supposedly you would use this setting to "disable Copilot in Edge entirely." Now you can find a setting called Show Hubs Sidebar in the Intune settings catalog and you can set it to enabled. When you nav to the edge://policy report you will even see it successfully configured and reporting in as OK. However, in my testing I have not seen this have any effect on the Always show sidebar setting found at edge://settings/sidebar, and I have not seen this have any effect on the Show Copilot setting found at edge://settings/sidebar when you drill into the Copilot settings. So, my only conclusion here is that the HubsSidebarEnabled from the Intune settings catalog isn't ready for showtime. DiscoverPageContextEnabled -- This is a setting you can find in the Intune settings catalog called Enable Discover access to page contents for AAD profiles. This setting will successfully configure and report back as OK in edge://policy report, however, I have not tested any further and can't tell you if it is actually doing what it intends to since I have not successfully configured Copilot using the other Intune settings. The only success I have found so far in all of this Copilot, Discover and Sidebar research are the following two extension IDs that can be added to your force install extension list -- and as a result the Copilot browser extension should appear. If you are new to using Intune to manage browser policy and aren't sure what I mean by the 'force install extension list,' drop a comment and I'll be happy to add some detail about that. Extension IDs: nkbndigcebkoaejohleckhekfmcecfja ofefcgjbeghpigppfmkologfjadafddi I found these extension IDs by using ctrl + f on the edge://sidebar-internals page looking for results related to the search term "Discover." At the moment this seems like the best way to enable and test Copilot until the Intune settings currently available begin working as they are described. This is not meant to criticize the speed at which Microsoft has made settings available or set them up to work perfectly, but to prompt discussion and help others who might be going in circles trying to figure out if they're configuring something incorrectly. TL;DR There are currently settings in the Intune settings catalog that don't seem to work as expected if you are trying to enable/disable Copilot for a managed instance of Edge at your organization. As a workaround there are a couple extension IDs that can be added to your ForceInstallExtension list to help display Copilot in the Edge sidebar. I've attached some screenshots related to different things referenced in this post.Solved9.6KViews3likes5CommentsBrowser for SQL Server 2017 and 2019
Hello, my question is the following. Despite having the latest updates released for SQL Server 2019 and 2017, I notice that SQL Server Browser does not change versions, remaining in the versions mentioned below. I would like to know if they are in fact the latest versions of SQL Server Browser released in the 2017 and 2019 packages. If the versions below are correct, if they really have not been updated. Browser for SQL Server 2017 14.0.1000.169 Browser for SQL Server 2019 15.0.2000.5150Views0likes1CommentDoes anyone inform their users how to set OneDrive to open in the client applications?
I'm looking for other opinions and experiences on this because of a question I've been asked. There are two ways to change your OneDrive for Business area (in browser) to open documents in the client application. It only affects the OneDrive that it is being set upon though, but it definitely has ripple effects that can cause confusion in users when they experience inconsistencies in behaviors. I think the shared documents experiences in particular might be the areas that would experience most of the weird behaviors. Has anyone else documented or instructed users about doing this? What behavior changes in the UI were noticed by people? Was it confusing or did people just brush off the inconsistent opening in the browser/client application experiences?647Views0likes4CommentsOutlook / Office links opening in Edge (with Sidebar)
Hi All, There has been a recent change in the way that URL's from office, in my case Outlook, open.. For my current employer they use specific SaaS tools that only work in Google Chrome so i've set the default browser for all workplaces on Chrome. Same as this tutorial: Set Google Chrome as Default Browser Using Intune – Learn Azure, OpenAI, M365, Terraform, Cybersecurity (ntweekly.com) But now the strange thing, despite having Chrome as default browser on the system, and having a cloud policy and configuration profile activated, the weblinks still open in EDGE.. Very frustrating for end users, does anyone have a permanent solution for this or encountered the same?Solved1.5KViews0likes4CommentsFeature 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 you561Views1like0CommentsNew 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-fetches6KViews0likes1CommentNew Feature in Edge: Provide option to keep specific cookies when closing Edge browser
This feedback item is now available in Microsoft Edge Version 83.0.470.0 (Official build) canary (64-bit) Status Feedback On this list for Planned for March Provide option to keep specific cookies when choosing to clear browsing data on close 19 weeks edge://settings/clearBrowsingDataOnClose You've allowed the following sites to save and read cookies on your device. Cookies for these sites won't be cleared when you exit the browser.10KViews5likes22Comments