ISSUE-163: How in the spec should we ensure user agents don't twist a user preference one way or another?
How in the spec should we ensure user agents don't twist a user preference one way or another?
- State:
- CLOSED
- Product:
- Compliance Next
- Raised by:
- Opened on:
- 2012-09-19
- Description:
- Part of original issue: Text that biases user decisions, "express" work flows, etc.
Related to outcome of ISSUE-149; http://lists.w3.org/Archives/Public/public-tracking/2012Sep/0197.html - Related Actions Items:
- No related actions
- Related emails:
- Batch closing of TCS issues (from jbrookman@cdt.org on 2014-09-10)
- Re: issue and action cleanup proposals (from jmayer@stanford.edu on 2013-05-21)
- Agenda for May 22 call (from peter@peterswire.net on 2013-05-21)
- Re: issue and action cleanup proposals (from ylagos@futureofprivacy.org on 2013-05-21)
- Re: issue and action cleanup proposals (from jmayer@stanford.edu on 2013-05-19)
- issue and action cleanup proposals (from npdoty@w3.org on 2013-05-15)
- Re: Mapping the "framework" to ISSUEs (from john@consumerwatchdog.org on 2013-05-07)
- Mapping the "framework" to ISSUEs (from jmayer@stanford.edu on 2013-05-07)
- Re: user interface/user education (from npdoty@w3.org on 2013-04-09)
- Re: DNT: Agenda for March 20 call (revised) (from peter@peterswire.net on 2013-03-19)
- Re: DNT: Agenda for March 20 call (from jmayer@stanford.edu on 2013-03-19)
- DNT: Agenda for March 20 call (from peter@peterswire.net on 2013-03-19)
- ISSUE-163: How in the spec should we ensure user agents don't twist a user preference one way or another? (Text that biases user decisions, 'express' work flows, etc). Related to outcome if ISSUE-149 and http://lists.w3.org/Archives/Public/public-tracking (from sysbot+tracker@w3.org on 2012-09-19)
Related notes:
Noted during issue cleanup, this may be a sub-issue of issue-194.
Nick Doty, 29 May 2013, 01:30:52Closed per http://lists.w3.org/Archives/Public/public-tracking/2014Sep/0023.html
Justin Brookman, 25 Feb 2015, 03:48:46Display change log