dev
42 TopicsExtension toolbar button not working (Edge Dev 132.0.2931.1)
In the latest Dev channel build, clicking on the extension button in the toolbar you see the UI is all strange and only shows one of your extensions taking up the whole window. You are also missing the bottom part of the UI. I've submitted feedback but I'm not sure if it captured a screencap of the issue. Screenshot below:Solved95Views2likes2CommentsThe edge dev is not opening
From the previous update of 119.0.2116.0 my microsoft edge dev is not opening. I think the problem come after this update and now I have manually updated to the latest 120.0.2165.1 with the installer and the problem is still there. I have seen the task manager the msedge process starts and run for sometime then automatically get terminated. Please Show any fix.478Views0likes0Commentsproblem on Surface Duo 2 Canary and Dev
Canary version 115.0.1867.0 still has the issue of going to the background whenever launched on Microsoft Surface Duo 2 .We are two weeks into it not working. the problem has migrated to Dev.. the problem started with trying to open a new Tab , Dev has this problem now for a week. Please fix this.Solved1.4KViews1like8CommentsEdge Dev 90 - Cannot manage certificates
Posted here https://answers.microsoft.com/en-us/microsoftedge/forum/all/microsoft-edge-dev-ubuntu-20041-manage/6a9e253b-3c81-4f3f-8d7b-20be69bad6e8 but I was advised to post here too. Problem: I cannot manage certificates on Ubuntu using this release - specifically I cannot import a privately issued client certificate. When opening edge://settings/?search=certificate I get this... The link is does not work, so how exactly does one manage [client] certificates in Edge? Contrast this with behaviour in Chromium Version 88.0.4324.50 (Developer Build) Ubuntu 20.04 (64-bit) where this feature is enabled and allows me to manage my certificate requirements... System details $ lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal $ dpkg --list|grep edge ii microsoft-edge-dev 90.0.782.0-1 amd64 The web browser from Microsoft Any ideas? --dave1.6KViews0likes2CommentsSay hello to the new Favorite Sidebar feature in the Edge browser
Microsoft Edge Version 87.0.654.0 (Official build) dev (64-bit) (This could be a controlled feature rollout meaning only available to a subset of insiders) this is the new view you get when you click on favorites button on Edge toolbar and once you click on that Pin icon, the sidebar will show up I love this mechanism and implementation, very neat and smart! thanks also the favorites menu no longer closes when you open favorite sites in new tabs, something I know a lot of people asked for.21KViews8likes37CommentsInstagram Live's not playable on Canary and Dev branches
having issues playing any IG Live Streams on the Canary and Dev versions; the beta and the standard release both seem okay; it recently began within the last 3-4 days; Tried to clear out settings/reinstall browser/kill all extensions/inprivate mode and adjust by tweaking the media flags but no luck. Tried to determine the issue by looking on the same page with working vs non working browser and could not quite pin down the issue and i don't see any running threads on any boards; so curious if anyone else see's the same? (NOTE: live streaming on instagram is where i noticed the issue, didnt' explore other streaming sites, did not impact playing a user's stories, only the live streams)623Views0likes0CommentsAccess Microsoft Edge Legacy/Classic (EdgeHTML) after installing the new version of Microsoft Edge
Access Microsoft Edge Legacy/Classic (EdgeHTML) after installing the new version of Microsoft Edge (Chromium) This article describes how to access Microsoft Edge Legacy (version 45 and earlier) after installing the new version of Microsoft Edge. Note: This article applies to the Microsoft Edge Stable channel. The procedures in this article apply to systems that have been updated with the latest security updates, up to and including November 2019. When the new version of Microsoft Edge is installed, the old version (Microsoft Edge Legacy) will be hidden. All attempts to launch the old version will redirect the user to the newly installed version of Microsoft Edge. Before you begin Before using the detailed instructions in this article, consider the following 2 steps to enable a side-by-side browser experience. These steps will let your users run Microsoft Edge Legacy and the next version of Microsoft Edge (Beta channel) side-by-side. Prevent the automatic install of the next version of Microsoft Edge by Windows Update. For more information, see Windows Update: FAQ Install the Beta channel of the new version of Microsoft Edge. Note This side-by-side solution is less complex and requires less management that the detailed solution described next in this article. How operating system (OS) changes are triggered After the systems are fully updated and the Stable channel of the next version of Microsoft Edge is installed, the following registry key and value is set: Key: SOFTWARE\Microsoft\EdgeUpdate\ClientState\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062} Key value: BrowserReplacement Important This key is over-written every time the Microsoft Edge Stable channel is updated. As a best practice, we recommend that you don’t delete this key to allow users to access both versions of Microsoft Edge. How to enable a side-by-side experience with both versions of Microsoft Edge Installing the Stable channel of the next version of Microsoft Edge at system-level will cause the current version (Microsoft Edge Legacy) to be hidden. If you want to let your users to see both versions of Microsoft Edge side-by-side in Windows, you can enable this experience by setting the Allow Microsoft Edge Side by Side browser experience group policy to "Enabled". To enable the side by side browser experience policy: Open the Group Policy Editor. Under Computer Configuration, go to Administrative Templates>Microsoft Edge Update>Applications. Under Applications, select "Allow Microsoft Edge Side by Side browser experience" and then click Edit policy setting. Select Enabled and then click OK. Note By default, this group policy is set to "Not configured", which results in Microsoft Edge Legacy being hidden when the new version of Microsoft Edge is installed. For the best experience, the Allow Microsoft Edge Side by Side browser experience should be enabled before the new version of Microsoft Edge is deployed to your users' devices. If the group policy is enabled after Microsoft Edge is deployed, there are the following side effects and required actions: Allow Microsoft Edge Side by Side browser experience won't take effect until after the installer for the new version of Microsoft Edge is run again. Note The installer can be run directly or automatically when the new version of Microsoft Edge updates. Microsoft Edge Legacy will need to be re-pinned to Start or the Taskbar because the pin is migrated when the new version of Microsoft Edge was deployed. Sites that were pinned to Start or the Taskbar for Microsoft Edge Legacy will be migrated to the new version of Microsoft Edge. Source15KViews0likes2Commentsheader styles not properly displayed in collections notes
Hi, While editing a note, if you choose some header styles ( either "header 1" or "header 2" or "header 3" or "paragraph" ) , they are properly displayed in the note , until the note is saved ( through the "check" icon in the note toolbar ) ; then , all header formatting is lost ; however , the bold , italic , underline and bullet list styles seem to be saved ) . It is a regression that appears both in the "dev" channel ( 93.0.933.1 ) and in the stable channel ( 91.0.864.67 ) whereas it worked before ( even if I don't precisely remember since when it stopped working ) . Am I the only one to see this ? Thank you for reading ( and also fixing it ) p.s. : I already filled a bug report in the feedback menu item550Views0likes0Comments