Steps to reproduce
I posted this on the Do Not Track bug but that is now marked fixed so might not be being looked at.
I have tested the latest Edge release on insider preview to check the DNT API bug fix.
storeStiteSpecificTrackingException now works for the top level origin and embedded third-party origins but not for XHRs sent to external domains from script running in the top level context . This works in the Internet Explorer and used to work on Edge so must be a bug introduced in the last fix.
You can check this with our tester at https://baycloud.com/dntapi. 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 ( or window.doNotTrack is updated) after a request for an exception.
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “James M.”
Changed Status to “Not reproducible”
Thank you for providing this information about the issue. After thorough testing, we are unable to reproduce the expected results on your sample webpage; the images are all displaying Unset and clicking them does not appear to change anything. Please reopen this case when you can review the sample and provide us new repro steps.
The MS Edge Team
The test page shows the value of DNT. If it says “unset” this is because you have not set DNT. In addition there is a recognised bug in the release version of Edge so the Do Not Track API does not work at all, so clicking the button will not do anything.
You have to use the current insider preview version of Edge where the API bug has been fixed, and set Do Not Track in it. You should then see the DNT:0 image.