Search the Community
Showing results for tags 'dev build'.
Found 2 results
Karlston posted a topic in Software NewsMicrosoft Edge gets the ability to generate unique passwords for the users Microsoft has added another highly requested feature that should help users when creating a new account on any website. With the latest Edge updates, users can now take the browser's help to generate strong and unique passwords for different websites, as spotted by Techdows. The feature is currently limited to Edge Canary and Dev builds, but if you are using one of those then you can just visit a website and click on create a new account to try the feature out for yourself. Once you have entered all the information and selected the Edge's suggested password, the browser will add your credentials to the saved password list so you don't have to remember it. If you're already using a password manager or don't want password recommendations from Microsoft Edge then you can follow the steps below to disable the feature: Open Microsoft Edge and click on the ellipsis icon (...) on the top right corner of the browser. Navigate to Settings > Profiles > Passwords. Find the "Suggest strong passwords” setting and turn off the toggle to disable the feature. You can always go back to the passwords menu if you want to enable the feature again in the future. Microsoft Edge Canary and Dev are currently on version 87 which is expected to roll out to Beta users in the near future. Edge Stable users, on the other hand, recently received version 85 and will have to wait for the next update to try out the new features. Microsoft Edge gets the ability to generate unique passwords for the users
zanderthunder posted a topic in Software NewsMicrosoft is back to its regular schedule with Edge Dev builds, after a late release last week, and today's update brings the browser version up to number 80.0.334.2. As with most builds based on Chromium 80 so far, this one is light on new additions, and it mostly brings fixes and smaller improvements to the experience. It also still doesn't include support for ARM64, which debuted in the Canary channel last week. With that being said, there are a couple of new features, which include a setting to force tracking prevention to be set to Strict when the user is browsing in an InPrivate window: Added a right-click option to sort individual favorites folders by name from the Favorites management page. Added a new setting to always use Strict Tracking Prevention inside InPrivate windows. Aside from those additions, this release is all about fixes, and there's a lot of them. As usual, the list is split into fixes for reliability and for behavior. Here's what's new for reliability: Fixed a crash on launch. Fixed an issue where searching from the address bar sometimes crashes the browser. Fixed a SmartScreen crash when downloading certain items. Fixed an issue where selecting context menu items on certain favorites entries causes a browser crash. Fixed an issue where renaming a Collection sometimes crashes the Collections pane. Fixed an issue where Application Guard windows sometimes crash upon startup. Fixed an issue where navigation fails in Application Guard windows. Fixed an issue where closing tabs that contain websites that are blocked by SmartScreen sometimes causes a browser crash. Fixed an issue where deleted or edited favorites aren’t synced properly, causing the edit to be undone when it syncs back down. Fixed an issue where syncing gets stuck in the “Setting up sync” state on browser startup. Fixed an issue where processes that grow too large and stop working aren’t automatically fixed. Fixed an issue where sync sometimes fails after restoring tabs after a browser crash. Fixed an issue where large Collections aren’t properly exported to Word. Fixed an issue where exporting a Collection to Excel sometimes fails. Reduced the number of times a user needs to sign out and sign back into the browser in order to fix sync. There are also a number of behavior changes and fixes, including a change that will prevent macOS users from exporting Collections to Word or Excel. Here's the full list: Temporarily disabled the ability to export Collections to Word and Excel on Mac. Temporarily disabled one form of DRM support on ARM64, which may impact the ability to play certain DRM-protected videos. Fixed an issue where windows that are minimized when the browser is restarted aren’t restored properly. Fixed an issue where Netflix playback fails with error D7356. Fixed an issue where the space bar doesn’t work when typing in the address bar. Fixed an issue where the enter key doesn’t work when typing in the address bar. Fixed an issue where the Windows Hello prompt to log into a website with the user’s OS credentials sometimes shows in an infinite loop. Fixed an issue for users of work and school accounts where websites that try and fail to use the browser profile’s credentials to log in don’t subsequently allow the user to fall back and try the user’s OS credentials. Improved the way Collections export images to Word documents. Fixed an issue where items sometimes fail to be added to Collections. Fixed an issue where webpage contents sometimes render all black if Collections is enabled. Fixed an issue where adding certain images to Collections results in a card with a broken image. Fixed an issue where PWAs installed for one user on a machine sometimes can’t be launched by other users on the machine. Fixed an issue on Mac where feedback screenshots can’t be included when submitting feedback. Fixed an issue where link context menus don’t show all the options if they’re opened via the keyboard instead of the mouse. Fixed an issue where some websites that are pinned to the Task Bar launch new tabs instead of activating existing tabs when tabs with those websites already exist. Fixed an issue where open tabs aren’t properly imported from Chrome. Fixed an issue where the wrong icon appears on web notifications. Recently, Microsoft has started including a list of known issues with its release notes, and there's a few in this release, despite the lengthy lists of fixes. Here's what you need to be aware of: There are some issues where users with multiple audio output devices sometimes don’t get any sound from Edge. In one case, Edge becomes muted in the Windows Volume Mixer and unmuting it fixes it. In another, restarting the browser fixes it. At certain zoom levels, there is a noticeable line between the browser UI and the web contents. Last month, some users got a “Work” account automatically added to the browser that wasn’t removable. Although we recently enabled the ability for some users to remove this account, there’s still an issue where users who are signed into Windows with a work or school account may not be able to remove that account from the browser. Clicking a link on one virtual desktop currently opens a new tab in a window on a different virtual desktop if there’s no window open on the current desktop but there is on another. This is a regression from past behavior, which opened a new window on the current desktop. Jumplist entries are not consistent between the Start Menu and the Task Bar for some users. We believe this is due to the shortcut on the Start Menu not getting migrated properly after an Edge update and are working on a fix. Additionally, after getting the update for the new icon, there are still places on the Start Menu, for example when searching, that still show the old icon. Other places like the Task Bar may be able to be fixed by un-pinning and then re-pinning any Edge shortcuts that already exist there. Sometimes the browser will appear to not respond to any user input (clicking or scrolling in webpages doesn’t do anything, hovering over UI doesn’t make it change), but clicking on certain buttons still works (like the … menu). The cause of this is due to an error in the GPU process, and opening the browser task manager (right-click near the window minimize/maximize/close buttons or hit shift+esc on the keyboard) will open a window that will allow you to end the GPU process, which will fix the issue. This issue was inherited from upstream Chromium, and a fix for it just went in upstream, so the next Dev update should have it. The latest build should now be showing up if you check for updates from within Edge Dev, and these improvements should help make the Beta channel more stable when the update makes its way there. That should happen shortly before the current Beta release is promoted to the stable channel on January 15, marking the official launch of the new Chromium-based Edge. Source: This week's Edge Dev build is 80.0.334.2 and it focuses on fixes (via Neowin)