microsoft / microsoft/MicrosoftEdge-Extensions
Bug: webRequest API doesn't report ping requests after latest Beta update
Open
@Rahul-Bauri is already working on this.
Since Jul 31, 2025.
API
Bug
Edge Client
Tracked
- Dominant language
- JavaScript
- Stars
- 245
- Forks
- 149
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
As of the latest Edge Beta update, chrome.webRequest doesn't notify of ping requests. This breaks extension functionality for detecting tracking via the Beacon API.
Last known working version: Microsoft Edge 131.0.2903.51 beta
First known failing version: Microsoft Edge 132.0.2957.11 beta
To Reproduce
- I created a mock extension that simply logs all webRequests: Mock-Extension.zip
- The background script:
chrome.webRequest.onBeforeRequest.addListener( function(details) { console.log("webRequest onBeforeRequest:", details); console.log(`Request made to: ${details.url}`); }, {urls: ["<all_urls>"]}, ["requestBody"] ); - Upload the unpacked mock extension to Edge Beta
- Inspect the mock extension's background page to see the webRequest console logs
- Visit https://efforg.github.io/privacybadger-test-fixtures/html/beacon.html and refresh the page
- The background page console does not have any logs for the ping request to https://privacybadger-tests.eff.org/ (sent via navigator.sendBeacon)
Expected behavior
- Repeat above steps on Edge to see the correct behavior: the background page console should contain logs for "Request made to: https://privacybadger-tests.eff.org/"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.