ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals?

How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals?

State:
CLOSED
Product:
Tracking Preference Expression (DNT)
Raised by:
Opened on:
2012-01-11
Description:
Related Actions Items:
Related emails:
  1. Re: Batch Closing of TPE-related ISSUEs: ISSUE-171, ISSUE-116, ISSUE-138, ISSUE-173, ISSUE-160 (from david@networkadvertising.org on 2012-11-05)
  2. Re: Batch Closing of TPE-related ISSUEs: ISSUE-171, ISSUE-116, ISSUE-138, ISSUE-173, ISSUE-160 (from singer@apple.com on 2012-11-05)
  3. Batch Closing of TPE-related ISSUEs: ISSUE-171, ISSUE-116, ISSUE-138, ISSUE-173, ISSUE-160 (from mts-std@schunter.org on 2012-11-05)
  4. Re: Towards closing the remaining issues in the TPE specification (from singer@apple.com on 2012-10-03)
  5. Re: Towards closing the remaining issues in the TPE specification (from fielding@gbiv.com on 2012-10-03)
  6. Re: Towards closing the remaining issues in the TPE specification (from jmayer@stanford.edu on 2012-10-02)
  7. Towards closing the remaining issues in the TPE specification (from mts-std@schunter.org on 2012-10-01)
  8. Re: Agenda for September 19, 2012 call (from jmayer@stanford.edu on 2012-09-19)
  9. Re: Agenda for September 19, 2012 call (from singer@apple.com on 2012-09-18)
  10. Agenda for September 19, 2012 call (from mts-std@schunter.org on 2012-09-18)
  11. Agenda for August 30, 2012 call (from mts-std@schunter.org on 2012-09-18)
  12. Re: action-241: Propose changes regarding issue-116 (and also 'general preference') (from rigo@w3.org on 2012-09-18)
  13. Re: action-241: Propose changes regarding issue-116 (and also 'general preference') (from singer@apple.com on 2012-09-18)
  14. Re: action-241: Propose changes regarding issue-116 (and also 'general preference') (from rigo@w3.org on 2012-09-18)
  15. Re: action-241: Propose changes regarding issue-116 (and also 'general preference') (from rigo@w3.org on 2012-09-18)
  16. RE: action-241: Propose changes regarding issue-116 (and also 'general preference') (from Brendan@iab.net on 2012-09-17)
  17. Re: action-241: Propose changes regarding issue-116 (and also 'general preference') (from singer@apple.com on 2012-09-17)
  18. Re: action-241: Propose changes regarding issue-116 (and also 'general preference') (from rigo@w3.org on 2012-09-17)
  19. Re: Intermediaries interfering with DNT decision making (from vp@iabeurope.eu on 2012-09-13)
  20. RE: Intermediaries interfering with DNT decision making (from michael.oneill@baycloud.com on 2012-09-13)
  21. RE: action-241: Propose changes regarding issue-116 (and also 'general preference') (from michael.oneill@baycloud.com on 2012-09-11)
  22. Re: action-241: Propose changes regarding issue-116 (and also 'general preference') (from fielding@gbiv.com on 2012-09-11)
  23. Re: action-241: Propose changes regarding issue-116 (and also 'general preference') (from singer@apple.com on 2012-09-10)
  24. Re: action-241: Propose changes regarding issue-116 (and also 'general preference') (from rigo@w3.org on 2012-09-10)
  25. action-241: Propose changes regarding issue-116 (and also 'general preference') (from npdoty@w3.org on 2012-09-09)
  26. Agenda for August 30, 2012 call (from mts-std@schunter.org on 2012-08-27)
  27. 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)
  28. Agenda for August 15, 2012 call (from mts-std@schunter.org on 2012-08-13)
  29. Re: agenda for August 08, 2012 call (from mts-std@schunter.org on 2012-08-07)
  30. agenda for August 08, 2012 call (from mts-std@schunter.org on 2012-08-07)
  31. agenda for August 08, 2012 call (from mts-std@schunter.org on 2012-08-07)
  32. 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)
  33. 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)
  34. 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)
  35. Re: Agenda for July 18, 2012 DNT WG Call on TPE (from fielding@gbiv.com on 2012-07-18)
  36. 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)
  37. 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)
  38. 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)
  39. Issues mentioned in the TPE document, or non-closed in the database and applying to TPE (from singer@apple.com on 2012-04-10)
  40. RE: set of exceptions (from wileys@yahoo-inc.com on 2012-03-06)
  41. Re: Work ahead; volunteers? (from john@consumerwatchdog.org on 2012-03-06)
  42. 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)
  43. TPE: Work ahead; volunteers? (from mts@zurich.ibm.com on 2012-03-06)
  44. ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals? (from sysbot+tracker@w3.org on 2012-01-11)

Related notes:

Reopened due to discussion on 2012-08-15 (and action generated for Nick)

Matthias Schunter, 27 Aug 2012, 07:41:19

changed to pending review to match the document

David Singer, 27 Sep 2012, 17:31:44

No objection against closing (see email Batch closing)

Matthias Schunter, 25 Nov 2012, 16:31:36

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 116.html,v 1.1 2019/02/01 09:32:27 vivien Exp $