- From: Chris Pedigo <Chris@digitalcontentnext.org>
- Date: Thu, 4 Feb 2016 00:35:08 +0000
- To: Mike O'Neill <michael.oneill@baycloud.com>
- CC: "rob@blaeu.com" <rob@blaeu.com>, "public-tracking@w3.org" <public-tracking@w3.org>
That is my understanding as well. But Apple may be working on a fix here. Perhaps David can provide an update when appropriate. > On Feb 2, 2016, at 7:57 AM, Mike O'Neill <michael.oneill@baycloud.com> wrote: > > I created a separate table for extensions, and added PrivacyBadger on > Firefox to it. > > I added a separate entry for Chrome on iOS as it does not support DNT at the > moment, which I think is because this is not configurable in the WKWebView > component it now uses. If this is wrong let me know. > > Mike > > > > -----Original Message----- > From: Rob van Eijk [mailto:rob@blaeu.com] > Sent: 31 January 2016 10:28 > To: michael.oneill@baycloud.com > Cc: public-tracking@w3.org > Subject: Wiki Privacy/TPWG/TPE Implementation Report > > Hi Mike, > Dear group, > > I will add the Maxthon Cloud browser to the table > [https://www.w3.org/wiki/Privacy/TPWG/TPE_Implementation_Report]. > > We should differentiate between browsers and DNT extensions in two > tables. The point of restricting table 1 to browsers would be to show > that only IE implemented the consent API partly. The point of > restricting table 2 to DNT extentsions woukld be to show tools using DNT > to enhance transparency and user control. > > Rob > > > >
Received on Thursday, 4 February 2016 00:35:41 UTC