Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
562 changes: 562 additions & 0 deletions microsoft-edge/devtools-guide-chromium/performance/extension.md

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
Expand Up @@ -165,6 +165,10 @@ Cloning the repo is recommended over downloading the repo, so that you can pull

To clone the **MicrosoftEdge / Demos** repo to your local drive:

1. In a command prompt, enter `git` to check whether git is installed.

1. If not done already, [Download git](https://git-scm.com/downloads) and install it.

1. Go to [MicrosoftEdge / Demos](https://github.com/MicrosoftEdge/Demos) in a new window or tab.

1. Click the **Code** drop-down button, and then click the **Copy url to clipboard** button.
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
---
title: What's New in DevTools (Microsoft Edge 137)
description: "The Enable settings sync checkbox lets you sync your DevTools settings across devices. And more."
author: MSEdgeTeam
ms.author: msedgedevrel
ms.topic: conceptual
ms.service: microsoft-edge
ms.subservice: devtools
ms.date: 05/29/2025
---
# What's New in DevTools (Microsoft Edge 137)

These are the latest features in the Stable release of Microsoft Edge DevTools.


<!-- ====================================================================== -->
## Sync your DevTools settings between devices

<!-- Subtitle: Enable settings sync lets you sync your DevTools settings across devices. -->

You can now easily sync your DevTools settings across multiple devices by using your signed-in Microsoft Edge profile. This ensures that your preferences remain consistent, and makes it easier to work across different devices without needing to reconfigure the same settings.

To enable DevTools **Settings** sync:

1. In DevTools, select **Customize and control DevTools** (![Customize and control DevTools icon](./devtools-137-images/customize-and-control-devtools-icon.png)) > **Settings** (![Settings icon](./devtools-137-images/settings-icon.png)).

DevTools **Settings** appears, with the **Preferences** page selected.

1. Scroll down to the **Sync** section at the bottom, and then select the **Enable settings sync** checkbox:

![The "Enable settings sync" checkbox](./devtools-137-images/enable-settings-sync.png)

Your signed-in Microsoft Edge profile is displayed.

1. In DevTools **Settings**, click the **Close** (![Close button](./devtools-137-images/close-button.png)) button.


<!-- ====================================================================== -->
## Announcements from the Chromium project

Microsoft Edge 137 also includes the following updates from the Chromium project:

* [Connect a workspace folder and save changes back to your source files](https://developer.chrome.com/blog/new-in-devtools-137#workspace)
* [New insights in the Performance panel](https://developer.chrome.com/blog/new-in-devtools-137#new-perf-insights)
* [Duplicated JavaScript](https://developer.chrome.com/blog/new-in-devtools-137#duplicated-js)
* [Legacy JavaScript](https://developer.chrome.com/blog/new-in-devtools-137#legacy-js)
* [Speculations now support rule tags](https://developer.chrome.com/blog/new-in-devtools-137#speculation-rule-tags)

<!-- ====================================================================== -->
## See also

* [What's New in Microsoft Edge DevTools](../../whats-new.md)
* [Release notes for Microsoft Edge web platform](../../../../web-platform/release-notes/index.md)
Original file line number Diff line number Diff line change
Expand Up @@ -37,3 +37,4 @@ To report a problem with DevTools or ask for a new feature, file an issue in the
* [What's New in DevTools archive](./whats-new-archive.md)
* [Experimental features in Microsoft Edge DevTools](../experimental-features/index.md)
* [Release notes for Microsoft Edge web platform](../../web-platform/release-notes/index.md)
* [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule)
Original file line number Diff line number Diff line change
Expand Up @@ -6,57 +6,62 @@ ms.author: msedgedevrel
ms.topic: conceptual
ms.service: microsoft-edge
ms.subservice: extensions
ms.date: 02/11/2025
ms.date: 05/30/2025
---
# Contact the Microsoft Edge extensions team

You can contact the Microsoft Edge extensions support team to request help, submit feedback, or report a copyright or trademark infringement.


<!-- ====================================================================== -->
## Inquire about an extension's review status or certification status

For questions about a specific developer account, or questions about the review status or certification status of your extension after submitting the extension via Partner Center, email extensions developer support at [ext_dev_support@microsoft.com](mailto:ext_dev_support@microsoft.com).

For questions about a specific developer account or the certification status of a specific extension, don't use the public **Issues** tab or the **Discussions** tab in the MicrosoftEdge-Extensions repo; use email instead.
## Issues page in the MicrosoftEdge-Extensions repo
<!-- sync:
https://learn.microsoft.com/microsoft-edge/extensions-chromium/publish/contact-extensions-team#issues-page-in-the-microsoftedge-extensions-repo
https://github.com/microsoft/MicrosoftEdge-Extensions/blob/main/README.md#issues
-->

See also:
* [Publish a Microsoft Edge extension](./publish-extension.md)
Use the [Issues](https://github.com/microsoft/MicrosoftEdge-Extensions/issues) page of the **MicrosoftEdge-Extensions** repo for:

* Communicating with the Extensions team:
* Report bugs or issues about [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) (the store) that affect all Edge extension developers or all Microsoft Edge extension users.
* Report bugs or issues about Microsoft Partner Center that affect all Edge extension developers or all Microsoft Edge extension users.
* Suggest new features that could impact or benefit all Microsoft Edge extension developers.
* Inquire about your Partner Center developer account for Microsoft Edge extensions.
* Inquire about the review status or certification status of your Edge extension after submitting the extension via Partner Center.

<!-- ====================================================================== -->
## Send email to extensions developer support
* Communicating with other extension developers:
* Connect with other extension developers about technical questions related to building Microsoft Edge extensions.
* Ask about aspects of extensions that affect all extension developers or all Microsoft Edge extension users.

To discuss issues about a specific developer account or extension, you can privately contact extensions developer support at [ext_dev_support@microsoft.com](mailto:ext_dev_support@microsoft.com).
See also:
* [GitHub Issues](https://docs.github.com/get-started/using-github/communicating-on-github#github-issues) in _Communicating on GitHub_.
* [Scenarios for issues](https://docs.github.com/get-started/using-github/communicating-on-github#scenarios-for-issues) in _Communicating on GitHub_.


<!-- ====================================================================== -->
## Discussion forum in the MicrosoftEdge-Extensions repo
<!-- sync:
https://learn.microsoft.com/microsoft-edge/extensions-chromium/publish/contact-extensions-team#discussion-forum-in-the-microsoftedge-extensions-repo
https://github.com/microsoft/MicrosoftEdge-Extensions/blob/main/README.md#discussions
-->

Participate in the [Discussions](https://github.com/microsoft/MicrosoftEdge-Extensions/discussions) forum in the **MicrosoftEdge-Extensions** repo. You can:
* Discuss developing extensions.
* Share best practices with other developers on building, managing or acquiring more users for their browser extension.
* Connect with other extension developers about technical questions related to developing a Microsoft Edge extension.
* Share ideas about Microsoft Edge extensions.
* Share ideas about UI features that are at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
* Request a feature for extensions.
* Share inputs or suggestions to the Microsoft Edge extensions team.
* Discuss how to improve extension publishing, management and listing processes or workflows.
* Provide early feedback to the Microsoft Edge extensions team about new features for managing and publishing extensions.

See also:
* [README.md](https://github.com/microsoft/MicrosoftEdge-Extensions/blob/main/README.md) of the **MicrosoftEdge-Extensions** repo.

Use the [Discussions](https://github.com/microsoft/MicrosoftEdge-Extensions/discussions) page of the **MicrosoftEdge-Extensions** repo for:

<!-- ====================================================================== -->
## Issues page in the MicrosoftEdge-Extensions repo
* Discussions with the Extensions team:
* Follow the latest announcements and updates from the Microsoft Edge extensions team.
* Request a feature for Edge extensions.
* Discuss how to improve UI features that are at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/).
* Discuss how to improve extension publishing, management and listing processes or workflows.
* Provide feedback about features for extensions publishing, extensions management, or processes or workflows for extensions listings.

To publicly report or discuss an issue about extensions, use the [Issues](https://github.com/microsoft/MicrosoftEdge-Extensions/issues) page in the **MicrosoftEdge-Extensions** repo.
* Discussions with other extension developers:
* Discuss technical questions about developing an Edge extension.
* Share best practices, tips, and tricks with other developers on building, publishing, managing, or acquiring more users for their browser extension.
* Share ideas about features for Microsoft Edge extensions.

Use this **Issues** page for:
* Aspects of Microsoft Partner Center that affect all extension developers.
* Aspects of extensions that affect all extension developers or all Microsoft Edge extension users.
* Aspects of the UI that's at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/) that affect all extension developers or all Microsoft Edge extension users.
See also:
* [GitHub Discussions](https://docs.github.com/get-started/using-github/communicating-on-github#github-discussions) in _Communicating on GitHub_.
* [Scenarios for GitHub Discussions](https://docs.github.com/get-started/using-github/communicating-on-github#scenarios-for-github-discussions) in _Communicating on GitHub_.


<!-- ====================================================================== -->
Expand All @@ -82,3 +87,11 @@ You can follow what's happening with Microsoft Edge extensions via [#EdgeExtensi
<!-- not specific to extensions -->

For news and updates about developing for the web with Microsoft Edge, follow the [Microsoft Edge Dev (@MSEdgeDev)](https://x.com/msedgedev/) team on X (Twitter).


<!-- ====================================================================== -->
## See also

* [Publish a Microsoft Edge extension](./publish-extension.md)
* [README.md](https://github.com/microsoft/MicrosoftEdge-Extensions/blob/main/README.md) of the **MicrosoftEdge-Extensions** repo.
* [Communicating on GitHub](https://docs.github.com/en/get-started/using-github/communicating-on-github) - When to use **Issues** vs. **Discussions**.
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ To use the Microsoft Edge Add-ons API, you first need to enable the API for your

##### [v1.1](#tab/v1-1)

1. At your [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd), sign in to the account that you used to publish an add-on.
1. At your [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd), sign in to the account that you used to publish an Edge extension.

1. Under the **Microsoft Edge** program, select **Publish API**.

Expand Down Expand Up @@ -138,7 +138,7 @@ To use the Microsoft Edge Add-ons API, you first need to enable the API for your

##### [v1](#tab/v1)

1. At your [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd), sign in to the account that you used to publish an add-on.
1. At your [Partner Center developer dashboard](https://partner.microsoft.com/dashboard/microsoftedge/public/login?ref=dd), sign in to the account that you used to publish an Edge extension.

1. Under the **Microsoft Edge** program, select **Publish API**.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ ms.author: msedgedevrel
ms.topic: conceptual
ms.service: microsoft-edge
ms.subservice: pwa
ms.date: 12/19/2024
ms.date: 06/04/2025
---
# Provide in-app purchases with the Digital Goods API

Expand Down Expand Up @@ -39,35 +39,13 @@ See:
<!-- ====================================================================== -->
## Enable the Digital Goods API

The Digital Goods API is currently available for testing in Microsoft Edge. To test the API, use either of the following ways:
* To test your code locally: [Use a supported preview channel of Microsoft Edge on your dev machine](#use-a-supported-preview-channel-of-microsoft-edge-on-your-dev-machine).
* To test your code in your Microsoft Store PWA: [Register for the origin trial, then use your token at your website](#register-for-the-origin-trial-then-use-your-token-at-your-website).

Details are below.


<!-- ------------------------------ -->
#### Use a supported preview channel of Microsoft Edge on your dev machine

To test the Digital Goods API locally, before deploying your app to production, run Edge Dev or Edge Canary. These preview versions of Edge have the API enabled, as part of a running experiment.

To download a preview channel of Microsoft Edge (Beta, Dev, or Canary), go to [Become a Microsoft Edge Insider](https://www.microsoft.com/edge/download/insider).


<!-- ------------------------------ -->
#### Register for the origin trial, then use your token at your website

To test the Digital Goods API in production, with your users, use an origin trial token. With this approach, when your users download your PWA from the Microsoft Store, they will have the API enabled.

See:
* [Use origin trials in Microsoft Edge](../../origin-trials/index.md)
* [Digital Goods API](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/4b4a9ead-d912-4349-87b3-25e5e50b4f13) at _Origin Trials_.
The Digital Goods API is currently available for all channels in Microsoft Edge. To test the API, make sure your Edge version is `134.0.3124.51` or higher.


<!-- ====================================================================== -->
## Checking whether the Digital Goods API is available

To detect whether you've correctly enabled the API on your website by using your origin trial token, check whether the `getDigitalGoodsService` method exists on the `window` object:
To detect whether you have access to the API on your website, check whether the `getDigitalGoodsService` method exists on the `window` object:

```javascript
if ('getDigitalGoodsService' in window) {
Expand Down Expand Up @@ -119,7 +97,7 @@ See also:

Use the `getDetails` method of the `DigitalGoodsService` interface to query item details.

After connecting the Digital Goods service to Microsoft Store, you can use the API to access product and purchase information. The `getDetails` method lets you get information about the items youve set up in the Partner Center. Display information such as the product title, description, and price in your app UI, so the user knows what's available for purchase.
After connecting the Digital Goods service to Microsoft Store, you can use the API to access product and purchase information. The `getDetails` method lets you get information about the items you've set up in the Partner Center. Display information such as the product title, description, and price in your app UI, so the user knows what's available for purchase.

The `getDetails` method takes a list of item IDs, which correspond to the product IDs of the in-app products and subscriptions you created in the Partner Center.

Expand Down Expand Up @@ -269,10 +247,6 @@ See also:
## See also
<!-- all links in article: -->

Origin trials:
* [Use origin trials in Microsoft Edge](../../origin-trials/index.md)
* [Digital Goods API](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/4b4a9ead-d912-4349-87b3-25e5e50b4f13) at _Origin Trials_.

GitHub:
* [Digital Goods API For Microsoft Store PWA Explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/PwaDigitalGoods/explainer.md)
* [Digital Goods API specification](https://wicg.github.io/digital-goods/)
Expand Down
16 changes: 12 additions & 4 deletions microsoft-edge/toc.yml
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,10 @@
href: ./devtools-guide-chromium/whats-new/whats-new.md
displayName: release notes, announcements
# latest 10 What's New
- name: Microsoft Edge 137
href: ./devtools-guide-chromium/whats-new/2025/06/devtools-137.md
displayName: What's New in DevTools (Microsoft Edge 137) # page title

- name: Microsoft Edge 136
href: ./devtools-guide-chromium/whats-new/2025/05/devtools-136.md
displayName: What's New in DevTools (Microsoft Edge 136) # page title
Expand Down Expand Up @@ -129,16 +133,16 @@
href: ./devtools-guide-chromium/whats-new/2024/08/devtools-128.md
displayName: What's New in DevTools (Microsoft Edge 128) # page title

- name: Microsoft Edge 127
href: ./devtools-guide-chromium/whats-new/2024/07/devtools-127.md
displayName: What's New in DevTools (Microsoft Edge 127) # page title

# keep 10 items above
- name: Archive
items:
- name: What's New in DevTools archive
href: ./devtools-guide-chromium/whats-new/whats-new-archive.md

- name: Microsoft Edge 127
href: ./devtools-guide-chromium/whats-new/2024/07/devtools-127.md
displayName: What's New in DevTools (Microsoft Edge 127) # page title

- name: Microsoft Edge 126
href: ./devtools-guide-chromium/whats-new/2024/06/devtools-126.md
displayName: What's New in DevTools (Microsoft Edge 126) # page title
Expand Down Expand Up @@ -559,6 +563,10 @@
- name: Analyze CSS selector performance during Recalculate Style events
href: ./devtools-guide-chromium/performance/selector-stats.md
displayName: Performance tool, css selector stats, css selectors, selector stats, selector statistics, css selector statistics

- name: Customize performance profile with extensibility APIs
href: ./devtools-guide-chromium/performance/extension.md
displayName: Performance tool
# Memory tool -----------------------------------------------------------------
- name: Memory tool
items:
Expand Down
Loading
Loading