Do Not Track Consent API not working on Edge

Fixed Issue #7834877


Mike O.
Jun 9, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

In webdev Console type:
navigator.storeSiteSpecificTrackingException({detailURI: "{any url}", explanationString: "explanation", siteName:"site name"});
You get Access is denied exception.
This used to work (and it works on IE11) , but I have just noticed it now does not.
Thousands of sites use this API


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To to “Christian F.”

    • removeSiteSpecificTrackingException({}); also throws an “Access is denied” exception.
      confirmSiteSpecificTrackingException({}) returns false i.e. does not throw an exception

      Also, if someone is looking at this, (this has been pointed out before), the doNotTrack property is on window, it should be on navigator


    • In contract IE11 still works, which is provable by going (say), hitting F12 Console,
      executing navigator.storeSiteSpecificTrackingException({});
      This does not throw an exception, returns void
      If you refresh the page you can see DNT:0 headers in the requests. (to and its embedees)
      Edge used to do this also, but quite recently no longer does

    • Microsoft Edge Team

      Changed Assigned To to “Venkat K.”

      Changed Assigned To to “Dave B.”

      Changed Assigned To from “Dave B.” to “Bruce M.”

    • Any news on this issue?

    • Microsoft Edge Team

      Changed Assigned To from “Bruce M.” to “Zach M.”

      Changed Assigned To from “Zach M.” to “Swathi G.”

    • Here is a test page that execrcises the DNT JavaScript API
      The test result at line 4 & 5 should be a green tick showing DNT:0 being received at the embedee server
      This works in IE11 (some of the subsequent tests fail but that is another issue with IE11)
      It used to work in Edge up till a few weeks ago

    • This bug report is 2 weeks old, why has it not been addressed?

    • It has been 26 days since this bug was reported and still no comment.

      If anyone ever gets round to looking at this, the correct version of the Tracking Preference & Scope Document (now a Candidate Recommendation) is:
      not the document linked to under the “Standard affected” heading.

    • Microsoft Edge Team

      Changed Status to “Confirmed”

    • Still no comment here (after a month), though I have been told its a recognised bug and in the process of being fixed. I just downloaded the windows insider latest version on windows 10, but the problem is still there.

    • Actually its been 2 months.

    • 3 months now

    • 4

    • Thanks for the bug report. We are in the process of implementing DNT Exceptions in Edge now. You’ll be able to test it in an Insider update when it’s ready.

    • Thanks Sean, that’s good to know.

      You can test it using my demonstrator page , where you can click on either the “first-party” button or the “third-party” buttons to toggle DNT to them.

      I also have a DNT API exerciser page at which tests each feature in turn. On IE and on Edge (up till last May) it does a restart and page refresh after each failure to handle implementations that need a refresh before they change DNT.

      I also wrote a browser extension (only on Chrome desktop ATM) that implements the API there,

    • Have these fixes reached 14986? If not will they be in next Insider Build?


    • Any news when this “bug” will be fixed? It is over 7 months now since it was introduced.

    • The bug is fixed in current Windows 10 Insider Preview builds. Thanks!

    • Microsoft Edge Team

      Changed Status from “Confirmed” to “Fixed”

    • I have tested it on insider preview .

      storeStiteSpecificTrackingException now works for the top level origin and embedded third-party origins but not for XHRs send to external domains from top level script. This works in the Internet Explorer and used to work on Edge so this must be a bug introduced in the last fix.

      You can check this with our tester at If you click on the big DNT icon in IE you can see the image flip to DNT:0 for the first-party and the third-parties. On Edge it only flips the first-party. This is because XHRs are still being sent with DNT:1 after a call to store SiteSpecificTrackingException. I have not tested it for dynamic image or other element creation.

      navigator.doNotTrack is still not being set (its on window.doNotTrack) , and you still have to do a reload before DNT:0 is sent after a request for an exception.

    • Hello,

      Thank you again for all of your help with resolving this case. If you are seeing new problems, please open a new bug report so we can work the issue in a separate case.

      Best Wishes,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in