All posts by Microsoft Edge Team

Introducing the Storage Access API – Microsoft Edge Blog

Today, we’re excited to announce the “first-look” rollout of the Storage Access API in our Canary and Dev channels. For developers, this API allows them to determine whether their access to browser-based storage is restricted by a user’s privacy settings and to request storage access from users if so. This capability can be used to create graceful fallback experiences in cases when storage access may be restricted by features such as tracking prevention in Microsoft Edge. For users, this API provides greater transparency into and control over the sites that are requesting access to browser-based storage that could be used to track their behaviors across the web. This post outlines what the addition of the Storage Access API means for both developers and users.

Using the Storage Access API is as easy as updating your code to leverage the following new functions:
hasStorageAccess()
Useful to check if access to cookies and other storage exists in the current context.
Returns a promise with a boolean result indicating if storage access exists or not.

requestStorageAccess()
Requires a user gesture to invoke.
Useful to request access to storage for a single third-party context.
Returns a promise that will resolve if access is either available or granted and reject if unsuccessful.

Note: Since we are still gradually rolling out the Storage Access API, it’s possible that you may not have it enabled by default on your device. If you want to test it early, please enable the “Storage Access API” flag in edge://flags.
The usage of these new functions is best demonstrated with an example.
Example:
A social media site, contoso.social, offers sites the ability for developers to embed social media widgets as third-party content on their sites. One site where these widgets appear is www.contoso.example. To offer the ability for contoso.social users to comment on, save, or share contoso.example content with friends, contoso.social’s embedded content needs access to its own storage such as cookies or localStorage in the context of contoso.example in order to associate these actions with a visitor’s account.
Checking for Access:
contoso.social can use document.hasStorageAccess() to see if access to storage already exists and to provide an alternative user experience such as displaying a request to login or request access if not:

Requesting Access:
If no storage access is currently present, contoso.social can request access during a user gesture. As an example, the onclick handler of a login button could be tied to a request for storage access (see the “User Experience” section below) using the document.requestStorageAccess() method.

Sandboxing
The allow-storage-access-by-user-activation token can be used to enable the usage of the API when embedded content is loaded in a sandboxed iframe. In practice, both the allow-scripts and allow-same-origin tokens will also be required as well to ensure the API can be effectively used.

As a developer, we hope you will leverage the Storage Access API to create web-based experiences that will continue to be compatible even as browsers place more restrictions on third-party storage.

With the introduction of the Storage Access API, you may notice an “Allow cookies and site data?” prompt like the one below when you interact with third-party content such as social media widgets or embedded videos while browsing:

