dev
42 TopicsSay 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.21KViews8likes37CommentsSet Aside Tab Feature | Collection Added to Edge insider Dev and Canary
Now you can Set your Tabs Aside Quickly and reopen them later. these tab groups Can get Synced with other devices that have Edge browser installed (Only desktops for now) so you can also resume your work from another computer. The tab groups that are set Aside are non-volatile, meaning they are not automatically deleted once you reopen them (unlike Edge legacy's behavior) you can give custom names to the tab groups you set Aside. Here is a 1080p 60FPS video to show you how easily it's done: https://streamable.com/uitriSolved19KViews14likes50CommentsEdge problem with full screen mode (a.k.a) --kiosk mode
From Edge Version 79.0.309.68 All the way to Version 81.0.396.0 canary, they have this problem. when I use this switch/command on the target of Edge shortcut: "--kiosk" (without quotes) I do get to launch Edge in full screen mode, but there is no way to interact with the toolbar anymore, neither is there any way to close Edge, other than pressing Windows key to show the taskbar. Edge Canary and Dev have this flag: #edge-enable-shy-ui More info here: https://techcommunity.microsoft.com/t5/discussions/finally-here-the-real-full-screen-experience-in-edge-insider/m-p/1011888 and you can see how it behaves in fullscreen mode with that flag. but when kiosk mode is used, that behavior doesn't work anymore.16KViews1like2CommentsMicrosoft is Adding Classic ‘Edge Mode’ to New Edge Browser
Microsoft is developing a new 'Edge Mode' that lets users visit sites using the same rendering engine as Classic Edge to continue using legacy web applications. In the Chromium-based Microsoft Edge, users can enable a feature called 'Internet Explorer Mode' that causes the browser to emulate Internet Explorer 11. This mode is designed for organizations that need to utilize web apps that were designed for the legacy browser. When Internet Explorer mode is enabled, the Internet Explorer icon will appear in the address bar and sites that you visit will think you are running Internet Explorer 11. Edge in Internet Explorer Mode If Internet Explorer mode is enabled, the Microsoft Edge Dev and Canary builds have also added a new option called 'Open sites in Edge mode'. While nothing official has been announced about this feature, it will most likely allow the browser to emulate Classic Edge. Open sites in Edge mode To use this feature, an Edge flag named "Enable IE Integration" at edge://flags/#edge-internet-explorer-integration must be set to 'IE Mode'. Enable IE Integration flag Once configured, users can then launch the new Microsoft Edge program with the '--ie-mode-test' command line argument to enable the Internet Explorer mode feature. Launch with --ie-mode-test argument Once that feature is enabled, an additional 'Open sites in Edge mode' option will become available under Options -> More Tools. This new mode does not appear to do anything as of yet. Still being developed This feature is still being developed as can be seen by the browser user-agents being sent when using these emulation modes. When a browser visits a web site, a user-agent string is sent to the web site with each request that can be used to identify the name and version of the browser. This user-agent can then be used by the site to determine what features the browser supports and any code changes that need to be made so that the web site renders properly. Below are the various user-agent strings sent by Microsoft Edge, Classic Edge, and the IE and Edge modes. New Microsoft Edge browser user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4023.0 Safari/537.36 Edg/81.0.396.0 Classic Microsoft Edge user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Edge/18.19013 Internet Explorer Mode user-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko Edge Mode user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4023.0 Safari/537.36 Edg/81.0.396.0 As you can see, when in Internet Explorer Mode the user agent is set to the one used by Internet Explorer 11. Edge Mode, though, still uses the same user-agent as the new Microsoft Edge rather than Classic Edge, which indicates that this feature is still in its infancy and being developed. As with all Microsoft software features, this one may not make it to Release, but based on the availability of IE Mode, we can expect that it will. Source15KViews3likes10CommentsAccess 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. Source15KViews0likes2CommentsWhat were the main reason(s) Microsoft chose Chromium over Firefox?
I just saw a post on my Twitter from EdgeDev and they said they contributed so much to the project. with hashtag #Opensource Open source is good but Chromium is not the only open source engine, There is Firefox, fully open source and it uses Gecko layout engine. it's been around way longer than Chromium, in fact it is one of the first engines that was ever created. So I'm both curious and really interested to know the logic and reason that why Microsoft chose Chromium instead of Firefox. hopefully we will see some official responses here too in addition to others 🙂Solved14KViews3likes27CommentsHow to get the new Edge insider Logo after update
UPDATE 1: You have to uninstall your browser and then download and reinstall it again from here: https://www.microsoftedgeinsider.com/en-us/download/ this is one way to get the correct icon everywhere (start menu, taskbar, desktop) and with the correct label (Canary, Dev, Beta) I did it and chose to delete user data during uninstall, but be careful, make sure to enable Sync before uninstall to prevent from losing any data. UPDATE 2: Thanks toasplode If you create a new profile and then promptly delete it, the icons are fixed! UPDATE 3: Thanks to MitchDahl signing out of Sync and then back in. UPDATE 4: Thanks to Dennis5mile "I found another way to change the icon for whichever version you are using. First right click the icon and then right click the exe for that version of edge you want changed then click properties.. follow the photos below which I did from my taskbar... then on next screen choose change icon.. Then choose the icon you want, but make sure the path is correct"14KViews4likes13CommentsEdge not receiving notifications when closed
This has been going on for months, it actually never worked and despite many posts from other users, it wasn't put on the feedback list to be fixed. I tried sending several feedbacks through browser as well in the last months. I hope someone manually give this a higher priority. here is the Chrome article about this: https://developers.google.com/web/ilt/pwa/introduction-to-push-notifications "Push messaging lets developers engage users by providing timely and customized content outside the context of the web page. It is one of the most critical APIs to come to the web, giving users the ability to engage with web experiences even when the browser is closed, without the need for a native app install." Currently Edge canary is Version 81.0.406.0 (Official build) canary (64-bit) all the related flags (native notifications etc etc) are all tested and they have no effects.Solved12KViews6likes29CommentsBlock 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. Source8KViews0likes2Comments