ISSUE-84: Make DNT status available to JavaScript

Make DNT status available to JavaScript

State:

CLOSED

Product:

Tracking Preference Expression (DNT)

Raised by:

Opened on:

2011-09-22

Description:

This issue is about the DNT status (=the DNT header info sent to the site). Querying exception status is treated in other issues.

Related Actions Items:

• ACTION-224 on Nick Doty to Ensure that Section 4 reflects the latest DomAPI proposal by Nick - due 2012-07-15, pending review
• ACTION-142 on Roy Fielding to Include updated Javascript API - due 2012-03-12, closed
• ACTION-167 on Thomas Lowenthal to Come up with updated text for a DOM api to allow access to DNT state - due 2012-05-05, closed
• ACTION-200 on Ian Fette to Write text for ISSUE-84 due 2012-06-01 - due 2012-08-16, closed

Related emails:

1. RE: action-241: Propose changes regarding issue-116 (and also 'general preference') (from michael.oneill@baycloud.com on 2012-09-11)
2. Re: action-241: Propose changes regarding issue-116 (and also 'general preference') (from fielding@gbiv.com on 2012-09-11)
3. Re: action-241: Propose changes regarding issue-116 (and also 'general preference') (from singer@apple.com on 2012-09-10)
4. Re: action-241: Propose changes regarding issue-116 (and also 'general preference') (from rigo@w3.org on 2012-09-10)
5. action-241: Propose changes regarding issue-116 (and also 'general preference') (from npdoty@w3.org on 2012-09-09)
6. SUMMARY: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from mts-std@schunter.org on 2012-08-25)
7. Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from singer@apple.com on 2012-08-24)
8. Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from vigoel@adobe.com on 2012-08-23)
9. Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from gelman@blurryedge.com on 2012-08-23)
10. Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from singer@apple.com on 2012-08-23)
11. Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from vigoel@adobe.com on 2012-08-23)
12. RE: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from wileys@yahoo-inc.com on 2012-08-20)
13. Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from singer@apple.com on 2012-08-20)
14. Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from david@networkadvertising.org on 2012-08-19)
15. Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from npdoty@w3.org on 2012-08-18)
16. Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from haakonfb@opera.com on 2012-08-17)
17. RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from mts-std@schunter.org on 2012-08-15)
18. Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from mts-std@schunter.org on 2012-08-07)
19. ACTION-200 (text for ISSUE-84) (from ifette@google.com on 2012-07-25)
20. Re: ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals? (from cblouch@aol.com on 2012-07-20)
21. Re: ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals? (from jmayer@stanford.edu on 2012-07-18)
22. Re: ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals? (from ed@felten.com on 2012-07-18)
23. Re: Agenda for July 18, 2012 DNT WG Call on TPE (from fielding@gbiv.com on 2012-07-18)
24. Re: ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals? (from npdoty@w3.org on 2012-07-17)
25. Re: ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals? (from singer@apple.com on 2012-05-30)
26. ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals? (from npdoty@w3.org on 2012-05-30)
27. Agenda for May 23, 2012 DNT WG Call V01 (from mts-std@schunter.org on 2012-05-23)
28. RE: Agenda for May 16, 2012 DNT WG Call (from wileys@yahoo-inc.com on 2012-05-14)
29. Agenda for May 16, 2012 DNT WG Call (from mts-std@schunter.org on 2012-05-14)
30. Issues mentioned in the TPE document, or non-closed in the database and applying to TPE (from singer@apple.com on 2012-04-10)
31. RE: set of exceptions (from wileys@yahoo-inc.com on 2012-03-06)
32. Re: Work ahead; volunteers? (from john@consumerwatchdog.org on 2012-03-06)
33. How can a server understand the site-specific exceptions that are stored in a user agent (was: Work ahead; volunteers?) (from mts@zurich.ibm.com on 2012-03-06)
34. TPE: Work ahead; volunteers? (from mts@zurich.ibm.com on 2012-03-06)
35. Re: DNT-aware JavaScript (ISSUE-84, ACTION-85) (from mts@zurich.ibm.com on 2012-02-20)
36. RE: DNT-aware JavaScript (ISSUE-84, ACTION-85, ACTION-111) (from jccannon@microsoft.com on 2012-02-13)
37. Re: DNT-aware JavaScript (ISSUE-84) (from npdoty@w3.org on 2012-02-12)
38. Re: DNT-aware JavaScript (ISSUE-84, ACTION-85, ACTION-111) (from tlr@w3.org on 2012-02-09)
39. RE: DNT-aware JavaScript (ISSUE-84, ACTION-85, ACTION-111) (from jccannon@microsoft.com on 2012-02-09)
40. Re: DNT-aware JavaScript (ISSUE-84, ACTION-85, ACTION-111) (from tlr@w3.org on 2012-02-09)
41. RE: DNT-aware JavaScript (ISSUE-84, ACTION-85, ACTION-111) (from jccannon@microsoft.com on 2012-02-07)
42. Re: DNT-aware JavaScript (ISSUE-84, ACTION-85, ACTION-111) (from jmayer@stanford.edu on 2012-02-07)
43. Re: DNT-aware JavaScript (ISSUE-84, ACTION-85, ACTION-111) (from mts@zurich.ibm.com on 2012-02-07)
44. RE: DNT-aware JavaScript (ISSUE-84, ACTION-85, ACTION-111) (from wileys@yahoo-inc.com on 2012-02-01)
45. Re: DNT-aware JavaScript (ISSUE-84, ACTION-85, ACTION-111) (from tlr@w3.org on 2012-02-01)
46. Re: DNT-aware JavaScript (ISSUE-84, ACTION-85) (from fielding@gbiv.com on 2012-01-26)
47. Re: DNT-aware JavaScript (ISSUE-84, ACTION-85) (from jmayer@stanford.edu on 2012-01-25)
48. RE: DNT-aware JavaScript (ISSUE-84, ACTION-85) (from kevsmith@adobe.com on 2012-01-25)
49. Re: DNT-aware JavaScript (ISSUE-84, ACTION-85) (from jmayer@stanford.edu on 2012-01-25)
50. RE: DNT-aware JavaScript (ISSUE-84, ACTION-85) (from kevsmith@adobe.com on 2012-01-25)
51. Re: DNT-aware JavaScript (ISSUE-84, ACTION-85) (from tlr@w3.org on 2012-01-25)
52. Re: DNT-aware JavaScript (ISSUE-84, ACTION-85) (from jmayer@stanford.edu on 2012-01-25)
53. Re: DNT-aware JavaScript (ISSUE-84, ACTION-85) (from fielding@gbiv.com on 2012-01-25)
54. DNT-aware JavaScript (ISSUE-84, ACTION-85) (from jmayer@stanford.edu on 2012-01-25)
55. diff of TPE editing since the FPWD (from fielding@gbiv.com on 2012-01-10)
56. Proposed Agenda for 2011-12-21 TPWG call (from mts@zurich.ibm.com on 2011-12-20)
57. Request to close ISSUE-84 (from mts@zurich.ibm.com on 2011-12-20)
58. RE: Proposed Agenda for 2011-11-30 TPWG call (from wileys@yahoo-inc.com on 2011-11-30)
59. RE: Proposed Agenda for 2011-11-30 TPWG call (from wileys@yahoo-inc.com on 2011-11-30)
60. Proposed Agenda for 2011-11-30 TPWG call (from mts@zurich.ibm.com on 2011-11-30)
61. Re: ISSUE-84: Do we need a JavaScript API / DOM property for client-side js access to Do Not Track status? (from jmayer@stanford.edu on 2011-10-31)
62. ISSUE-84: Do we need a JavaScript API / DOM property for client-side js access to Do Not Track status? (from sysbot+tracker@w3.org on 2011-09-22)

Related notes:

Display change log