Jump to content

Search the Community

Showing results for tags 'edge'.

More search options

  • 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

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 37 results

  1. Collections is now live in Edge Dev and Edge Canary Today, Microsoft announced that Collections is now enabled by default in the Edge Dev and Canary channels. The feature was announced at Build this year, and then it made its debut back in August. It's been hidden behind a flag though, up until now. Collections is exactly what it sounds like. It allows you to collect images, text, links, and so on from around the web and group them into categories. You can use it for shopping, research, and plenty of other use cases. In the blog post, Microsoft also noted some improvements that it made since the feature was first introduced. Collections now sync between devices, even though you still can't sync your browser history. There's also now an option to open all of the links in a Collection, and they're easier to share as well. Finally, support for dark theme was added. Again, this feature is available now in the Canary and Dev branches. It will likely make its way to the Beta branch whenever the next update is, but it won't be in the release build when Edge Chromium is released to the general public on January 15. It will probably be in the update after that. Source: Collections is now live in Edge Dev and Edge Canary (Neowin)
  2. Microsoft details tracking prevention improvements in the new Edge browser A while back, Microsoft announced that the new Chromium-based Edge browser was getting built-in tracking prevention, a feature that helped users manage how their activity on the web is tracked. It's been some time since then, and the company has detailed some of the improvements made to the experience with Edge version 79. This is the version that's currently in the Beta channel and set to be the first generally available version of the new browser. Microsoft said its goal with the new improvements was to simultaneously block more kinds of trackers while also ensuring as much compatibility as possible with the web. Blocking too many trackers can cause some sites to break, so a certain balance is necessary. Microsoft says it figured out a way to do this by measuring the user's engagement with organizations, so tracking prevention can be less strict when the user has a clear relationship with a website or organization. This helps users achieve better compatibility with websites they care about most, while blocking more trackers on websites they don't visit as often. Microsoft says that, by enabling this capability, called Org Engagement Mitigation, it actually blocked 25% more trackers on average, so the end result should actually be better for privacy-conscious users. However, if you really don't want any trackers, you'll be happy to know that this feature is only enabled for users that use the Balanced setting for tracking prevention in Edge. Users who opt into Strict mode will still block the maximum number of trackers regardless of their site and organization engagement. For InPrivate mode, Edge 78 initially set the tracking prevention mode to Strict at all times, but that's changing now since users were seeing some sites breaking because of it. InPrivate windows will now follow the same setting as regular browsing, but Microsoft is testing a new toggle in the Canary and Dev channels to allow users to continue using Strict mode for InPrivate browsing. For users who want to know more about which trackers Edge has blocked, there's also now a new page to view a list of blocked trackers and how many times each tracker was blocked. The list can be found in edge://settings/privacy/blockedTrackers. Source: Microsoft details tracking prevention improvements in the new Edge browser (Neowin)
  3. FAQ: Microsoft sharpens Edge The company's new Chromium-based browser will officially arrive in final form in January. Here's what you need to know about it ahead of the rollout. Urupong Getty / Microsoft Microsoft will release the polished version of its overhauled Edge browser in less than 10 weeks. While the new Edge has been built using technologies from a fierce rival - Google, which controls two-thirds of the global user share - it's also an attempt by Redmond to resurrect its own browser fortunes. Edge, the old Edge, the browser that debuted alongside Windows 10 four years ago, was roundly rejected by users. Now, Microsoft wants a second chance. But will customers grant the company a mulligan? We don't know. But we do know answers to a variety of other important questions about Edge Part Deux. In fact, we have more answers than space, so we'll revisit second-chance Edge before that January 2020, roll-out arrives. When will Microsoft ship a polished version of Edge? Jan. 15, 2020 will be the date of "general availability," or GA, a Microsoft term for a production-quality release. Chrome calls this "Stable," a label that Microsoft has also used, at times alongside GA. What version of Chromium will the first Stable version of Edge be based on? Version 79. Chromium numbers its versions as M78, M79, M80 and so on. Those numbers correspond to the Chrome identifiers. Thus, M79 was wrapped up Oct. 17 and promoted to Chrome Beta 79 Oct. 31; it's slated to reach release as Chrome Stable 79 (or just Chrome 79) on Dec. 10. Why does that Jan. 15 date sound familiar? The date you're probably thinking of is Jan. 14, 2020, the end of support for Windows 7 and the retirement of the decade-old OS. More on Windows 7, Edge and the two dates a bit later. What happens to the old Edge - what Microsoft's been called "legacy Edge" but which cynics might dub "dull Edge" - when Microsoft releases the Chromium Edge, and we download and deploy it? Ooooh. Good question. Microsoft will "hide" the old Edge when the new Edge is installed. "Installing the Stable channel of the next version of Microsoft Edge at system-level will cause the current version of Microsoft Edge to be hidden," Edge documentation stated. The old Edge isn't being scrubbed from the device because Microsoft will allow IT admins - not end users - to retain the earlier Edge and run that alongside Chromium Edge. Not surprisingly, group policies are involved in this. (For basic instruction on how to do this, check out this document.) Will Chromium Edge force-change the browser default to itself? No. That's a major change - seismic, really - from the hijinks Microsoft pulled with Edge when the browser debuted inside Windows 10 in mid-2015. In a fit of insecurity, Microsoft made Edge the default, then added insult to injury by requiring users to jump through a Hula factory full of hoops to name a rival as the default instead. Later, Microsoft continued the shenanigans by reverting to Edge-as-default whenever Windows 10 received a new feature upgrade. That's not going to happen this time, Microsoft said. "If you have set a different browser as your default, we do not assume ourselves as the default. We keep that default, we do not touch that," said Colleen Williams, a senior program manager on the Edge team, during a presentation last week at Microsoft's Ignite conference. Only if old-Edge was the Windows 10 default will Chromium-Edge end up taking that spot. (Because Edge is new to several OSes, including Windows 7 and macOS, Chromium Edge will probably not be the default on Jan. 15.) How often will Microsoft upgrade the new Edge? Every six weeks. That's what Microsoft says now. Old-Edge, of course, was refreshed just twice annually, in each of the two feature upgrades Microsoft issues each year. But new Edge, like Chrome and other niche browsers built atop Chromium, will update about four times more often. Earlier this year, other Microsoft managers told users not to expect a cadence like Chrome's. "We're not beholden to six weeks or four weeks or something like that," said Chris Heilmann in June. Still unclear, however: How closely, if at all, Edge's upgrades will sync with Chrome's. The first Edge release won't be synchronized at all. Chrome 79 is currently scheduled to release on Dec. 10, or five weeks before Edge 79. What about security updates As does Chrome, Edge will patch vulnerabilities in each major upgrade. The latest version of Chrome, v.78, for example, contained 37 fixes. But because Google typically patches Chrome one or more times in between each upgrade, Edge users should expect the same from Microsoft. The company confirmed that, more or less, with the line, "Security and compatibility updates will be shipped as needed" in Edge's documentation. Again, as an example, Chrome 78, which was released Oct. 22, or nearly three weeks ago, has been patched twice since then: once on Oct. 31 with two fixes and again on Nov. 6 with four. Exactly when - in relation to Chrome - Microsoft will patch Edge is another unanswered question. Once Edge has gone Stable, will Microsoft release its security-only updates on the same day as Google does Chrome's? Or later. And if later, how much later? Those are important queries because if patching is not synchronized, it may be possible for criminals to gain insight into flaws that have been fixed in Chrome (and Chromium) but not yet patched in Edge, then use the knowledge to attack the latter browser. Now that Edge includes IE mode, will Microsoft dump the IE11 browser like a penny stock gone bad? At the Ignite conference, Microsoft's Williams said, "We get that question a lot." Her answer seemed clear-cut. "IE11 is not going anywhere," she asserted. "The introduction of IE mode does not mean that we change support for IE11. That continues to be supported on the lifecycle of the OS on which it ships." (In anther presentation at Ignite, Steve Rugh, a principal program manager, said, "Currently, there's not a plan to do that" when asked by an audience member whether Microsoft would remove IE11 from Windows.) According to those operating system life cycles, IE11 is to be supported on, say, Windows 10, forever - since Windows 10 is to evolve a time or two each year but will never be replaced. However, Computerworld has maintained that the life of the separate, stand-alone application known as IE11 will come to an end. Retaining IE11, for example, in Windows 10 when the OS also boasts a browser (Edge) that offers an integrated IE mode, smacks of unnecessary redundancy. If IE mode performs as Microsoft promises, what purpose does a separate IE11 serve? Even Windows 7 - set to reach support expiration in two months - benefits from Edge's IE mode. Microsoft's offer of extending Windows 7 security support for up to three more years - until January 2023 - meant IE was still required. But shouldn't IE mode suffice? Microsoft may say today that it will let IE11 hang around, but there's nothing to stop the company - nor would it be remarkable considering past moves, like shortening several IE versions' support by years - from announcing a change tomorrow. (Ironically, the fact that Microsoft employees invariably use very similar phrasing to describe IE11's support, as if it was rote call and response, reduces confidence in the this-browser-will-live-forever pledge.) Computerworld will stick with its forecast that Microsoft will eliminate IE11 and tell users to rely solely on IE mode in Edge. Maintaining two identical browsers simply makes no sense. How long will Microsoft support each version of Edge? Until the next Stable build launches. At Ignite, Microsoft said it will support only the "latest" Stable and Beta channel releases. Once a build ages out, replaced by a newer Stable or Beta, the former falls off support. This is exactly how rival browsers, notably Chrome and Firefox, treat support. Here's an example: Microsoft launches Edge 79 on Jan. 15, 2020. The next Edge, version 80, is slated to release Feb. 26 (that's six weeks from Jan. 15). From Jan. 15 to Feb. 26, Microsoft supports Edge 79. When that's replaced by 80, 79's support expires and Microsoft starts supporting 80. On What operating systems will Edge run? In general terms, Windows and macOS. A version for Linux will be "available in the future," Microsoft has said, but it has not provided details or a timetable. More specifically, Edge will run on every supported version of Windows and Windows Server, including Windows 7 (now and, of course, even after 7's retirement), Windows 8.1, Windows 10 and Windows Server 2008 R2 and later. Interestingly, the Windows 10 support for Edge extends to all flavors of that OS, including Windows 10 S Mode and Windows 10 LTSC (Long-term Servicing Channel). The latter, a special edition that receives only security updates during its lifetime - thus, its at-start feature set will not change - is the most intriguing on the list. Microsoft never packaged the old-Edge with Windows 10 LTSC, only IE11, because it argued that Edge needed to evolve and that feature evolution contradicted the premise of the unchanging operating system. Apparently, the fact that full-Chromium Edge will refresh every six weeks - as opposed to the every-six-month cadence of old-Edge - meant that a browser that changes constantly is a better fit to LTSC than one that only changes occasionally. Weird. It's unknown how Microsoft will verbally square the circle here. What's the top enterprise feature in Chromium Edge? There are several to choose from, but we point to IE mode. The two-browser solution Microsoft introduced in 2015 was clunky: sites designated to open in IE automatically launched IE11 - the full browser - yanking users out of Edge and dropping them into the vastly-different UI of IE11. Worse for Microsoft, the dual - and dueling - browsers motivated customers to ignore Edge. If employees required two browsers, one for legacy sites (IE11) and another for all the rest, why not select a more web-compatible browser as the second? There was no reason, other than loyalty to Microsoft, to stick with Edge. Instead, enterprises skewed toward Chrome. Instead, Microsoft has managed to keep sites and apps requiring IE on a tab inside new-Edge. The result? "This allows you to have one browser for backwards compatibility. And a modern browser so you can stay in one spot," said Williams. Although it's still unclear how IE mode works on a technical level - Does it emulate IE inside Edge? Does it simply display the content there, but IE11 renders it? Microsoft hasn't said - the usage mechanism is very much like what's current in Windows 10. Admins create a list - called the Enterprise Mode Site list - of websites and web apps that should be rendered by Internet Explorer or alternately instruct all intranet sites to be drawn by IE, then set some group policies. Does everyone get IE mode in Edge? No. Only Enterprise and Education licenses - the former is the most expensive commercial license - are able to use IE mode. And the only way to enable and manage it are through group policies, putting the mode's management almost exclusively in the hands of IT administrators. Source: FAQ: Microsoft sharpens Edge (Computerworld - Gregg Keizer)
  4. Microsoft's Edge browser is officially coming to Linux soon Back in May at Microsoft's Build 2019 developer conference, the company teased that its new Chromium-based Edge browser might be coming to Linux. At the time, public testing of the new browser was in its infancy, so there were a lot of uncertainties. In fact, back then, we didn't even have a Beta channel, and there weren't any builds for macOS yet, or older versions of Windows. Microsoft has teased Edge coming to Linux a couple of times since then, and today, it's finally official. During its State of the Browser session at its Ignite 2019 conference in Orlando, the Redmond firm finally said that there's a version of Edge coming to Linux. As for the timeline, it's the most familiar for those that follow Microsoft: it's coming soon. The Edge team rarely provides actual details for when the browser will hit a major milestone, so it was a bit surprising that it actually announced a general availability date today. Edge Chromium will be available for Windows and macOS beginning on January 15. While it's possible that the Linux variant could be in the Canary and Dev channels by then, it won't be generally available, just like the ARM64 flavor for Windows 10. Source: Microsoft's Edge browser is officially coming to Linux soon (Neowin)
  5. New Edge will bring captions and improved inking for web apps As discovered by Windowslatest, new developments are being made to Chromium-based edge, specifically: support for native captions and improved inkling support for web apps. In a post on Github, Microsoft confirmed that it’s adding “Native Styling Support’ for WebVTT captions on Windows 10 so that webpages in Chromium support Windows’ caption Settings. The change will allow users to style WebVTT captions –Web Video Text Tracks format– from the Windows 10 Settings app. Captions are customisable by many parameters, including transparency, style, size, effects and background colour. The settings for the appearance of the captions are discrete- any changes made will be independent of the overall site layout. Microsoft described the change as follows: For web video content that uses the WebVTT standard to include a caption payload for HTML5 content, this change will apply the caption styling preferences the user explicitly sets in the OS Settings app on Windows 10 or macOS. The next change mentioned on Github resolves around delivering a superior inking experience, which can be achieved by the use of low-latency ink. With the change, web apps will be able to successfully achieve latency parity with Windows 10 and ChromeOS. Operating system compositors typically introduce a frame of latency in order to compose all of the windows together. During this frame of latency, input may be delivered to an application, but that input has no chance of being displayed to the user until the next frame that the system composes, due to this pipelining. Download the new Chromium Edge here. Source: New Edge will bring captions and improved inking for web apps (MSPoweruser)
  6. Microsoft provides group policies for enterprise control of 'full-Chromium' Edge updates IT admins will be able to use the policies to manage, deploy and update the new browser to their corporate workforce. Thinkstock Microsoft has published the template and documentation that will be required to manage updates of the not-yet-finalized "full-Chromium" Edge browser, making good on a promise of earlier this summer. When Microsoft first pounded the Edge-for-enterprise drum in June, the Redmond, Wash. developer unveiled a preliminary catalog of group policies that IT administrators would use to deploy, customize and maintain the browser. Omitted, though, were GPOs (group policy objects) and an administrative template for wrangling updates. "Policies for managing updates aren't included; those will be in a separate administrative template file," Sean Lyndersay, a group program manager on the Edge team, wrote in a June 14 post to a Microsoft blog. Unlike previous Microsoft browsers - Internet Explorer (IE) and the original Edge, the latter powered by Microsoft's own technologies - the Edge built from the Google-dominated Chromium open-source project will be updated on a much faster six-to-eight-week cadence, just as is Chrome. Microsoft has severed the link between browser and OS feature updates. Enterprises that want to test and verify that each update works as expected need a way to block the native update mechanism. That's where these new GPOs come into play. The update-related group policies can be found in the full-Chromium Edge's online documentation. They require version 77 or later of Edge; the Dev 77 build was released last month, while Beta 77 launched this week. The administrative template - msedgeupdate.admx - to manage Edge updates can be downloaded from this landing page; it is one of the two templates collected in the MicrosoftEdgePolicyTemplates.zip file. (For those unfamiliar with using Windows' group policies, get-started instructions for the Edge templates can be found under the heading 1. Download and install the Microsoft Edge administrative template on this support page.) Because an organization's administrators will probably want to restrict employees' browser choices - to, for instance, keep everyone on the same version for support reasons - the GPOs allow for blocking updates of specific builds, like Canary, Dev and Beta - as well as preventing workers from manually refreshing the browser. Other GPOs let IT set specific systems with an update override, so that, say, a piloting team has access to Dev and Beta when everyone else does not. Still other GPOs set a value for the minimum number of minutes between automatic update checks - the default is 10 hours - and bar updates during office hours so as not to interrupt work. The GPOs control how Edge's native update service operates - the service that deals out upgrades to unmanaged machines - but Microsoft pledged that enterprise-grade platforms would also be supported by the browser. Deployment and configuration integrations with Microsoft's Intune and System Center Configuration Manager (SCCM), for example, are on the roadmap, though sans timelines. The browser will also be offered in MSI (for Windows) and PKG (macOS) installation formats for distribution by an organization's IT staff. The list of all Edge GPOs as of July 22 (other than those for updates) can be found here, and the browser's in-enterprise guidance begins here. Microsoft Microsoft has posted the administrative template for managing Edge's updates using group policies configured by IT. If this policy were enabled, the target Windows PC would be able to receive Beta channel updates. Source: Microsoft provides group policies for enterprise control of 'full-Chromium' Edge updates (Computerworld - Gregg Keizer)
  7. Microsoft is asking Windows Insiders to schedule an anonymous call with Microsoft developers to discuss their experiences using OneNote, Outlook, or the Edge browser. These requests are being shown in notifications displayed on the desktop from the Feedback Hub. While using the latest Windows 10 Insider 20H1 build 18941, a Feedback Hub notification was displayed titled "Let's talk! Scan QR Code" that stated "Microsoft Engineer has a question for you: Talk to Microsoft engineers about your recent experiences using OneNote, Outlook, or Edge browser. See available time: https://aka.ms/InsiderNinjaCat. Schedule a call notification When you click on the notification, you will be brought to a Feedback Hub entry that contains the same information. While it does prompt you to leave a comment, Windows users should instead visit the listed URL, which in this case is https://aka.ms/InsiderNinjaCat. Feedback Hub Entry If you browse to https://aka.ms/InsiderNinjaCat, you will be brought to a Microsoft Research page that asks you to schedule an anonymous call with the Microsoft engineering team to discuss "your recent experiences with OneNote, Outlook, or Edge browser". This call will be used to get feedback from Microsoft customers. "We gather customer feedback through multiple channels such as the Windows Feedback Hub. We also like to talk directly customers - and that’s what our online user research sessions are all about. They provide an exciting opportunity to connect with the engineers who design and build our products. Hearing from you early in the development cycle helps our engineers make changes to our products and test them before release. Early customer interactions ensure we hit the mark with features. The time you spend with us today can improve our products for users around the world." Microsoft is currently scheduling calls on 7/30/2019 between 9:30 AM - 11:30 AM PDT. The page further states that the calls will not be recorded, it is completely anonymous, and each call should take approximately 5 - 10 minutes, but may go longer if necessary. "Each 1:1 conversation is expected to run 5-10 minutes, but may be longer if there is more to discuss. We are not recording or storing the content of this call." In April 2019, Microsoft had asked users to call in and discuss their experience using the Windows 10 taskbar. Source
  8. Microsoft tells enterprises to be on Edge The company has begun telling companies about a variety of corporate features that have been baked into the browser, which is built on underpinnings from Google's Chromium. Microsoft / Google / Vijay Kumar / Getty Images Microsoft on Wednesday kicked off an Edge-is-for-enterprise effort, detailing the corporate features that have been baked into the under-construction browser so far and urging business users to give Edge a go. "The Dev Channel now has enterprise features enabled by default and is ready for evaluation and supported by detailed deployment and configuration documentation," said the browser's makers in a post to a Microsoft blog. "We are also offering full support for deployment in pilot and production environments through our commercial support channels." There are currently two versions, or builds, of Edge available to Windows and macOS users: Canary and Dev. The former is a rough build updated daily, while the latter is somewhat more reliable and stable, and updated weekly. Microsoft pushed enterprise IT administrators - and users - to try Dev. (A Beta build will eventually appear, but Microsoft now says it will "be available in the coming months," implying later rather than sooner.) IT gets more GPOs, ability to block updates In a special enterprise-focused section of the Edge Insider site, Microsoft has posted a .zip-format file that contains all the files - including ADMX and ADML files, and an HTML document - for using group policies on Windows and macOS machines to configure Edge in a managed environment. Last month, Microsoft had previewed those same files and most of the group policies. It wasn't easy to find the files, though, since Microsoft had hidden them in a post on the Insider forum. The current collection of group policy objects (GPOs) also includes those for managing Edge updates, something missing from the bunch previewed in June. One update-related policy, UpdateDefault, for example, lets administrators specify whether and how workers' copies of Edge use the Microsoft Edge Update service, a spin-off of the updater that handles Office. Policy configurations include disabling updates entirely, allowing manual updates and offering only periodic background updates. Other policies can be set so that some or all users are allowed to, for instance, update the beta and stable channel builds of the browser, but not the rougher dev and canary versions. "Customers will be able to control the flow of updates, either by leveraging our general updating mechanisms and using policies to pause updates at a particular version while testing compatibility with a small set of pilot users, or by using the provided offline installers (MSIs and PKGs) to push updates directly to their managed devices on their own schedule," Microsoft said in the Tuesday blog post. A list of all currently-supported group policies for full-Chromium Edge is available on this support site. The update-related policies are listed separately here. Microsoft has yet to integrate Edge deployment and management with its own Intune mobile device management platform - or third-party substitutes - but will, the company said. System Center Configuration Manager (SCCM) can be used to deploy the new browser, but like Intune, cannot currently configure Edge. Again, Microsoft pledged that SCCM - widely used in enterprise - would handle such chores at some future date. IE..., it's alive! Two months ago, when Microsoft showed off the new "full-Chromium" Edge - that name reflecting the browser's adoption of foundational technologies from the Google-centric Chromium open-source project - the firm touted a new Internet Explorer (IE) mode. Unlike the dual-browser approach taken by Windows 10 since 2015, the IE mode would, Microsoft said, "seamlessly render legacy IE-only content in high fidelity inside of Microsoft Edge." Rather than open a second browser - IE11 on Windows 10 - when encountering a legacy website or app that required the ancient application, Edge will render IE content so that it is "visually like it's just a part of the next Microsoft Edge, providing users with the latest UI (user interface)." IE mode is now ready to try and test in the Dev build on Windows. Because IE-inside-Edge relies on Enterprise Mode and the Enterprise Mode Site List - as does IE11 and old-Edge - IT can designate what sites are drawn by IE and which by Edge. Several group policies also allow IT administrators to customize workers' experiences. The InternetExplorerIntegrationLevel policy, for instance, lets admins choose to open IE11 (or not) when the employee calls up an old-school site or app. Microsoft has published documentation on using IE mode inside full-Chromium Edge here. (An interesting side note in the documentation referenced above: A short FAQ at its end includes the query, "Will IE mode replace Internet Explorer 11?" without actually answering the question. The closest Microsoft comes is when it says, "Internet Explorer is still a component of Windows..." with emphasis added by Computerworld. The word "still" suggests the current condition is not permanent, and that Microsoft will eventually eliminate the stand-alone IE11 and tell customers that their only option is to use Edge and its IE mode.) Past, present and future For the first time, Microsoft talked roadmap, albeit in general terms, to Edge's path in the enterprise. Trumpeted features, including IE mode and 180+ group policies, that are already in place were joined with several - including the unified search it has pushed for Windows 10, as well as a corporate-focused new tab page that will integrate Office 365 - that have not yet rolled out in their entirety. The Edge team referred to how it plans to deploy the second group of new features with the phrase "controlled rollout," reminiscent of the "controlled feature rollout" (CFR) phrase and acronym unveiled by Windows 10's makers this month. As in Windows 10, the intent seems to be to release Edge previews that will include off-by-default features that will be, assuming everything works as expected, switched "on" at some later date. Each feature will first be tested with a small subgroup; as bugs are uncovered and quashed, and Microsoft becomes convinced the feature works as intended without significant negative side effects, others will be added to the test pool. At some point, presumably, everyone has it enabled by default. Future features - the roadmap didn't bother with dates - range from the already-mentioned Intune and SCCM support for deployment and configuration to Information Protection on Windows 10. Even with the truncated list of features, Microsoft encouraged commercial customers to get going. "We believe that with today's announcement, the enterprise feature set is complete enough for most companies to start evaluations and pilots," the Edge team wrote. Microsoft still has not laid out a timetable for finalizing Edge. While the mid-January retirement of Windows 7 would argue that the deadline should be soon - why craft Edge to work on that OS when the OS itself won't be supported? - at this point it's clear that Microsoft interest in the 2009 operating system is only to support corporate customers who pony up for the "Extended Security Updates" (ESR) available through January 2023. Microsoft Microsoft's enterprise roadmap for 'full-Chromium' Edge may be rough, but the developer argued that there was enough there there to start piloting the new browser. Source: Microsoft tells enterprises to be on Edge (Computerworld - Gregg Keizer)
  9. Microsoft previews 'chromified' Edge's group policies to win enterprise approval Hoping to catch the interest of IT admins, Microsoft is offering a sneak peek of group policies they could use to manage the still-under-development "full-Chromium" Edge. Microsoft / Google / Vijay Kumar / Getty Images Microsoft has unveiled a preliminary catalog of group policies for managing the still-under-development "full-Chromium" Edge, giving IT admins a glimpse at what they will be working with if they adopt the browser. "We're still working on the list, but I'd like to share an early preview of the management policies we are working on for the new version of Microsoft Edge," Sean Lyndersay, a group program manager on the Edge team, wrote in a June 14 post to the Insider online forum. An attached file in .zip format contained ADMX and ADML files - the two required to implement group policies on a Windows device - and an HTML document that lists and describes the policies on Windows and macOS machines. "This is a work in progress," cautioned Lyndersay. "The list will change between now and our final release, with policies being added, removed or changed based on feedback." Microsoft announced in December 2018 that it was dumping its own technologies, notably rendering and JavaScript engines, and would instead take those from Chromium, the Google-centric, open-source project that feeds into Chrome and some lesser browsers. The revamping of Edge - which is to result in what Computerworld has called "full-Chromium Edge" - does not have a timetable, although with Windows 7's retirement looming in six months, and Edge to run on that edition as well as Windows 10, Windows 8.1 and macOS, one would think the browser will ship before year's end. While Microsoft has trumpeted the technical progress it's made in the transition to Chromium - boasting of how many "commits" its engineers have added to the project, for instance - the company has not yet made much of a case as to why enterprises should drop Chrome for the new Edge. The appearance of supported group policies, even incomplete as it was, implicitly argues for a change in enterprise browsers. "Thank you! This was high on my list, to see these GPO templates," said a user identified as Senturion33 in a comment appended to Lyndersay's post. "The seamlessness of [the planned implementation of IE mode] plus Chromium compatibility will have me pushing this out ASAP when it's available," added jrasmussen. Historically, Microsoft has had a major advantage over rival browsers in that its applications, particularly Internet Explorer (IE) in the days prior to Windows 10, could be managed by IT using Windows' group policies infrastructure. But as Google's Chrome overtook IE to become the world's most popular browser, it, too, took on enterprise characteristics, including scores of supported group policies. (Mozilla's Firefox, although accounting for less than 10% of global browser user, has also attended to business needs with its ESR, or Extended Support Release, version, in the hope of acquiring customers or keeping those it has.) The focus on group policies for full-Chromium Edge means Microsoft would like to reclaim its reputational spot. "Certainly, manageability is something that Microsoft always felt that it had a focus on," said Stephen Kleynhans, of Gartner. "It's always thought it brought an enterprise-class platform set of tools [to browsers]." The company, Kleynhans continued, both hopes and plans to bring a more manageable version of Chromium to enterprise customers. "That's one of the value-adds that Microsoft feels it brings." Some of the group policies administrators want will come later, not sooner, to Edge, said Lyndersay. Among them: GPOs (group policy objects) to manage the browser update process. "Policies for managing updates aren't included; those will be in a separate administrative template file," he wrote. "We need to verify each [Edge] update with remote vendors and to ensure policies still work as needed," said Senturion33. "The policy to disable the native update service is definitely part of the set we will have," Lyndersay answered. Unlike previous Microsoft browsers - IE and the 2015 Edge - full-Chromium Edge will be updated on a fast cadence, refreshed every six to eight weeks if the company keeps up with Chrome. Enterprises, some at least, will want to verify that each update works as expected with add-ons and web apps, before letting it land on employees' devices. Those organizations will need a way to block the native update mechanism. Edge on Macs will be managed via policies - those supported on macOS - deployed via a plist file, Lyndersay said. "We have tested with JAMF and a few other Mac management tools and will be publishing documentation with step-by-step instructions," he said on July 3. Updates to the group policy list will be announced on the group's Twitter account, @MSEdgeDev. And at some point, full-Chromium Edge will have its own policy change history documentation, similar to what the original Edge now has here. Source: Microsoft previews 'chromified' Edge's group policies to win enterprise approval (Computerworld - Gregg Keizer)
  10. Following Mozilla's lead, Microsoft pushes Edge onto anti-tracking bandwagon By adding 'tracking prevention' to the Chromium-based version of Edge, Microsoft can show it's putting a little distance between its browser and Google Chrome. Thinkstock Microsoft is the latest browser also-ran to tackle Google's leader, Chrome, by introducing anti-tracking expertise to Edge. Calling the feature "tracking prevention," Microsoft described it in terms much like those used by rivals Mozilla and Apple, which have cookie blockers in place in their browsers, Firefox and Safari. "Tracking prevention is designed to protect you from being tracked by websites that you aren't accessing directly," wrote Brandon Maslen, senior software engineer, and Ryan Cropp, software engineer, in a June 27 post to a company blog. Because Microsoft's just started to show its anti-tracking talents to users, it's hidden them behind an option flag; in Edge, it's reached by typing edge://flags in the address bar. (Edge's Chromium roots show here; the chrome://flags command has been long known to hard-core Chrome users.) Once the user has selected "Enabled" as the setting for the "Microsoft Edge tracking prevention" option, then relaunched the browser, Edge will begin stymying trackers. Microsoft Microsoft has hidden the new tracking prevention 'on' switch on the edge://flags option page; users must change the setting to 'Enable' and relaunch the browser. Additional settings appear in Edge's Settings that let users dial up or dial down tracker blocking's aggressiveness. Only the Windows version of the "Canary" build - the roughest, least reliable of the eventual four channels Microsoft will maintain - currently contains tracking prevention. The macOS Canary build will have the feature shortly; next up, certainly the Windows 10 and macOS Dev builds. Because the "full-Chromium" Edge - the browser Microsoft is re-creating this year based on the Chromium open-source project - also runs on Windows 7, 8 and 8.1, the blocking will eventually come to those OSes, as well. Microsoft In the Settings pane, users can tell Edge how tough to get on trackers. Computerworld set it to 'Strict' and encountered few problems. It's unclear how long it will take Microsoft to flesh out Edge's tracking prevention. Microsoft's Maslen and Cropp made it sound as if the effort were just beginning. "We'll use your feedback on this experimental feature in the Canary and Dev channels to understand potential impact to web compatibility and iterate on the experience to be helpful and easy to use," they said. That makes sense. For example, Mozilla, whose Firefox arguably boasts the most comprehensive anti-tracking scheme, spent years working on the defensive technology, first restricting it to the browser's privacy mode then cautiously integrating it with the browser as a whole. The deliberate work was necessary, Mozilla said, because tracking blockers have a habit of "breaking" sites. It was only earlier this month, in fact, that Mozilla felt comfortable enough with the feature to turn it on by default. It may not have been a coincidence that Microsoft touted tracking prevention not long after Mozilla switched on its Enhanced Tracking Protection (ETP). The privacy feature has been one of Mozilla's biggest selling points for Firefox, and the message has made an impression: The Washington Post last week said Chrome "looks a lot like surveillance software" because it doesn't try to stem tracking, and recommended Firefox as the browser best able to block trackers. "Having the world's biggest advertising company make the most popular web browser was about as smart as letting kids run a candy shop," asserted Geoffrey Fowler, the newspaper's technology columnist. "It made me decide to ditch Chrome for a new version of nonprofit Mozilla's Firefox, which has default privacy protections." Microsoft would want to be on the anti-Chrome side of this fight, seeing as how its browsers' influence, like that of Firefox's, has been greatly undermined by Google. Edge isn't going to grow much by stealing share from Firefox - Mozilla's browser has under 10% by the last measurement - but has to convince Chrome users on Windows to return to a Redmond-made application. Speaking of Chrome, Edge's tracking prevention can also be seen as Microsoft's loudest-yet statement of independence. Although Microsoft is now beholden to the Chromium project for its underlying technologies (and Google essentially runs Chromium), the company has hinted that it would not mimic Chromium/Chrome in all respects. Staking out a position that Google is unlikely to wholeheartedly adopt is one way to demonstrate that Edge is not just Chrome with a different name. The Windows 10 Canary build of Edge can be downloaded from Microsoft's website. Source: Following Mozilla's lead, Microsoft pushes Edge onto anti-tracking bandwagon (Computerworld - Gregg Keizer)
  11. Microsoft releases Microsoft Edge Chromium Group Policies preview Microsoft released an early preview of the policies that it plans to support in the Microsoft Edge Chromium web browser. Microsoft Edge Chromium, much like the classic Microsoft Edge browser, Google's Chrome web browser or Mozilla's Firefox browser, supports policies that administrators may set. The administrative template is available as a preview that has some limitations currently. The templates are only available in English (US), don't include policies for updates as Microsoft plans to release those in a separate administrative template file, and may change before the final release as policies may be added, changed, or removed based on feedback and development. All that is required is to download the administrative template for Microsoft Edge to the local system and add it to the Group Policy. If you are just interested in the available policies check out the HTML file that lists them all in the common folder. The HTML file lists all included policies in the template; each policy has a link to a details page that contains the description and other information useful to administrators. You can check out our instructions for adding Chrome templates to the Group Policy, or follow these basic steps to integrate the template: Download the Administrative Template from the Microsoft Tech Community website. Extract the zip archive on the local system. Note that it includes policies for Windows and Mac. Open the Group Policy Editor, e.g. by opening Start, typing gpedit.msc and selecting the item from the list of results. Right-click on Computer Configuration > Administrative Templates, and select Add/Remove Templates. Click on Add in the window that opens and browse to the location of the Microsoft Edge templates file. Select Close to end the process. You find the new policies in the Group Policy Editor afterward. All changes that administrators make are saved in the Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge. The policies for the old Microsoft Edge browser are saved to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\MicrosoftEdge instead. Closing Words The release of administrative templates for Microsoft Edge Chromium marks another important step towards a final release of the web browser. Microsoft has yet to announce an official release date for the new Edge version; a stable version is not available yet. Microsoft released preview versions of the browser for Windows 7 and 8.1 this week. (via) Source: Microsoft releases Microsoft Edge Chromium Group Policies preview (gHacks - Martin Brinkmann)
  12. As the title asks, does adguard block with Microsoft's new (chrome) browser? The reason for the question is on a particular site that I'm familiar ads and redirected pages open. This does not happen when used with such combinations as AG and Opera or AG and chrome. It's not a feature of the browser as they appear in those without AG. I think that they have not enabled it for Edge as yet. If they have it's not working.
  13. The move will allow companies who continue to use the legacy browser to run web sites or web apps inside the upcoming Chromium-based Edge. Microsoft Microsoft yesterday stuck a knife in Internet Explorer (IE) when it announced that the 23-year-old browser would appear as a "mode" within Edge in its new "full-Chromium" incarnation. While the Redmond company did not publish a death notice for IE or even admit to browser-cide, as sure as Law & Order's churning cast yanked criminals off streets, IE's days as a stand-alone browser are numbered. "The new Internet Explorer mode ... seamlessly render legacy IE-only content in high fidelity inside of Microsoft Edge, without the need to open a separate browser or for the user to change any settings manually," Kyle Pflug, a senior program manager lead who heads the developer ecosystem team, asserted in a post to a company blog. "Microsoft Edge uses your existing Enterprise Mode Site List to identify sites which require IE rendering and simply switches to Internet Explorer mode behind the scenes." Enterprise Mode is a Windows 10 feature that allows enterprise IT administrators to define which websites and web apps are opened in IE; currently, those sites and apps launch within the separate Internet Explorer 11 (IE11) bundled with Windows 10. Even though Microsoft built Windows 10 on the concept of multiple browsers - IE11 and Enterprise Mode for legacy sites and apps, Edge for all the rest - Pflug now derided the idea. "We hear from our customers that most enterprises rely on a multiple-browser solution today, and we hear from our customers and partners that this experience is disjointed and confusing," he said, implying IE is one of those browsers. (According to analytics data Net Applications, Chrome is the most likely partner in such scenarios.) In hindsight, IE's demotion should have been foreseen months ago when Microsoft program manager Chris Jackson belittled the application by calling it "a compatibility solution" and telling users that the more they used it, the further behind they'd fall. Pflug did not describe how the new IE11 mode will work within Edge when the latter wraps up its based-on-Chromium transformation. But no matter how Microsoft does it, its process won't be a first. Similar solutions have been around for years. One of the best known is IE Tab, a Chrome extension available since 2009 that displays pages using IE inside Google's browser. It does almost exactly what Pflug said the IE mode would do inside the revamped Edge. Another is Browsium's Catalyst, a tool that acts as an IT traffic cop, directing some sites and apps to open in one browser, Firefox or Chrome, say, and others in IE. And Google offers something like Catalyst - dubbed "Legacy Browser Support" (LBS) - to enterprise customers for handling required-IE pages and apps. Just last month with the release of Chrome 74, Google moved LBS from browser-external to browser-internal. The add-on that was once required no longer needs to be installed to use LBS. Once configured, usually by enterprise IT administrators, LBS automatically opens IE11 when links clicked within Chrome lead to websites, web services or web apps requiring Microsoft's browser, or more likely, IE's ActiveX controls or Java - neither of which Google's browser supports. By tucking IE11 into Edge, Microsoft will be able to dispense with standalone IE and keep its promise to support the legacy browser for an unspecified future. Microsoft has linked IE11's support to that of Windows 10, saying that the former will be maintained with security updates as long as the latter is also in support. "Internet Explorer 11 will continue receiving security updates and technical support for the lifecycle of the version of Windows on which it is installed," the company stated in a FAQ on the browser. Earlier this year, Computerworld laid out why it was unlikely that Microsoft would support IE indefinitely. One thing left unconsidered, however, was the browser-in-a-browser angle Microsoft decided to take. Even so, if Microsoft can add an IE mode to Edge, it can just as easily remove it when the old browser's no long useful to customers or too much of a burden in Redmond to justify continued support. In the meantime, IE integration can only help Edge's battle for some browser share. If Microsoft, as Computerworld expects, stops supporting stand-alone IE11 when full-Chromium Edge (with IE inside) reaches the Stable release channel, commercial users who require IE will take the path of least resistance and adopt Edge on Windows 10, the still-in-support Windows 8.1 and those Windows 7 PCs on the post-retirement paid support dole. Source: Microsoft will demote IE to a 'mode' inside Edge (Computerworld - Gregg Keizer)
  14. The iOS and Android versions of the company's Edge browser now support single sign-on and conditional access, a move that could spur more use for the mobile version of Edge. Microsoft Microsoft on Monday announced that the iOS and Android versions of its Edge browser now support single sign-on (SSO) and conditional access - crucial security, management and convenience features to the enterprise. Integrating Edge on mobile into the broader enterprise ecosystem - leveraging the SSO of Azure Active Directory (Azure AD), for example - may be Microsoft's best shot at getting its most important customers to adopt the browser. Edge's user share on mobile has been microscopic. According to analytics vendor Net Applications, Edge accounted for just six-hundredths of one percentage point in March, or more than 1,000 times less than the leader, Google's Chrome. Support for SSO and conditional access was added in a public preview of Edge, Mayunk Jain, a senior product manager, said in an April 22 post to a company blog. Jain told users to install the latest version and provided a link to an acquisition page. Sign in, please Users of Edge can now launch Azure AD-connected web apps, third-party or in-house, without having to re-enter credentials. Once logged in to the device, all other Azure-AD connected apps - those are designated by the organization's IT staff - can be accessed sans additional authentication. Microsoft When Edge is set as the default browser in the Outlook app and conditional access is enabled, all Azure AD-connected web resources open in Edge and without additional authentication. Edge can replace the clumsy Intune Managed Browser - a bare bones browser previously awarded managed status by Microsoft - for SSO, and thus streamline web app access. (Intune Managed Browser was first integrated with Azure AD and SSO in mid-2017, months before Edge debuted on iOS or Android.) It's also a way to push Edge onto enterprise users, who Microsoft must hope will dispense with the default browsers on their mobile devices (Chrome for Android, Safari for iOS). Certain conditions More important to the organization than SSO, conditional access support has also been handed Edge, said Jain, who didn't mince words about the browser rivals. "You can now enforce policy-managed Microsoft Edge as the approved mobile browser to access Azure AD-connected web apps, restricting the use of unprotected browsers like Safari or Chrome," he wrote. "Conditional access" is the umbrella term for a set of IT-mandated policies that determine which devices, from where and under certain situations, can access an organization's web apps from mobile devices. Rather than rely solely on username-password authentication to grant access, conditional access can consider a wide range of circumstances that must be in place before allowing the user to tap into company data. Is the device fully patched? Is it connecting from a familiar geographic location or does its IP address put it suddenly in, say, Moscow? Like SSO, conditional access is a feature of Azure AD, but unlike the former, the latter is limited to the most expensive identity plans, or SKUs of pricy subscriptions like Microsoft 365. It's also a club Microsoft can wield to get more enterprise users running Edge. "Users attempting to use unmanaged browsers such as Safari and Chrome will be prompted to open Microsoft Edge instead," Jain pointed out when describing how conditional access works with Edge. Late last year, Microsoft said it would rejigger Edge, dropping its own rendering and JavaScript engines, replacing them with those from the open-source Chromium project, which feeds code to Chrome. Although Edge for Android uses Chromium's components, Apple's App Store requirements will force Edge on iOS to continue using Safari's rendering and JavaScript engines. Source: Microsoft adds more reasons for enterprise users to run Edge on mobile devices (Computerworld - Gregg Keizer)
  15. Microsoft's Chromium-based Microsoft Edge web browser has not been released yet as a stable version; the preview versions that Microsoft released, Microsoft Edge Dev and Canary, provide a good understanding of the browser already, however. The web browser relies on the same core that Google Chrome uses, and that makes these browsers look and behave similarly in most aspects. That's good on the one hand, as it means faster updates and better web standards compatibility, but it also means that there is little that distinguishes the browser from Chrome unless modified. Companies that rely on Chromium can modify the browser; Vivaldi, Opera and Brave do this to create custom experiences that differ significantly from Chromium and Google Chrome. Microsoft's Edge browser will be different to a degree as well, and the following list of features highlights just some of the differences between Edge and Chrome. 1. Better Support for commercial Streaming Media services Microsoft Edge is the only Chromium-based browser that supports Google's Widevine DRM and Microsoft's own PlayReady DRM. Support for the latter unlocks 4K streams on Netflix, something that only Internet Explorer and Microsoft Edge (classic) support on Windows. Chrome, Firefox, and any other browser may stream with a quality of up to 1080p with the help of extensions. The feature is restricted to Windows 10, however. 2. Internet Explorer Mode The Chromium-based version of Microsoft Edge will (likely) come with Internet Explorer integration. The feature is listed as an experimental flag at this time which could mean that it is removed without further notice. It is more likely that the feature remains in Edge once it gets released to provide organizations with an option to access Internet Explorer optimized or exclusive content in Edge. The feature is not completely integrated right now but the description suggests that Edge users may load Internet Explorer content in a tab in Edge. 3. Support for Microsoft Voices Another feature that is hidden behind a flag currently. Enable Microsoft Voices Extension adds support for Microsoft voices in the SpeechSynthesis API. Interestingly enough, the feature is available for Windows, Mac and Linux devices. 4. Mute Tab instead of Mute Site Microsoft Edge supports tab muting. You can mute individual tabs using its default configuration which gives you more control over the muting process. Chrome supported this in previous iterations as well but Google changed the feature to site muting instead. If you mute a site in any tab, that site gets muted everywhere automatically in Chrome. In Edge, just click or tap on the sound icon in front of the page title in the tab to mute audio in that tab. Microsoft Edge still supports site permissions to mute audio permanently for individual domains. A flag is available to enable site-wide muting. Load chrome://flags/#edge-sound-content-setting to configure it. 5. Windows Defender SmartScreen integration Chrome and most Chromium-based browsers use Google's Safe Browsing security feature for security. Microsoft Edge will use Microsoft's Windows Defender SmartScreen security feature instead. The feature protects against malicious sites and downloads. Just like Google's implementation, it is known for the occasional false positive. Can be disabled in the settings. 6. Microsoft Account and Azure Active Directory support It should not come as a surprise that the Chromium-based Microsoft Edge web browser will support Microsoft Account and Azure Active Directory for authentication and single sign-in. Edge supports Microsoft infrastructure better than Chrome, and integration of these features confirms that. 7. Removed Google services Microsoft published a list of disabled or removed Google services in the Chromium-based Edge browser recently. The list of features is surprisingly long; Microsoft disabled some and replaced others (or plans to), e.g. Google Translate will be replaced by Microsoft Translate. While you could say that you trade one data-hungry company for another, it boils down to personal preference. 8. Exclusive Extensions Microsoft Edge users may install extensions from the Chrome Web Store or Microsoft's only store. The main advantage of this is that Microsoft's store does not have the same restrictions as Google's store. One example: Google disallows extensions that download videos from YouTube, Microsoft's Store does not. It is true, however, that Microsoft's Store lists a bit more than a 100 extensions at the time. It seems unlikely that many more will be added to the Store in the coming years if you consider the rather weak number of extensions that were produced for Edge or ported since 2015. Source: 8 ways in which Microsoft Edge (Chromium) is better than Google Chrome (gHacks - Martin Brinkmann)
  16. One of the main advantages of the upcoming Microsoft Edge web browser that is based on Chromium is that it supports multiple extension stores. Microsoft Edge users may install extensions from Microsoft's own extensions store for Edge, or enable an option in the web browser to unlock extension installations from the Chrome Web Store as well. But how different are the extensions designed specifically for Microsoft Edge, and the extensions offered by Google on the Chrome Web Store? Are there any extensions available exclusively that Chrome users cannot install? I decided to compare the available extensions for the Chromium-based Microsoft Edge browser that are offered on Microsoft's Edge extensions store with what is being offered on the Chrome Web Store. Microsoft's Edge extensions store list 117 extensions. The number of extensions on the Chrome Web Store is unknown as Google does not reveal it. The following extensions are unique to Microsoft Edge. Note that alternatives may be available on the Chrome Web Store for some of them. ClassLink OneClick -- offers access to web apps and files. Download music from VK -- VK music downloader. Easy Video and Audio Downloader -- media downloader (does not work on YouTube). Ebates Rakuten: Get Cash Back For Shopping -- shopping extension. Eno from Capital One -- shopping assistant. FlipGive Max -- shopping extension. Marker: Screen capture tool for professionals -- screenshot extension. Microsoft Personal Shopping Assistant -- shopping extension. MyPoints Score -- shopping extension. Rutoken Plugin for Edge -- digital signature, encryption, and 2FA extension. TrueKey (McAfee) -- password manager. Video Downloader Professional for Edge -- media downloader. Vonage Integration Suite -- communication extension. Wikibuy -- shopping extension. A total of 14 extensions are exclusive and may be installed in the Chromium-based Microsoft Edge browser. That leaves 103 extensions that are not unique and also available on the Chrome Web Store. Some users may wonder why Microsoft bothers with its own extensions store if most extensions are available on the Chrome Web Store as well. We need to look at the extensions that are unique in more detail to answer that question. The three main categories are shopping, media downloads, and Enterprise functionality. Shopping may come as a surprise to many, media downloading not so much. One of the limitations of Chrome extensions is imposed by Google policies. Extensions may not offer functionality to download media from select Google properties such as YouTube. Microsoft does not impose the same limitations on extension developers (Mozilla, Opera, and other browser makers don't either). Closing Words Maintaining an extension store for the Chromium-based Edge browser offers several advantages. It gives Microsoft full control over extensions including its own vetting and verification process. One of the main advantages is that extensions may offer features and options that Chrome extensions don't support in that form. Source: These Extensions are exclusive to the Chromium-based Microsoft Edge (gHacks - Martin Brinkmann)
  17. The company is being refashioned in ways its former CEOs could never have imagined. Thinkstock Microsoft stunned most tech watchers several months ago when it announced it was abandoning 25 years of its go-it-alone browser strategy and would replace Edge’s web rendering engine with one developed by the Chromium open-source project. The shock wasn’t just that Microsoft was turning to open source for its browser. It was that Chromium also powers Edge’s main rival, Google’s Chrome browser — and that the Chromium project was originally created by Google, although Google is not in charge of it now. The move was born of desperation. As Computerworld’s Gregg Keizer points out, Edge had only a 12% adoption rate in February, while Chrome had an insurmountable 67% market share. There’s been no evidence that Edge will ever catch up. There are plenty of reasons for Edge’s failure. But a significant one is the lack of add-ons for the browser — a paltry 118 at last count, even though Microsoft has been courting developers to write add-ons for Edge ever since the browser was introduced four years ago. That’s compared to many thousands for Chrome. When Edge adopts Chromium, Chrome extensions will almost certainly be able to run on it. By adopting Chromium, Microsoft can also free up Edge engineers to work on other company projects. And Edge will get more frequent updates than it does now, because Chromium generally gets updated eight times a year, Keizer reports. So there’s a great deal of logic to the move. It’s only surprising because of how much it goes against the company’s decades of going its own way with browsers. But it’s very much in keeping with CEO Satya Nadella’s cleanup of an old, die-hard Microsoft culture that vowed to dominate every market possible using the blunt force of Windows’ dominance. There’s poetic justice in Nadella accepting open-source standards for Edge and abandoning its go-it-alone ways. The move is a direct repudiation of the hard-charging, legally questionable tactics Bill Gates used to build Microsoft into what by the 1980s and 1990s had become the world’s most powerful tech company. Because of that dominance, in 1998 the U.S. Department of Justice and 20 state attorneys general sued Microsoft for illegally using its Windows monopoly to thwart competition. Internet Explorer was at the core of the case. Microsoft, at the time, required that computer makers include Internet Explorer in every Windows installation. The company also made it difficult, if not impossible, for consumers to install and use non-Microsoft browsers. Microsoft contended that Internet Explorer was so integral to Windows that removing it would slow down the operating system. The company also claimed it was easy for people to install alternate browsers. The trial uncovered the dirty underbelly of Microsoft’s strong-arm tactics. In perhaps the lowest point in the company’s public history, the company presented as evidence videotapes that purported to show that removing Internet Explorer would slow down Windows, and that it was quite simple to install a different browser on the operating system. It turned out, though, that Microsoft had doctored both tapes. Eventually Microsoft settled the suit. Microsoft’s abandoning of a proprietary browser in favor of open standards finally closes that chapter of the company’s past. As I’ve written previously, Nadella has revived Microsoft by, among other things, increasingly having the company accept and work with open-source software. The company’s SQL Server database now runs on Linux, for example. John “JG” Chirapurath, a general manager with Microsoft, puts the new Microsoft outlook this way: ““To keep flexibility and choice is absolutely critical. We can’t walk into a customer today and offer them a data platform that exclusively works with Windows or, say, C#. We’ve got to go in there and say, ‘Can we meet you on your terms, and what does that look like?’” Microsoft Vice President for Windows Joe Belfiore, in his announcement about Microsoft’s plan to move Edge to Chromium, seconded that by saying, “We intend to become a significant contributor to the Chromium project, in a way that can make not just Microsoft Edge — but other browsers as well — better on both PCs and other devices.” If true, that means Microsoft will be contributing to work that will not just make Edge better, but Chrome as well, because Chrome uses Chromium technology. The move signals a symbolic end to the old Microsoft. Microsoft’s proprietary browsing technology helped the company unfairly extend its monopoly, and that abuse eventually brought the company low. By going open source with the core of Edge, Nadella has finally refashioned Microsoft in a way that Bill Gates and Steve Ballmer could have never imagined. Source: Here’s why Microsoft raised the white flag on Edge (Ars Technica)
  18. Petrovic

    MS Edge

    edge-follow-os-theme Download: https://wbdiagstor.blob.core.chinacloudapi.cn/fileshare/microsoftedgesetup-latest.zip
  19. Google's most secure login system now works on Firefox and Edge, too Better hardware security key support means our post-password future is one step closer to reality. Yubico's hardware security keys let you log on without a password on sites, apps and devices that support the FIDO2 authentication technology. Stephen Shankland/CNET Google has updated its support for hardware security keys so you no longer need to rely on its Chrome browser to log into websites like Gmail, YouTube and G Suite. Hardware security keys, small devices that connect to devices wirelessly or with USB, offer better logon security than passwords alone or passwords combined with short-lived numeric codes sent to your phone. But until now, Google's support was limited to an earlier standard called U2F that came with a lot of confines. But now Google updated its login with the newer, broader standard of FIDO2 and its incarnation for websites, WebAuthn. The change means people using Mozilla's Firefox and Microsoft's Edge will be able to log into Google websites with hardware security keys -- though for now they'll still need Chrome to enroll in the system. And later, embracing FIDO2 opens the door for Google to move beyond passwords entirely, since FIDO2 enables authentication with a combination of security key and biometric data like faces or fingerprints. That would be a victory for those who want to move beyond today's plague of problems with passwords. U2F, short for Universal Second Factor, is limited to uses that combine the hardware key with a password. Browsers like Firefox, Edge and Apple Safari don't support it. FIDO2, which like U2F was developed by a consortium called the Fast Identity Online Alliance, encompasses U2F and other options, including just the hardware security key alone. Christiaan Brand, product manager for identity and security, announced Google's move to WebAuthn in a tweet Thursday. On Friday, Mark Risher, director of identity platform and account security, added: "FIDO2 rolling now!" Google didn't immediately comment on when people would be able to use other browsers to enable hardware security key login or whether Google plans to move to passwordless authentication. Google in February embraced FIDO2 for its Androidsoftware, a move that lets people use fingerprints to log into apps. Microsoft has embraced passwordless logon with Windows and online services like Outlook, Skype and Xbox Live. Source
  20. Mozilla Firefox and Microsoft Edge Hacked at Pwn2Own Mozilla Firefox and Microsoft Edge were both hacked in the second day of the Pwn2Own hacking contest, and in the case of the Windows 10 browser, researchers came up with a super-complex and clever approach to escape a virtual machine and get inside the host. Amat Cama and Richard Zhu of Fluoroacetate were the first to attempt to break into Mozilla Firefoxusing a JIT Bug and an out-of-bounds write in the Windows kernel. This technique allowed to run code at system level, technically taking over the machine completely after pointing Firefox to a crafted website. The two were received a price of $50,000. Mozilla’s browser was also hacked by Niklas Baumstark, who escaped the sandbox with a mix of a JIT bug and a logic bug. The researcher eventually obtained the same rights as the logged-in user, which could obviously provide full control of the host in the case of an administrator account. Baumstark received $40,000 for his exploit.Microsoft Edge exploitsFluoroacetate also hacked Microsoft Edge with a more complex attack that earned them $130,000. “Starting from within a VMWareWorkstation client, they opened Microsoft Edge and browsed to their specially crafted web page,” Zero Day Initiative explains. “That’s all it took to go from a browser in a virtual machine client to executing code on the underlying hypervisor. They started with a type confusion bug in the Microsoft Edge browser, then used a race condition in the Windows kernel followed by an out-of-bounds write in VMware workstation.” Arthur Gerkis of Exodus Intelligence also managed to exploit Microsoft Edge with a double free bug in the renderer mixed with a logic bug to escape the sandbox. His successful attack against the Windows 10 browser brought him $50,000. The vulnerabilities that the researchers used to break into the two browsers have been reported to Mozilla and Microsoft and they should be patched in the coming updates. Source
  21. Responding to complaints, Microsoft acknowledges that all of this month’s Win10 Patch Tuesday cumulative updates make it impossible to access certain local pages from Edge. Getty Images If you can’t get to your router’s admin page using the Edge browser, there’s a reason why. Microsoft broke it with this month’s cumulative updates. Yesterday, Microsoft appended this warning to all of its Windows 10 January cumulative update pages for version 1703 onward: After installing [this month’s cumulative update], some users report that they cannot load a webpage in Microsoft Edge using a local IP address. Browsing fails or the webpage may become unresponsive. There’s a manual workaround that involves adding the malfunctioning page’s IP address to your Trusted Sites list. That’s going to put a lot of creases on the already-overworked brows of security mavens, but so be it. The announcement concludes: Microsoft is working on a resolution and will provide an update in an upcoming release. Of course, the obvious solution is to use a different browser – even Internet Explorer seems to work – but whatever. Looking into the problem, I was surprised to see that it’s been well documented for more than a week. Poster Bree on Tenforums said: None of my physical machines can open my router page in Edge after the Dec. 8 update - that's Edge in the latest build of 1809, 1803, x86 or x64. It appears that only certain routers are affected. So far we have reports for Edge being unable to use web admin on Verizon FIOS-G1100, Netgear, WDC N750 and my BT HomeHub4. In general, if you’re using Edge to access a local page with an address like 192.168.x.x or myrouteradminpage.com and you can’t get to it, blame the latest cumulative update -- and switch browsers. Are you an AskWoody Plus member? Donate on the AskWoody Lounge. Source: There’s a newly acknowledged Edge local IP networking bug in Win10 (Computerworld - Woody Leonhard)
  22. After a few days of rumors, Microsoft announced today that it's going to be using Chromium in its browser moving forward and that the new Edge will be coming to Windows 7, 8.1, and macOS. Now, Mozilla CEO Chris Beard has posted a response to the news, saying that it's bad for the internet. Mozilla says that Microsoft's decision to use Chromium and the Blink rendering engine basically gives Google a monopoly on what we see on the internet. Remember, Chromium is the open-source browser that Google Chrome is based on, and other third-party browsers use it too, like Opera, Vivaldi, and more. With Microsoft moving away from EdgeHTML, that's one less competitor in the browser space, growing Chromium's market share. Mozilla worries that when Chromium's usage share gets large enough, web developers won't test their apps against anything else, going so far as to compare this to when Microsoft had a monopoly in browsers in the early 2000s. Mozilla also said that this is why it exists. "We compete with Google not because it’s a good business opportunity," Beard said. "We compete with Google because the health of the internet and online life depend on competition and choice." Source: Neowin
  23. A team of Belgian researchers discovered privacy issues in how browsers, ad-blocking, and anti-tracking implementations handle third-party cookie requests. A team of Belgian researchers from KU Leuven analyzed third-party cookie policies of seven major web browsers, 31 ad-blockers and 14 anti-tracking extensions and discovered major and minor issues in all of them. Major issues include Microsoft Edge's unwillingness to honor its own "block only third-party cookies" setting, bypasses for Firefox's Tracking Protection feature, and use of the integrated PDF viewer in Chrome and other Chromium-based browsers for invisible tracking. Cookie requests can be sorted into two main groups: first-party requests that come from the address listed in the address bar of the browser and third-party requests that come from all other sites. Advertisement displayed by websites makes use of cookies usually and some of these cookies are used for tracking purposes. Internet users can configure their browsers to block any third-party cookie requests to limit cookie-based tracking. Some browsers, for instance Opera or Firefox, include ad-blockers or anti-tracking functionality that is used in addition to that. Anti-tracking mechanisms have flaws The research paper, "Who Left Open the Cookie Jar? A Comprehensive Evaluation of Third-Party Cookie Policies", detailed information about each web browser, tests to find out if a browser is vulnerable to exploits, and bug reports are linked on the research project's website. The researchers created a test framework that they used to verify whether "all imposed cookie- and request-policies are correctly applied". They discovered that "most mechanisms could be circumvented"; all ad-blocking and anti-tracking browser extensions had at least one bypass flaw. In this paper, we show that in the current state, built-in anti-tracking protection mechanisms as well as virtually every popular browser extension that relies on blocking third-party requests to either prevent user tracking or disable intrusive advertisements, can be bypassed by at least one technique The researchers evaluated tracking protection functionality and a new cookie feature called same-site cookies that was introduced recently to defend against cross-site attacks. Results for all tested browsers are shown in the table below. The researchers tested the default configuration of Chrome, Opera, Firefox, Safari, Edge, Cliqz, and Tor Browser, and configurations with third-party cookie blocking disabled, and if available, tracking protection functionality enabled. Tor Browser is the only browser on the list that blocks third-party cookies by default. All browsers did not block cookies for certain redirects regardless of whether third-party cookies were blocked or tracking protection was enabled. Chrome, Opera and other Chromium-based browsers that use the built-in PDF viewer have a major issue in regards to cookies. Furthermore, a design flaw in Chromium-based browsers enabled a bypass for both the built-in third party cookie blocking option and tracking protection provided by extensions. Through JavaScript embedded in PDFs, which are rendered by a browser extension, cookie-bearing POST requests can be sent to other domains, regardless of the imposed policies. Browser extensions for ad-blocking or anti-tracking had weaknesses as well according to the researchers. The list of extensions reads like the who is who of the privacy and content blocking world. It includes uMatrix and uBlock Origin, Adblock Plus, Ghostery, Privacy Badger, Disconnect, or AdBlock for Chrome. The researchers discovered ways to circumvent the protections and reported several bugs to the developers. Some, Raymond Hill who is the lead developer of uBlock Origin and uMatrix, fixed the issues quickly. At least one issue reported to browser makers has been fixed already. "Requests to fetch the favicon are not interceptable by Firefox extensions" has been fixed by Mozilla. Other reported issues are still in the process of being fixed, and a third kind won't be fixed at all. You can run individual tests designed for tested web browsers with the exception of Microsoft Edge on the project website to find out if your browser is having the same issues. Closing Words With more and more technologies being added to browsers, it is clear that the complexity has increased significantly. The research should be an eye opener for web browser makers and things will hopefully get better in the near future. One has to ask whether some browser makers test certain features at all; Microsoft Edge not honoring the built-in setting to block third-party cookies is especially embarrassing in this regard. (via Deskmodder) Now You: Do you use extensions or settings to protect your privacy better? Source
  24. When Microsoft released Windows 10 build 17623 to Skip Ahead today, one of the "changes, improvements, and fixes" listed was that the company is going to start testing a feature that will force users of the Windows 10 Mail app to open links in the Edge browser. Dona Sarkar, who wrote the blog post, said that Edge "provides the best, most secure and consistent experience on Windows 10 and across your devices." The only problem is that not everyone feels that way. Many users have Chrome, Firefox, or something else set as their default browser, and Microsoft wants to subvert that in order to get them to use its own in-house solution. Luckily, Windows 10's default Mail app isn't the only email client that you can use. This isn't the first time that Microsoft has done something like this with Windows 10. In April 2016, it announced that Cortana will be locked down so that it will only work with Bing and Edge. Then, last May when the company launched Windows 10 S, it confirmed that users won't even have the option to switch their default browser or search engine on the new SKU of the OS. Luckily, Microsoft is only testing the feature, and it will take feedback from the Windows Insider community. Depending on how that goes, it may decide to push the feature. But make no mistake, despite the fact that this showed up in a Redstone 5 build, it will be made available through a Mail & Calendar app update, meaning that this could be pushed through at any time. If you're in the Skip Ahead subset of the Fast ring and you want to leave feedback on the new feature, you can do so via the Feedback Hub. Source
  25. A preview version of Microsoft's popular browser, Edge, was released for Android back in October. After coming out of beta almost two months later, it soon surpassed one million downloads on the Google Play Store. Last month, the application was updated to include support for adaptive icons, among other changes. Now, a new update has been made available to Edge for Android users, bumping the app to version and bringing a couple of interesting changes. Unsurprisingly, the update brings performance improvements, along with bug fixes; these accompany almost every app update. However, other changes include better support for the newsfeed of the New Tab Page, allowing users to personalize their feed based on the selected region and language. Similarly, improvements to the option that enables users to set Edge as their default browser have been made. The official changelog for the update reads as follows: At the time of writing, the popular browser holds a rating of 4.3 stars out of 5 on the Play Store based on user ratings. This is an improved score in comparison to its rating at the beginning of the year. In any case, if you're interested in these improved features, you can download the latest version of the application here. Source
  • Create New...