RE: Edge support for the user-granted exception mechanism

Has Edge support for DNT been resolved?  

-----Original Message-----
From: Craig Spiezle 
Sent: Thursday, June 30, 2016 2:25 PM
To: 'Mike O'Neill' <michael.oneill@baycloud.com>; public-tracking@w3.org
Cc: 'Brendon Lynch (CELA)' <Brendon.Lynch@microsoft.com>
Subject: RE: Edge support for the user-granted exception mechanism

I have escalated this internally to various teams and have copied Brendon Lynch the CPO.

-----Original Message-----
From: Mike O'Neill [mailto:michael.oneill@baycloud.com] 
Sent: Thursday, June 30, 2016 11:58 AM
To: public-tracking@w3.org
Subject: Edge support for the user-granted exception mechanism

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The Tracking Exception API no longer works in the latest release of Edge, now Microsoft’s primary consumer browser.

I reported this on the Microsoft Edge developer forum 3 weeks ago https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/7834877/ but it has not been responded to. I also raised a support request and sent emails but have hit a brick wall. I include the details below.

I felt the need to report this now because this is the last day of the group charter, unless it gets extended, and the Tracking Compliance and Scope requires user agents support the “user-granted exception mechanism”, see  the second paragraph under Scope https://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html#scope-and-goals


The bug in the Tracking Exception API in MS Edge.

Although the functions navigator.storeSiteSpecificTrackingException, navigator.storeWebWideTrackingException, navigator.removeSiteSpecificTrackingException and navigator.removeWebWideTrackingException still exist any call to them throws a JavaScript exception “Access is Denied”, and DNT:0 is never sent in the appropriate requests. Calls to navigator.confirmSiteSpecificTrackingException and navigator.removeWebWideTrackingException calls do not throw an exception and always return ‘false’, which is correct, but there is now no way to create a Tracking Exception so the call can never return ‘true’.

This API was supported in Edge from when it was introduced in March 2015. It was working fine the last time I tested it a few weeks ago. If this is a deliberate change I can find no reference to it on the web.

The latest Internet Explorer still supports the API, and it works as it always has since 2013.

There is a web page that exercises the API at https://cookieq.eu/api/test



Mike O'Neill
Technical Director
Baycloud Systems
Oxford Centre for Innovation
New Road
Oxford
OX1 1BY
Tel. 01865 735619
Fax: 01865 261401
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using gpg4o v3.5.54.6734 - http://www.gpg4o.com/

Charset: utf-8

iQIcBAEBAgAGBQJXdWvJAAoJEOX5SQClVeMPuHoP/3ungHctGByEhFHT0CrihaeK
qSwxaoY8mCvipugpHsHHVY8UoYMMKfyslt+tKvU5cBkB1T7QtTrwGG3pSA8mUITx
DJ8qG166a56O78m2tt1mkCVC/AsUe4tALkrx0EykLiCeXBoX9+2DhdfgtfNitqPS
4CfHbno0HYkwwNWLLtfu9T2zOo5+rh4UZ01Bc2GCEj2TX6Jatn/uadA9Ooc/PbDk
E//vEpx2fpKWIsGLM4gWn+VaKm+CQQqy+YgNBoKewFAXrwpl6fNPRcU7WSqukJLE
5FitTilY3k7u3aFM8bjEL+aUvqmLD7nwEop0NOyCCr5YM+DTDmGs9TRvUZtMhTkp
9zKNvE4CdpsCL1WAc7wP6wfYNJawtJ4NZ0tpw4g0u3Wno2ie7mqHQ17dqN+nvGwt
BIRgYGWXlXxcisNiH/pjRpLl77cR/RHoEHrOsU3Y2yXoYNFDoMd0qeg2gF1Clii2
PJJTXJsB/OJ3EJwzjH+7G39mzd+Af3eE09WLspqs/2V6+pU1O+J0kQjhJdpv5na7
qt9BPeZk4oSOZCMKYwp5mircu2VBYy9d81ZBFdxWpfHHW5/OwctVZyuAkt5LFpsU
R/B+qkSwcwZr7mlm9kGv7pKjHQ0sXJe/tANz0ByvfxhCZWGhQJzovMJtfFDtpcZ/
5GJ0JWf4/1q5K1i2vjnv
=EcBd
-----END PGP SIGNATURE-----

Received on Thursday, 6 October 2016 04:55:35 UTC