Forum Discussion
Bug Report: "Open in Sidebar" Available Despite Sidebar Being Disabled with HubsSidebarEnabled
We have encountered an issue where, despite having the sidebar disabled through the HubsSidebarEnabled policy, pages can still be opened via the "Open in Sidebar" option accessible through right-click context menus.
It appears that the "Open in Sidebar" feature was introduced in version 121, adding it to the page's right-click context menu. This allows for the sidebar to be opened even when it has been disabled using the HubsSidebarEnabled policy. Isn't this a bug?
Furthermore, if the "Open in Sidebar" function is not part of the HubsSidebar features, we would like to request the addition of a policy to disable this functionality itself.
Our company develops Web Filter Add-ons, and the sidebar browser cannot be hooked by the Add-on, which creates a loophole and is causing significant confusion.
5 Replies
- Kelly_Y
Microsoft
kojisugiyama Hello - I've checked and it looks like there is an upcoming policy that will control this behavior. It appears it will be in Microsoft Edge 123 soon. They are also discussing backporting to Microsoft Edge 122, but that has not been decided yet. The policy should be called "EdgeOpenInSidebarEnabled". Thanks!
-Kelly
Kelly_Y That's great news! Thank you for checking and for the update. The introduction of the "EdgeOpenInSidebarEnabled" policy in Microsoft Edge 123 sounds like a promising solution, and the potential backporting to Microsoft Edge 122 is also encouraging. I appreciate the information.
kojisugiyama and @Kelly_Y
The V122 Policy documentation and the stable release notes talks about its included.
https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies#edgeopeninsidebarenabled
https://learn.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel
Unfortunatly in the 122.0.2365.59 policy file its still not included. So documentation lies to us? Or is documentation just faster than real world?
