Jump to content

Search the Community

Showing results for tags 'edge chromium'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station


  • Drivers
  • Filesharing
    • BitTorrent
    • eDonkey & Direct Connect (DC)
    • NewsReaders (Usenet)
    • Other P2P Clients & Tools
  • Internet
    • Download Managers & FTP Clients
    • Messengers
    • Web Browsers
    • Other Internet Tools
  • Multimedia
    • Codecs & Converters
    • Image Viewers & Editors
    • Media Players
    • Other Multimedia Software
  • Security
    • Anti-Malware
    • Firewalls
    • Other Security Tools
  • System
    • Benchmarking & System Info
    • Customization
    • Defrag Tools
    • Disc & Registry Cleaners
    • Management Suites
    • Other System Tools
  • Other Apps
    • Burning & Imaging
    • Document Viewers & Editors
    • File Managers & Archivers
    • Miscellaneous Applications
  • Linux Distributions


  • General News
  • File Sharing News
  • Mobile News
  • Software News
  • Security & Privacy News
  • Technology News

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 12 results

  1. This week at its Ignite 2019 conference in Orlando, Microsoft announced the general availability date of its new Chromium-based Edge browser, which has been in public testing since April. Beginning on January 15, it will be considered generally available, meaning that it will start updating users to its new browser. Unfortunately, it's going to be missing a few key features. ARM64 support will be missing at launch, despite Microsoft having released its own ARM-powered PC just this week. You also won't find the new browser for Xbox One or HoloLens; and it probably goes without saying, but the newly-announced Linux version won't be available on January 15. Some app features won't be there either, including history syncing and extension syncing. To be clear though, these features, along with ARM64 support, won't be in the shipping version of the browser, but they could be in Canary and Dev channels by then. The reason for the lack of ARM64 support is a blocking bug that is exclusive to the ARM architecture. Microsoft did indeed plan to announce support for the chip architecture at its October 2 event alongside of the ARM-powered Surface Pro X, but it just wasn't ready, and it's still not ready. ARM64 support is definitely coming though, just in case anyone was worried. As for things like Xbox One and HoloLens, those are just lower priority, and it makes sense. The browser isn't used nearly as much on something like an Xbox. It's coming, but there's no specific timeline. I met with Edge CVP Chuck Friedman, and I did ask why the team chose to announce a GA date when things like ARM64 support, history syncing, and extension syncing aren't ready, and aren't going to be ready in time. It pretty much comes down to those features not being important enough. ARM64 PCs are still a tiny segment of the Windows 10 market, even with a brand new flagship ARM64 PC from Microsoft, the Surface Pro X. History and extension syncing are both important, but not as important as password syncing, which is already included in the browser. Beginning on January 15, users will start seeing the Edge Chromium browser showing up on their PCs. The back end for the updates will be Windows Update, so you'll pretty much get an app that installed over Legacy Edge. Eventually, there will be a Windows 10 feature update that removed Legacy Edge entirely, but there's no telling when that will be. Source: Microsoft's new Edge will ship without ARM64 support, history sync, and extension sync (via Neowin)
  2. Microsoft's Edge Chromium browser to ship in Windows 10 as soon as it's generally available Here at Microsoft's Ignite 2019 conference, the company announced the general availability date for its new Chromium-based Edge browser. The rebuilt Edge will be available on January 15. In fact, if you sign up for the Beta channel, you can get the release candidate right now. The next question is that of when the browser will actually ship with Windows 10, with many speculating that it might ship in 20H1 - which would be the first feature update after January 15 - or even 20H2, since 20H1 might RTM in December. As it turns out, neither of those theories are accurate, as the browser will start to be bundled with the OS right after the GA date. It's going to be a slow rollout though. We're not all going to wake up one day and find Legacy Edge replaced by the new Edge. That's how staged rollouts work though. There will be a small sample group that will get it first, and then that group will be expanded. As for new installations of Windows, the bits will be sent out to OEMs as soon as they're generally available. The point is that it doesn't require a Windows 10 feature update at all. The app can simply be bundled with the OS, and as we've seen, when Edge is installed from the production branch, it replaces Legacy Edge, or Edge Spartan. So if you buy a new PC next year, chances are that it will be running Edge Chromium out of the box. Source: Microsoft's Edge Chromium browser to ship in Windows 10 as soon as it's generally available (Neowin)
  3. Microsoft will be pushing out the new Edge via Windows Update to the majority of Windows 10 users In an article on how to stop it, Microsoft has revealed that they will be pushing out the Chromium-based Edge browser to the majority of Windows 10 users. Microsoft will be pushing out the update, replacing the old Edge, to all Windows 10 users on Windows 10 RS4 (April 2018 Update) and newer. This may of course cause compatability issues, and Microsoft is releasing a Blocker Toolkit for enterprise users to control the rollout. Microsoft writes: To help our customers become more secure and up-to-date, Microsoft will distribute Microsoft Edge (Chromium-based) through Automatic Updates for Windows 10 RS4 and newer. The Blocker Toolkit is intended for organizations that would like to block automatic delivery of Microsoft Edge (Chromium-based) to machines in environments where Automatic Updates is enabled. The Blocker Toolkit will not expire. For computers running Windows 10 RS4 and newer, the Blocker Toolkit prevents the machine from receiving Microsoft Edge (Chromium-based) via Automatic Updates. The Blocker Toolkit will not prevent users from manually installing Microsoft Edge (Chromium-based) from internet download, or from external media. Organizations do not need to deploy the Blocker Toolkit in environments managed with an update management solution such as Windows Server Update Services or System Center Configuration Manager. Organizations can use those products to fully manage deployment of updates released through Windows Update and Microsoft Update, including Microsoft Edge (Chromium-based), within their environment. The toolkit and more information can be found at Microsoft here. Source: Microsoft will be pushing out the new Edge via Windows Update to the majority of Windows 10 users (MSPoweruser)
  4. Microsoft is now accepting submissions for Edge Chromium extensions Developers can now submit their extensions for Microsoft's new Chromium-based Edge browser, the company announced today. The new Edge is set for launch on January 15, so Microsoft wants to have a robust Edge Addons store, also saying that if you're a developer and you have a Chromium extension, it likely won't take any additional work to port it to Edge. If you have created a new Edge Legacy extension, the last day to submit it will be tomorrow, December 17. It makes sense though, since beginning on January 15, Microsoft is going to start moving people to Edge Chromium. The migration of 900 million Windows 10 users is going to take some time, but it's clear that EdgeHTML is a thing of the past. Those that already have Edge Legacy extensions on the existing store will want to submit Edge Chromium extensions as soon as possible. Microsoft noted in the blog post today that if there's no Chromium extension available, then the extension won't migrate when the customer is upgraded. And since Edge Chromium currently doesn't have any kind of extension syncing, your customer will have to manually obtain that extension again. If you want to submit an extension for Edge Chromium, you can do so at the Partner Center Developer Dashboard. Source: Microsoft is now accepting submissions for Edge Chromium extensions (Neowin)
  5. Microsoft 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)
  6. Windows 10's built-in Edge browser (now informally called Legacy Edge) has always natively supported ARM64, or at least since Windows on ARM was a thing. But up until now, those testing out Microsoft's new Chromium-based Edge browser haven't been able to run it natively on ARM; they could only get the x86 version running in emulation. Now, testers can finally use native ARM64 Edge Chromium. While most 32-bit Intel apps run fine in virtualization on ARM processors, browsers don't. Browsers generate code in real-time, making it hard to cache. That means that for Windows on ARM to be truly viable, there needs to be native browsers. Up until now, the only web browsers that ran native on ARM64 PCs were Edge Spartan and Firefox, the latter of which was announced back in December. But while native Firefox was announced at the same event as Chromium, Firefox was available for testing in January. Edge is now the first Chromium-based browser to have a shipping version running on native ARM64, albeit not from the stable channel. I've been told that Chrome won't be coming until next year. For now, ARM64 Edge Chromium is only available in the Canary channel. It will be coming to Dev and Beta channels soon; however, it won't be in the stable channel when it's generally available on January 15. Source: Microsoft's Chromium-powered Edge browser is now available for ARM64 PCs (via Neowin)
  7. It was almost a year ago that Microsoft announced that it's rebuilding its Edge browser from Google's open-source Chromium project. Today at its Ignite 2019 conference in Orlando, it finally announced that general availability is slated for January 15, and the release candidate is coming today. Well now, that release candidate is finally available from the Beta channel. The version number is 79.0.309.11; Dev and Canary are on the newer Chromium 80, which is to be expected given that they're updated more frequently. In fact, you can expect Edge Beta to move to Chromium 80 right before Edge 79 is released to production. Another announcement that was made recently was that Edge is getting a new logo, as you can see from the image above. Interestingly enough, this release candidate does not have the new icon, although we should be seeing it in builds later on this week, probably alongside new Canary and Dev builds that have it. But if you want to check out the release candidate now, you can download it here. Source: Microsoft's Edge Chromium release candidate is now available in the Beta channel (via Neowin)
  8. Microsoft's new Edge browser, based on the Chromium project, is set to release on January 15, and when it does, it'll be missing a few features, such as history syncing and extension syncing. Another thing that'll be missing, for those using the current version of Edge, is the ability to set tabs aside to use later. But if you're using this feature in the current version of Edge. As spotted by Techdows, if you install the stable version of Microsoft Edge - which is only available through unofficial methods - on Windows 10, your tabs set aside will be available as favorites. Upon launching the updated browser, when you right-click one of the tabs at the top of the screen, there'll be a menu item saying you can find your tabs set aside in Favorites. There, you can find them in a dedicated folder to tabs set aside, with each set of tabs grouped into a different folder. Since the new version of Edge will be added to Windows 10 as soon as it's generally available, displacing the current version, it makes sense for user content to be preserved somehow. On the favorites page, you'll also see a message saying you can't currently set tabs aside in Edge. Microsoft has talked about the possibility of bringing some features over from the current version of Edge, and during a session at Build this year, no guarantee was given that the ability to set tabs aside would be among them. However, the text on this page could suggest it is happening at some point. It's worth noting that the Canary and Dev channels of the new Edge have an interesting new feature called Collections, which can gather websites, images, and notes into user-created groups, which isn't too far off from how setting tabs aside worked. With the ability to add all the current tabs to a collection, for instance, the functionality would be nearly identical to how it works in the current version of the browser. It could end up being something completely different, though. Source: The new Edge will seemingly import tabs set aside from the legacy version as favorites (via Neowin)
  9. Microsoft usually only provides detailed changelogs for Edge builds in the Dev channel, but today, the company has changed things up with a forum post dedicated to the latest Canary build, which carries number 80.0.319.0. The company says it's still determining if it will keep publishing daily changelog posts for Canary builds and is gauging interest in them. To kick things off, Microsoft posted the changelog in a very cryptic way, but user Cameron_Bush managed to decipher the text. Despite being on a daily release cycle, there's quite a lot that's new in the build, including the ability to import browsing history from Firefox, as well as support for extensions that change the browser's appearance from the Chrome Web Store - though in our testing this doesn't seem to be referring to themes. Here's what's new: Created an easier way to add a favorite. Opening collections items can now be done via the keyboard. Downloads now warn you of dangerous items. Extensions now show the publisher's information. New options for organising installed apps. Additional zoom options are now available. Microphone or camera use is now shown in the address bar. Extensions that modify the browser's appearance can now be installed from the chrome web store. Opening apps can now be done via the keyboard. Firefox history can now be imported. Just like with Dev builds, Microsoft is providing two lists of fixes and improvements, one for behavior and one for reliability. Here's the list of reliability fixes: Favorites opened via touchscreen no longer crash the browser. Intranet sites no longer hang when loading. Reopening windows no longer fails. Several application guard crashes have been fixed. Tracking prevention exceptions can now be added without the settings page occasionally crashing. Windows can no longer be created offscreen. Improved the password import success rate. New tabs opened quickly now always succeed. Downloads no longer fail if you quickly close the tab. Opening InPrivate windows no longer fails. Windows closed quickly now stay closed. Saving PDF documents no longer crashes the tab. Finally, here are the behavior changes in this release, which include more frequent checks for updates to the browser: Temporarily removed the new PDF toolbar. Organising extensions can now be done by individual sources like the web store or unpacked files. Standard form controls are now accessible. History items are spaced better. Intranet searches now appear in the address bar. Performing searches from the address bar now saves that data to the cloud so it can sync to other devices. Wording on error pages has been improved. Intranet search performance has been improved. Tabs created offscreen can now be switched to. History items cleared with the clear browsing data dialog are now properly deleted from the current session. Images on certain webpages are no longer squished. Edge now checks for updates more frequently. The latest build should now be rolling out to everyone in the Canary channel, and these improvements should be available to Insiders in the Dev channel sometime next week. Source: Today's Edge Canary build lets users import browsing history from Firefox (via Neowin)
  10. Edge, both in its UWP form and the new Chromium-based version, has supported dark mode for some time, but it only applies to the browser interface itself, and not web content. However, as spotted by eagle-eyed Reddit user Leopeva64-2 (via OnMSFT), Microsoft has added a flag in the latest Canary build of Edge that lets users force web content to be displayed in dark mode. Many websites (like Neowin) already offer a built-in dark theme, and there's also a number of extensions that can force websites to display in dark mode, but it's still interesting to see the feature being implemented into the browser itself. Currently, the setting is hidden in the flags page and disabled by default, but it could eventually be added to the main settings page. Despite being an early implementation, it already offers a variety of options for forcing dark mode, which could help adjust the effect to be more pleasant on the eyes. These include HSL-, RGB-, CIELAB-based inversion, selective image inversion, and so on. Of course, it's still a workaround for websites that don't support it, and it won't be perfect. If you're interested in enabling the feature, you'll need to have Edge version 80.0.317.1 and go to edge://flags to find the "Force Dark Mode for Web Contents" flag. Source: Latest Edge Canary build lets you enable dark mode for websites (via Neowin)
  11. Microsoft will be releasing the final version of the new Chromium-based Edge browser on the 15th of January and it appears Microsoft is testing dropping the beta label on the icon for the browser. WindowsUnited reports that on a number of installations of the beta build of the browser the Beta label has disappeared, suggesting Microsoft is testing some back-end server-side changes in readiness of the final release on the 15th. Microsoft will be pushing out the new Chromium-based Edge browser, replacing the EdgeHTML-powered version for all Windows 10 users. Microsoft says the two browsers should now work identically, but it is still possible for enterprise users to block the roll-out, or to run both old and new browser side by side. Have any of our readers noticed their Betal label disappearing? Let us know below. Source
  12. Most expected this was coming, not this soon. Google got away and backed its decision to say new Edge Chromium as an unsupported browser on its sites such as Duo for web, Meet and YouTube when it was in development, once the Edge stable version has been released the Search engine giant has started to show its true colors to Microsoft who is actively contributing to Chromium. The company is now aggressively prompting Edge users on its websites such as Google Search, Google News, Google Docs and Google Translate to “Switch to the Chrome” browser. It all started with Chrome Web Store where Google began to recommend Chrome to use extensions securely. While a normal user may not understand and treat this as an ad, non-Chrome and classic Edge users will definitely find the ones appearing now on Google properties as pop-up ads. While folks over at MSPU found this on the search engine giant home page, we noticed they are doing this on their News, Docs and Translate websites as well. We’ve even got an unsupported browser warning for Google Drive albeit for Edge Canary but not in the release version. New Edge users don’t need to jump to Chrome as Microsoft has covered Edge browser which comes with automatic updates with alternate features for Safebrowsing, Google Translate, and Adblocker Chromium Edge too has got Google’s ad blocker enabled in the browser if it thinks Chrome blocks ads on websites that show abusive ads. While Chrome protects its users when they visit dangerous and malware websites via the Safe Browsing feature, new Edge has Microsoft Defender Smartscreen and Potential unwanted Application download protection integrated to guard its users. Talking about updates, Edge Chromium stable too now gets updated regularly like Chrome. If Chrome auto translates pages with its Translate service, new Edge has Microsoft Translator integrated to translate the pages. Google soon will load all websites with slogans to switch to Chrome when it detects you’re using a new Edge browser. Get accustomed to them or ignore or switch to Chrome (will you do that?) or another browser or start using search engines such as Bing, DuckDuck Go and browsers such as Firefox and Vivaldi to get a reprieve from these ads which also protects your privacy to some extent. Source
  • Create New...