The new Microsoft Edge is better than Chrome in my opinion and I go through a few reasons why. Microsoft has finally managed to create a browser worth using.
- The Beta channel is the most stable Microsoft Edge preview experience. With major updates every 6 weeks, each release incorporates learnings and improvements from our Dev and Canary builds. Also available for. Windows 8 / 8.1.
- Microsoft Edge is a cross-platform web browser developed by Microsoft. It was first released for Windows 10 and Xbox One in 2015, then for Android and iOS in 2017, for macOS in 2019, and as a preview for Linux in October 2020.
Back in 2019 when Microsoft announced that it would rebuild Microsoft Edge browser based on the Chromium engine, the company also promised it would retain the look and feel of the original version of the browser that was bundled with Windows 10 since 2015.
And while most of Edge Legacy has already moved to the Chromium-based successor, the transition is still under way, with some features still under development to work exactly as they did in the previous version of the browser.
One of them is the scrolling, which as many Windows 10 know already, was absolutely amazing in the legacy version of Microsoft Edge. Everything was super smooth and fluid, and Microsoft wants the same experience to come to the Chromium browser as well.
Of course, this means that other Chromium browsers could benefit from the improved scrolling as well, including Google Chrome, but that’s a completely different story,
In the meantime, as Microsoft works on bringing the old scrolling to the new browser, certain things could be broken down, and this is the case of the latest version of Edge Dev that introduces such a bug.
Ore specifically, scrolling on trackpads or touchscreens in the latest Edge Dev doesn’t work exactly as expected, and Microsoft describes it as a wobbling effect. This only happens on some sites, it says, and while a fix is in the works, you can very well disable the experimental scrolling to bring things back to normal.
“Some users are seeing “wobbling” behavior when scrolling using trackpad gestures or touchscreens, where scrolling in one dimension also causes the page to subtly scroll back and forth in the other. Note that this only affects certain websites and seems to be worse on certain devices. This is most likely related to our ongoing work to bring scrolling back to parity with Edge Legacy’s behavior, so if this behavior is undesirable, you can temporarily turn it off,” Microsoft says.
Disabling the new scrolling system means you’ll just have to stick with the standard Chromium scrolling, but given the new one experiences issues, this is most likely the better way to go. Of course, this is just a temporary workaround until Microsoft manages to get the scrolling feature right, so you can revert the changes once this happens.
Disabling the Edge Legacy scrolling behavior in the Chromium successor is possible. All you need to do is turn to a dedicated flag that lets you do the whole thing. So the first thing you need to do is type the following code in the address bar to launch the advanced flags screen:
edge://flags
Next, in the search box at the top of the screen, type the following flag name:
Microsoft Edge scrolling personality
If you just want to use a shortcut, copy the following code and paste it in the address bar of Edge Dev:
edge://flags/#edge-experimental-scrolling
Next, you need to use the drop-down menu for this flag to select the disabled value. A reboot of the browser will be required to save your changes, but when the browser relaunches, everything should be back to normal and the scrolling should work just as expected.Microsoft hasn’t provided any ETA as to when it could fix the scrolling in Edge. The next stable release is due in mid-May, while new Dev builds land every week as per the standard release schedule. It remains to be seen when this bug would be corrected, but in the meantime, the aforementioned workaround comes in handy to continue using Edge Dev without the scrolling problem. Install mysql for mac.
-->Use the following information to configure Microsoft Edge policy settings on your Windows devices.
Note
This article applies to Microsoft Edge version 77 or later.
Configure policy settings on Windows
You can use group policy objects (GPO) to configure policy settings for Microsoft Edge and managed Microsoft Edge updates on all versions of Windows. You can also provision policy through the registry for Windows devices that are joined to a Microsoft Active Directory domain, or Windows 10 Pro or Enterprise instances enrolled for device management in Microsoft Intune. To configure Microsoft Edge with group policy objects, you install administrative templates that add rules and settings for Microsoft Edge to the group policy Central Store in your Active Directory domain or to the Policy Definition template folder on individual computers and then configure the specific policies you want to set.
You can use Active Directory group policy to configure Microsoft Edge policy settings if you prefer to manage policy at the domain level. This enables you to manage policy settings globally, targeting different policy settings to specific OUs, or using WMI filters to apply settings only to users or computers returned by a particular query. If you want to configure policy on individual computers, you can apply policy settings that only affect the local device using the Local Group Policy Editor on the target computer.
Microsoft Edge supports both mandatory and recommended policies. Mandatory policies override user preferences and prevents the user from changing it, while recommended policy provide a default setting that may be overridden by the user. Most policies are mandatory only; a subset are mandatory and recommended. If both versions of a policy are set, the mandatory setting takes precedence. A recommended policy only takes effect when the user has not modified the setting.
Tip
You can use Microsoft Intune to configure Microsoft Edge policy settings. For more information, see Configure Microsoft Edge using Microsoft Intune.
There are two administrative templates for Microsoft Edge, both of which can be applied either at the computer or Active Directory domain level:
- msedge.admx to configure Microsoft Edge settings
- msedgeupdate.admx to manage Microsoft Edge updates.
To get started, download and install the Microsoft Edge administrative template.
1. Download and install the Microsoft Edge administrative template
If you want to configure Microsoft Edge policy settings in Active Directory, download the files to a network location you can access from a domain controller or a workstation with the Remote Server Administration Tools (RSAT) installed. To configure on an individual computer, simply download the files to that computer.
When you add the administrative template files to the appropriate location, Microsoft Edge policy settings are immediately available in the Group Policy Editor.
Go to the Microsoft Edge Enterprise landing page to download the Microsoft Edge policy templates file (MicrosoftEdgePolicyTemplates.cab) and extract the contents.
Add the administrative template to Active Directory
On a domain controller or workstation with RSAT, browse to the PolicyDefinition folder (also known as the Central Store) on any domain controller for your domain. For older versions of Windows Server, you may need to create the PolicyDefinition folder. For more information, see How to create and manage the Central Store for Group Policy Administrative Templates in Windows.
Open MicrosoftEdgePolicyTemplates and go to windows > admx.
Copy the msedge.admx file to the PolicyDefinition folder. (Example: %systemroot%sysvoldomainpoliciesPolicyDefinitions)
In the admx folder, open the appropriate language folder. For example, if you’re in the U.S., open the en-US folder.
Copy the msedge.adml file to the matching language folder in the PolicyDefinition folder. Create the folder if it does not already exist. (Example: %systemroot%sysvoldomainpoliciesPolicyDefinitionsEN-US)
If your domain has more than one domain controller, the new ADMX files will be replicated to them at the next domain replication interval. Picopix fun viewer for mac.
To confirm the files loaded correctly, open the Group Policy Management Editor from Windows Administrative Tools and expand Computer Configuration > Policies > Administrative Templates > Microsoft Edge. You should see one or more Microsoft Edge nodes as shown below.
Add the administrative template to an individual computer
- On the target computer, open MicrosoftEdgePolicyTemplates and go to windows > admx.
- Copy the msedge.admx file to your Policy Definition template folder. (Example: C:WindowsPolicyDefinitions)
- In the admx folder, open the appropriate language folder. For example, if you’re in the U.S., open the en-US folder.
- Copy the msedge.adml file to the matching language folder in your Policy Definition folder. (Example: C:WindowsPolicyDefinitionsen-US)
- To confirm the files loaded correctly either open Local Group Policy Editor directly (Windows key + R and enter gpedit.msc) or open MMC and load the Local Group Policy Editor snap-in. If an error occurs, it’s usually because the files are in an incorrect location.
2. Set mandatory or recommended policies
You can set mandatory or recommended policies to configure Microsoft Edge with the Group Policy Editor for both Active Directory and individual computers. You can scope policy settings to either the Computer Configuration or User Configuration by selecting the appropriate node as described below.
To configure a mandatory policy, open the Group Policy Editor and go to (Computer Configuration or User Configuration) > Policies > Administrative Templates > Microsoft Edge.
To configure a recommended policy, open the Group Policy Editor and go to (Computer Configuration or User Configuration) > Policies > Administrative Templates > Microsoft Edge – Default Settings (users can override).
3. Test your policies
On a target client device, open Microsoft Edge and navigate to edge://policy to see all policies that are applied. If you applied policy settings on the local computer, policies should appear immediately. You may need to close and reopen Microsoft Edge if it was open while you were configuring policy settings.
For Active Directory group policy settings, policy settings are propagated to domain computers at a regular interval defined by your domain administrator, and target computers may not receive policy updates right away. To manually refresh Active Directory group policy settings on a target computer, execute the following command from a command prompt or PowerShell session on the target computer:
You may need to close and reopen Microsoft Edge before the new policies appear.
You can also use REGEDIT.exe on a target computer to view the registry settings that store group policy settings. These settings are located at the registry path HKLMSOFTWAREPoliciesMicrosoftEdge.