This indicates that the site whose embedded content you’re interacting with (contoso.social in the example above) currently has its storage restricted by Microsoft Edge’s privacy settings and is requesting your permission to access its storage within the context of the site you’re visiting (https://www.contoso.example in the example above). While several types of sites require storage access for legitimate scenarios such as making sure you’re signed in when you expect to be, allowing this access can allow the site requesting it track your activity on the site you’re currently visiting.
Clicking “Allow” will temporarily allow the requesting site access to its storage on the site you were visiting when the prompt appeared. This allowance will last for a 30-day period after which it will automatically expire. Clicking “Block” will prevent the requesting site from accessing its storage on the site you were visiting when the prompt appeared. If you change your mind, interacting with the third-party content a second time will cause the prompt to be displayed again, giving you the option to revisit your choice.
To give you control over any storage access requests you’ve allowed before they automatically expire, you’ll notice a new “Cookies and site data you’ve temporarily allowed” section at the bottom of the edge://settings/content/cookies page. Here, you can review and revoke the storage access requests you’ve granted in a single list:

We implemented the Storage Access API upstream so that all Chromium-based browsers could benefit from it. We are also actively participating in standardization discussions that are ongoing in the W3C Privacy Community Group to ensure that the API works uniformly across browsers. If you have any feedback on the functionality or capabilities of the API itself, please feel free to join the standardization discussions by filing an issue on GitHub. If you have any feedback on the Storage Access API as it exists in Microsoft Edge, please send us feedback using in-app feedback tool (Alt + Shift + I).
To close, we’d like to thank our friends at Apple and Mozilla for their early work on the Storage Access API and our friends at Google for helping pave the way for getting the API implemented in Chromium. We’re excited for you to try it out and to hear what you think!
–  Brandon Maslen, Senior Software Engineer–  Scott Low, Senior Program Manager

Protecting users from potentially unwanted applications in Microsoft Edge – Microsoft Edge Blog

Our customer feedback tells us that when users search for free versions of software, they often find applications with a poor reputation being installed on the machine at the same time. This pattern indicates that the user has downloaded an application which shows offers (or bundles) for potentially unwanted applications (PUA).
Potentially unwanted applications can make the user less productive, make the user’s machine less performant, and lead to a degraded Windows experience. Examples of PUA include software that creates extra advertisements, applications that mine cryptocurrency, applications that show offers for other software and applications that the AV industry considers having a poor reputation.
In the new Microsoft Edge (beginning with 80.0.338.0), we’ve introduced a new feature to prevent downloads that may contain potentially unwanted apps (PUA), by blocking those apps from downloading. This feature is off by default, but can be turned on in three easy steps:
Tap … (Settings and more) > Settings.
Choose Privacy and services.
Scroll down to Services, and then turn on Block potentially unwanted apps.

Here is what users will see when a download is blocked by the feature (Note: PUA blocking requires Microsoft Defender SmartScreen to be enabled):

To learn more about what Microsoft defines as PUA, see the criteria in our documentation.
If an app has been mislabeled as PUA, users can choose to keep it by tapping … in the bottom bar, choosing Keep, and then choosing Keep anyway in the dialog that appears.

From edge://downloads/, users can also choose Report this app as reputable, which will direct them to our feedback site. There, users can let us know that they think the app is mistakenly marked as PUA.
If you own the site or app in question, you can let us know here. Your feedback will be reviewed by our team to determine an appropriate follow up action.

Our goal is to assist users in getting the apps they want, while empowering them to maintain control over their devices and experiences.
You can learn more about how Microsoft identifies malware, unwanted software, and PUA in our security documentation.
We encourage users to always try to download software from a trusted location, such as the publisher’s website or a reputable app store, and to check reviews of the app and the reputation of the publisher before downloading.
If you are an admin or IT professional and are interested in enabling this feature on for your users, see our enterprise documentation here.
We hope you’ll try out this new feature in the new Microsoft Edge and let us know what you think! Give us your feedback by clicking the feedback link in the upper right corner of your browser or pressing Alt-Shift-I to send feedback.
– Juli Hooper and Michael Johnson, Microsoft Defender ATP

New optimizations boost performance in preview builds of Microsoft Edge – Microsoft Edge Blog

Starting with Microsoft Edge build 81.0.389.0 on 64-bit Windows 10, we’ve enabled new toolchain optimizations that should provide a substantial performance improvement in general browsing workloads.We’ve measured an up to 13% performance improvement in the Speedometer 2.0 benchmark when compared to Microsoft Edge 79. Speedometer measures performance by simulating user interactions in a sample web app across a number of DOM APIs and popular JavaScript frameworks used by top sites, and is generally regarded as a good proxy for real-world performance across a number of different subsystems including the DOM, JavaScript engine, layout, and more.
We’d like your help validating these improvements in your real-world browsing as we approach our next Beta release later this month. You can try out these improvements by comparing performance in the latest Dev or Canary builds to Microsoft Edge 80 or earlier.
The details:
We measured Speedometer 2.0 in ten consecutive runs on Microsoft Edge 79, where the optimizations are not yet implemented.  The results are below.

Microsoft Edgev. 79.0.309.71
1
84.6
2
85.4
3
85.3
4
85.3
5
84.6
6
84.9
7
85.8
8
84.7
9
84.8
10
84.3
Median
84.85
Benchmarked on Windows 10 1909 (OS Build 18363.592) on a Microsoft Surface Pro 5 (Intel(R) i5-8250U CPU 1.60GHz and 8 GB RAM), with no other applications running and no additional browser tabs open.
We then ran Speedometer 2.0 on recent versions of Microsoft Edge 81 which include the new optimizations, with the following results.

Microsoft Edgev. 81.0.410.0
Microsoft Edgev. 81.0.403.1
1
96.3
96.7
2
91.1
95.7
3
91.7
95.2
4
96
95.5
5
97.6
95.5
6
97.4
95.9
7
96.8
96.2
8
94.4
96.2
9
96.4
95.5
10
94.4
95.4
Median
96.15
95.6
Benchmarked on Windows 10 1909 (OS Build 18363.592) on a Microsoft Surface Pro 5 (Intel(R) i5-8250U CPU 1.60GHz and 8 GB RAM), with no other applications running and no additional browser tabs open.
We would love for you to try the new optimizations in Dev or Canary and let us know if you notice these improvements in  your real-world experience. Please join us on the Microsoft Edge Insider forums or Twitter to discuss your experience and let us know what you think! We hope you enjoy the changes and look forward to your feedback!
Update as of 02/20/2020 – Thank you to the Microsoft Edge Insider Community for continuing to test and provide feedback on Microsoft Edge. Your testing and feedback helped us identify a compatibility issue with a third party app that we’re actively working to address. We’ve modified the optimizations to mitigate the issue and expect you’ll see more modest performance improvements in the upcoming Beta Channel build. Please continue hammering on the Canary and Dev builds and sending us feedback!

Bringing the Microsoft Edge DevTools to more languages – Microsoft Edge Blog

We know inclusivity makes us work better and we love when we find ways to put that knowledge into practice. On the Edge team, we believe—and usage and research show—that developer experiences are more productive when they fit our language and location preferences. Today, we’re excited to move in that direction by announcing that the new Microsoft Edge now features DevTools localized in 10 languages (in addition to English):
Chinese (Simplified) – 中文(简体)(简体)
Chinese (Traditional) – 中文(繁體)(繁體)
French – français
German – deutsch
Italian – italiano
Portuguese – português
Korean – 한국어
Japanese – 日本語
Russian – русский
Spanish – español
This adds our new browser tools to a long list of other localized Microsoft developer experiences including VS Code, Azure Portal, and more.
This release is the result of collaboration over many months between our team and the DevTools, Lighthouse, and Chrome teams at Google. We’ve contributed all localizability features upstream (explainer), and plan to continue to do so so that other browsers can benefit from this work.
Try the localized developer tools
Make sure you have “Enable localized Developer Tools” turned on by heading to edge://flags, finding that flag, and setting it to “Enabled” (this is on by default in Canary; on by default soon in Dev, Beta, and Stable channels). Once on, your DevTools will match the language of the browser. On macOS, the developer tools inherit the language from the operating system. You can change the language in the Settings under the “Language and Region” section. Add another language, change it to your primary. Once you restart Microsoft Edge, the developer tools will be in that language.
If you just wanted to try the feature out and wish to revert to English, go to DevTools Settings (F1) > Preferences and click the checkbox to deselect “Match browser language.”

What’s next
For the initial release, we went with the top languages used by web developers within our ecosystem. Next, we’re evaluating popular right-to-left languages like Hebrew and Arabic and working on localizing our documentation. If you’d like those languages or other features in the localization and internationalization space, please let us know. We’re always happy to hear your thoughts.
To get in touch, you can Send Feedback from the Microsoft Edge menu (Alt-Shift-I), or share your thoughts with us on Twitter.
– Erica Draud, Program Manager, Microsoft Edge DevTools

Get started with Collections in Microsoft Edge – Microsoft Edge Blog

We’re excited to announce that Collections is now enabled by default for all Microsoft Edge Insiders in the Canary and Dev channels (build 80.0.338.0 or later). Following our initial preview behind a feature flag two months ago, we have been adding in new features and functionality. For those who enabled the feature flag – thank you! We have been listening to your feedback and are excited to share the improvements we’ve made.We designed Collections based on what you do on the web. If you’re a shopper, it will help you collect and compare items. If you’re an event or trip organizer, Collections will help pull together all your trip or event information as well as ideas to make your event or trip a success. If you’re a teacher or student, it will help you organize your web research and create your lesson plans or reports. Whatever you are doing on the web, Collections can help.
Recent improvements to Collections
We’ve been working hard to add more functionality and refine the feature over the last couple months – some of which were directly informed by your feedback.
Here are some of the improvements we made, based on your input:
Access your collections across your devices: We’ve added sync to Collections. We know some of you have seen issues around sync, your feedback has been helping us improve. We know this is an important scenario and are ready for you to try it. When you are signed into Microsoft Edge preview builds with the same profile on different computers, Collections will sync between them.
Open all links in a collection into a new window: We’ve heard you’d like an easy way to open all sites saved in a collection. Try out “Open all” from the “Sharing and more” menu to open tabs in a new window, or from the context menu on a collection to open them as tabs in the current window so you can easily pick up where you left off. We’ve also heard that you want an easy way to save a group of tabs to a collection. This is something that we are actively working on and are excited to share when it is ready.
Edit card titles: You’ve been asking for the ability to rename the titles of items in collections, so they are easier for you to understand. Now you can. To edit a title, right click and choose “Edit” from the context menu. A dialog will appear giving you the ability to rename the title.
Dark theme in Collections: We know you love dark theme, and we want to make sure we provide a great experience in Collections. We’ve heard some feedback on notes which we’ve addressed. Try it out and let us know what you think.
 “Try Collections” flyout: We understand that if you’re an active user of Collections that we were showing you the “Try Collections” flyout even though you previously used the feature. We’ve now tuned the flyout to be quieter.
Sharing a collection: You’ve told us that once you’ve collected content you want to share it with others. We have lots of work planned to better support sharing scenarios. One way you can share today is through the “Copy all” option added to the “Sharing and more” menu, or by selecting individual items and copying them via the “Copy” button in the toolbar.

Once you’ve copied items from your Collection, you can then paste them into your favorite apps, like OneNote or Email. If you are pasting into an app that supports HTML you will get a rich copy of the content.

Try out Collections
You can get started by opening the Collections pane from the button next to the address bar.
When you open the Collections pane, select Start new collection and give it a name. As you browse, you can start to add content related to your collection.

Send Feedback
Now that we’re on by default, we hope that more of you will give us a try. Thank you again to all of you that have been using the feature and sending us feedback. If you think something’s not working right, or if there’s some capability you’d like to see added, please send us feedback using the smiley face icon in the top right corner of the browser.

Thanks for continuing to be a part of this preview!

Improving Tracking Prevention in Microsoft Edge – Microsoft Edge Blog

Today, we’re excited to announce some improvements to our tracking prevention feature that have started rolling out with Microsoft Edge 79. In our last blog post about tracking prevention in Microsoft Edge, we mentioned that we are experimenting with ways that our Balanced mode can be further improved to provide even greater privacy protections by default without breaking sites. We are looking to strike a balance between two goals:Blocking more types of trackers – Microsoft Edge’s tracking prevention feature is powered by Disconnect’s tracking protection lists. We wanted to build off our initial implementation of tracking prevention in Microsoft Edge 78 and maximize the protections we offered by default by exploring blocking other categories of trackers (such as those in the Content category) in Balanced mode. These changes resulted in Microsoft Edge 79 blocking ~25% more trackers than Microsoft Edge 78.
Maintaining compatibility on the web – We knew that blocking more categories of trackers (especially those in the Content category) had the potential to break certain web workflows such as federated login or embedded social media content.
We learned through experimentation that it is possible to manage these tradeoffs by relaxing tracking prevention for organizations with which a user has established a relationship. To determine this list, we built on-device logic that combines users’ personal site engagement scores with the observation that some organizations own multiple domains that they use to deploy functionality across the web. It’s worth mentioning that this compatibility mitigation only applies to Balanced mode; Strict mode will continue to block the largest set of trackers without any mitigations.

The Chromium project’s site engagement score is a measure of how engaged a specific user is with a specific site. Site engagement scores can range from 0 (meaning a user has no relationship with a site) to 100 (meaning that a user is extremely engaged with a site). Activities such as browsing to a site repeatedly/over several days, spending time interacting with a site, and playing media on a site all cause site engagement scores to increase, whereas not visiting a site causes site engagement scores to decay exponentially over time. You can view your own site engagement scores by navigating to edge://site-engagement.
It’s also worth noting that site engagement scores are computed on your device and never leave it. This means that they are not synced across your devices or sent to Microsoft at any time.
Through local experimentation, we found that a site engagement score of 4.1 was a suitable threshold to define a site that a user has an active relationship with. While this value is subject to change based on user feedback and future experiments, it was selected as an initial value for two reasons:
It is low enough to ensure successful interactions with a site that a user has not previously had a history of engagement with.
It is high enough to ensure that sites a user visits infrequently will drop off the list relatively quickly.
While site engagement helps signal which sites are important to individual users, allowing third party storage access/resource loads from only these sites would not consider the fact that organizations can serve content that users care about from multiple domains, which can still result in site breakages.
Combining site engagement with organizations
In our last blog post about tracking prevention, we introduced the concept of an organization, that is, a single company that can own multiple domains related to their business (such as Org1 owning “org1.test” and “org1-cdn.test”). We also shared that in order to keep sites working smoothly, our tracking prevention implementation groups such domains together and exempts storage/resource blocks when a domain in one organization requests resources from another domain in that same organization.
In order to keep sites that users engage with working as expected while also increasing the types of trackers that we block by default, we combined the concept of an organization together with site engagement to create a new mitigation. This mitigation takes effect whenever a user has established an ongoing relationship with a given site (currently defined by a site engagement score of 4.1 or greater). For example, consider the following organization which owns two domains:
Social Org
social.example
social-videos.example
A user will be considered to have a relationship with Social Org if they have established a site engagement score of at least 4.1 with any one of its domains.
If another site, content-embedder.example, includes third-party content (say an embedded video from social-videos.example) from any of Social Org’s domains that would normally be restricted by tracking prevention, it will be temporarily allowed as long as the user’s site engagement score with Social Org’s domains is maintained above the threshold.
If a site does not belong to an organization, a user will need to establish a site engagement score of at least 4.1 with it directly before any storage access/resource load blocks imposed by tracking prevention will be lifted.
What does this mean?
By exempting sites and organizations that you have an ongoing and established relationship with from tracking prevention, we can ensure that the web services and applications you care about continue to work as you expect across the web. Leveraging site engagement also allows us to only unblock content that is likely to be important to you and reflects your current needs. This ensures that actions such as briefly visiting a site or seeing a popup aren’t enough to unblock content by themselves. If content does get unblocked due to you interacting with a site, it is always unblocked in a temporary manner that is proportional to how highly engaged you are with that site/its parent organization. By combining these exemptions with more strict blocking of trackers by default, we can provide higher levels of protection while still maintaining compatibility on the ever-evolving set of sites that you engage with.
It’s worth noting that tracking prevention, when enabled, will always block storage access and resource loads for sites that fall into the Fingerprinting or Cryptomining categories on Disconnect’s tracking protection lists. We will also not apply the site engagement-based mitigation outlined above for our most privacy-minded users who opt into tracking prevention’s Strict mode.

The best way to learn what’s changed with tracking prevention in Microsoft Edge 79 is to take a look at the table below:
Along the top are the categories of trackers as defined by Disconnect’s tracking protection list categories.
Along the left side are comparisons of the improvements made to our tracking prevention feature broken down into Basic, Balanced, and Strict.
The letter “S” in a cell denotes that storage access is blocked.
The letter “B” in a cell denotes that both storage access and resource loads (i.e. network requests) are blocked.
A “-“ in a cell denotes that no block will be applied to either storage access or resource loads.
The “Same-Org Mitigation” refers to the first mitigation that we introduced in our previous blog post and recapped above.
The “Org Engagement Mitigation” refers to the second mitigation based on site engagement that we introduced earlier in this post.

Advertising
Analytics
Content
Cryptomining
Fingerprinting
Social
Other
Same Org Mitigation
Org Engagement Mitigation
Basic

Microsoft Edge 78



B
B


Enabled
Not impl.
Microsoft Edge 79



B
B


Enabled
N/A
Balanced

Microsoft Edge 78
S


B
B
S

Enabled
Not impl.
Microsoft Edge 79
S

S
B
B
S
S
Enabled
Enabled1
Strict 2

Microsoft Edge 78
B
B

B
B
B
B
Enabled
Not impl.
Microsoft Edge 79
B
B
S
B
B
B
B
Enabled
Disabled
Does not apply to Cryptomining or Fingerprinting categories.
Strict mode blocks more resource loads than Balanced. This can result in Strict mode appearing to block less tracking requests than Balanced since the trackers making the requests are never even loaded to begin with.
With our recent updates in Microsoft Edge 79, we have seen, on average, 25% more trackers blocked in Balanced mode. Close monitoring of user feedback and engagement time also showed no signs of negative compatibility impact, suggesting that the org engagement mitigation is effective at minimizing breakage on sites that users actively engage with. While this does mean that top sites have the org engagement mitigation applied more often, we believe this is an acceptable tradeoff versus compatibility, especially as more top sites are starting to give users mechanisms to transparently view, control, and delete their data.
As with all our features, we’ll continue to monitor telemetry and user feedback channels to learn more and continually improve tracking prevention in future releases. We are also exploring additional compatibility mitigations such as the Storage Access API, which we intend to experiment with in a future version of Microsoft Edge.
InPrivate Changes
In our previous blog post, we mentioned that users browsing in InPrivate will automatically get Strict mode protections. By listening to the feedback our users provided, we found that this led to unexpected behavior (such as causing sites that worked in a normal browsing window to fail to load InPrivate) and broke some important use cases. That’s why in Microsoft Edge 79, your current tracking prevention settings will be carried over to InPrivate sessions.
We are currently experimenting in our Canary and Dev channels with a switch at the bottom of our settings panel (which you can reach by navigating to edge://settings/privacy) that will allow you to re-enable Strict mode protections InPrivate by default:

We’ve also made it easier for you to view the trackers that Microsoft Edge has blocked for you. Navigate to edge://settings/privacy/blockedTrackers to test out this new experience today!

We’d love to hear your thoughts on our next iteration of tracking prevention. If something looks broken, or if you have feedback to share on these changes, we’d love to hear from you. Please send us feedback using the “smiley face” in the top right corner of the browser.
Send feedback at any time with the Send a Smile button in Microsoft Edge

As always, thanks for being a part of this journey towards a more private web!
–  Scott Low, Senior Program Manager–  Brandon Maslen, Senior Software Engineer

Join the Microsoft Edge team next week at Ignite 2019 – Microsoft Edge Blog

Next week, we will be travelling to Microsoft Ignite 2019 to share what’s new in Microsoft Edge for enterprises, IT professionals, and web developers. We’re very excited to share more about our journey with Chromium over the past year, what it means to your customers, and to hear your feedback.In this post, we’ve outlined all the breakout sessions and other activities our team will be presenting at Ignite next week, so you can easily track which sessions you want to attend or review later. This year, Ignite is also introducing Roundtable Topics, which are a great opportunity to share your experiences with the product team directly, provide feedback, and help us understand how we can empower you and your organization with Microsoft Edge.
The full list of sessions is provided below. We look forward to seeing you there! Don’t miss out—sign in using your attendee or tech community account to build your Ignite schedule today!

Monday, November 4th
2:00 – 2:45 PM ET: BRK012 – The Web: Where the rubber hits the road on security and manageability, and productivity
Join VP of Product for Microsoft Edge, Chuck Friedman, Group Product leader for Microsoft Edge Enterprise, Sean Lyndersay, and VP of Bing, Jordi Ribas to discuss how Microsoft Edge and Microsoft Search in Bing is the best browser and search for business. We can help you with a systematic approach to identity and security, high-performing intranet and internet searches, and how to think about web and app compatibility on the internet.
3:15 – 4:00 PM ET: BRK1019 – State of the browser: Microsoft Edge
Come learn about the history of Microsoft Edge and the decision to move to Chromium as well as the roadmap for enterprises and show you the 4 pillars of what the team focuses on: Rock solid fundamentals, Safety and Security, Flexible and efficient manageability and deployment, and end-user productivity.
Tuesday, November 5th
11:05 – 11:20 AM ET: MLS1020 – Microsoft Edge and Chromium: What’s new for web developers
In this Microsoft Ignite Live session, Burke Holland will interview Kyle Pflug, PM for Microsoft Edge Developer Experiences, about what the new Chromium foundation means for your web sites and web apps, and how the Microsoft Edge team is working with web standards and the Chromium community to build a better web for everyone.
1:50 – 2:10 PM ET: THR2279 – Mechanics Live: Microsoft Edge and Microsoft Search: Complete tour for IT admins and users
Join Chuck Friedman and Jeremy Chapman to get a comprehensive understanding of the enterprise-focused capabilities in the new Microsoft Edge browser. This is a 20-minute Theater session filmed in the Mechanics Live studio in the hub and you are a part of the experience.
3:05 – 3:25 PM ET: THR108 – Top 10 reasons why you’ll choose the next version of Microsoft Edge
We’re on a mission to create the best browser for the enterprise. We believe the next version of Microsoft Edge is that browser and in this session, we will share the top 10 reasons why.
Roundtable Topics
Wednesday, November 6th
 10:15 – 11:00 AM: BRK2230 – One browser for modern and legacy web apps: deploying Microsoft Edge and IE mode
We have worked with numerous companies – ranging from 1,000’s to 100,000’s of seats – to move from multiple browser environments to a single browser environment. We’ll share lessons learned and best practices for piloting and deploying the next version of Microsoft Edge by leveraging our investments in Internet Explorer mode, Configuration Manager, and Intune.
1:50 – 2:10 PM ET: THR1075 – Enterprise ready PDF solution in Microsoft Edge
Customers have communicated they want a PDF solution in the browser, so they don’t have to manage additional 3rd party software. The Microsoft Edge’s PDF solution will help you understand the investments we’re making so we can accomplish that specific feedback.
Roundtable Topics
Thursday, November 7th
12:45 – 1:30 PM ET: BRK3099 – Moving the web forward: Microsoft Edge for web developers
The next version of Microsoft Edge is built on a new foundation, powered by Chromium. This foundation will empower you with a consistent set of developer tools and enable you to deliver powerful standards-based and hybrid application experiences using web technologies. In this session, we’ll share how our upcoming release simplifies cross-browser testing and enables the latest capabilities for your sites and line of business (LOB) apps, plus our ongoing contributions to Chromium that improve the browser experience for everyone. Finally, we’ll reveal what’s next for web developers in the new Microsoft Edge.
3:40 – 4:00 PM ET: THR106 – Microsoft Edge on macOS
Microsoft Edge will be our first browser for macOS in 13 years. In this session, we share how Microsoft Edge feels at home on macOS, how you can be more productive and secure using it, and what you need to know about managing Microsoft Edge on macOS.
Roundtable Topics
Friday, November 8th
10:15 – 11:00 AM ET: BRK3253 – Protected, productive mobile browsing with Microsoft Edge and Intune
Microsoft Edge isn’t just a desktop browser. The mobile platform has been going strong for close to 2 years. This session will show you the investments we’re making to allow for a full range of experiences starting with management capabilities with Intune, customizing the end user experience, and how to migrate from the Microsoft Intune managed browser to Microsoft Edge.
11:30 AM – 12:15 PM ET: BRK2231 – Keep users productive and data secure in a cloud-first world: secure browsing with Microsoft Edge
Wrap up your Friday with a deep dive on all things security regarding Microsoft Edge. Features such as Application Guard, Conditional Access, and Microsoft Information Protection will be discussed along with other security measures to show you how Microsoft Edge is the most secure browser in the enterprise.
See you there! Don’t forget to sign in using your attendee or tech community account to build your Ignite schedule today!
– Colleen Williams, Senior Program Manager, Microsoft Edge

Update on removing Flash from Microsoft Edge and Internet Explorer – Microsoft Edge Blog

In 2017, we published a roadmap to remove Adobe Flash from Microsoft Edge and Internet Explorer by 2020. Since that post, we announced our intent to build Microsoft Edge on the Chromium open source project. In this post, we will provide an update on what to expect for the Flash retirement in Microsoft browsers.Here’s what you can expect for each Microsoft browser:
In the next version of Microsoft Edge (built on Chromium), we will continue to retire Flash in the same timeframe as other Chromium based browsers. You can learn more of that timeline in this blog post. Flash will initially be disabled, and the user will need to re-enable Flash on a site-by-site basis; Flash will be completely removed from the browser towards the end of 2020. Group policies are available for enterprise admins and IT pros to change the Flash behavior prior to that date.
For both the in-market version of Microsoft Edge (built on EdgeHTML) and Internet Explorer 11, the current experience will continue as-is through 2019. Specifically, we no longer intend to update either Microsoft Edge (built on EdgeHTML) or Internet Explorer 11 to disable Flash by default. We still plan to fully remove Flash from these browsers by December 2020, as originally communicated.
– Colleen Williams, Senior Program Manager, Microsoft Edge
[Updated to clarify the in-market EdgeHTML/IE experience – Ed.]

Collections is now available to test in the Canary channel – Microsoft Edge Blog

Today, we’re releasing an experimental preview of Collections for Microsoft Edge. We initially demoed this feature during the Microsoft Build 2019 conference keynote. Microsoft Edge Insiders can now try out an early version of Collections by enabling the experimental flag on Microsoft Edge preview builds starting in today’s Canary channel build.We designed Collections based on what you do on the web. It’s a general-purpose tool that adapts to the many roles that you all fill. If you’re a shopper, it will help you collect and compare items. If you’re an event or trip organizer, Collections will help pull together all your trip or event information as well as ideas to make your event or trip a success. If you’re a teacher or student, it will help you organize your web research and create your lesson plans or reports. Whatever your role, Collections can help.
The current version of Collections is an early preview and will change as we continue to hear from you. For that reason, it’s currently behind an experimental flag and is turned off by default. There may be some bugs, but we want to get this early preview into your hands to hear what you think.

To try out Collections, you’ll need to be on the Canary Channel which you can download from the Microsoft Edge Insider website.
Once you’re on the right build, you’ll need to manually enable the experiment. In the address bar, enter edge://flags#edge-collections to open the experimental settings page. Click the dropdown and choose Enabled, then select the Restart button from the bottom banner to close all Microsoft Edge windows and relaunch Microsoft Edge.

Once the Collections experiment is enabled, you can get started by opening the Collections pane from the button next to the address bar.

Drag/drop: When you have the Collections pane open, you can add specific content from a webpage with drag and drop. Just select the image, text, or hyperlink and drag it into the collection.

Context menu: You can also add content from a webpage from the context menu. Just select the image, text, or hyperlink, right-click it, and select Add to Collections. You can choose an existing collection to add to or start a new one.

When you add content to Collections, Microsoft Edge creates a visual card to make it easier to recognize and remember the content. For example, a web page added to a collection will include a representative image from that page, the page title, and the website name. You can easily revisit your content by clicking on the visual card in the Collections pane.

You’ll see different cards for the different types of content you add to Collections. Images added to a collection will be larger and more visual, while full websites added to a collection will show the most relevant content from the page itself. We’re still developing this, starting with a few shopping websites. Content saved to a collection from those sites will provide more detailed information like the product’s price and customer rating.

Add notes: You can add your own notes directly to a collection. Select the add note icon from the top of the Collections pane. Within the note, you can create a list and add basic formatting options like bold, italics, or underline.
Rearrange: Move your content around in the Collections pane. Just click an item and drag and drop it in the position you prefer.
Remove content: To remove content from your collection, hover over the item, select the box that appears in the upper-right corner, and then select the delete icon from the top of the Collections pane.

Once you’ve created a collection, you can easily use that content by exporting it. You can choose to export the whole collection or select a subset of content.
Send to Excel: Hit the share icon from the top of the Collections pane and then select Send to Excel. Your content will appear on a new tab with pre-populated table(s) that allow you to easily search, sort, and filter the data extracted from the sites you added to your Collection. This is particularly useful for activities like shopping, when you want to compare items.

Copy/paste: Select items by clicking the box in the upper right. A gray bar will appear at the top of the Collections pane. Select the copy icon to add those items to your clipboard. Then, paste it into an HTML handler like Outlook by using the context menu or Ctrl+V on your keyboard.
Sending content to Excel is available for Mac and Windows devices running Windows 10 and above. We’ll add support for Windows devices running Windows 7 and 8 soon. Additional functionality, like the ability to send to Word, will also come soon.

This is the just the first step in our Collections journey and we want to hear from you. If you think something’s not working right, or if there’s some capability you’d like to see added, please send us feedback using the smiley face icon in the top right corner of the browser.

Thanks for being a part of this early preview! We look forward to hearing your feedback.
– The Microsoft Edge Team

An update on disabling VBScript in Internet Explorer 11 – Microsoft Edge Blog

In early 2017, we began the process of disabling VBScript in Internet Explorer 11 to give the world the opportunity to prepare for it to be disabled by default.The change to disable VBScript will take effect in the upcoming cumulative updates for Windows 7, 8, and 8.1 on August 13th, 2019. VBScript will be disabled by default for Internet Explorer 11 and WebOCs for Internet and Untrusted zones on all platforms running Internet Explorer 11. This change is effective for Internet Explorer 11 on Windows 10 as of the July 9th, 2019 cumulative updates.
The settings to enable or disable for VBScript execution in Internet Explorer 11 will remain configurable per site security zone, via Registry, or via Group Policy, should you still need to utilize this legacy scripting language.
To provide feedback on this change, or to report any issues resulting from this change, you can use the Feedback Hub app on any Windows 10 device. Your feedback goes directly to our engineers to help make Windows even better.
– Brent Mills, Senior Program Manager