- From: Thomas Roessler <tlr@w3.org>
- Date: Thu, 17 Jan 2008 19:25:58 +0100
- To: Ian Fette <ifette@google.com>
- Cc: public-wsc-wg@w3.org
On 2008-01-17 10:20:21 -0800, Ian Fette wrote: > One who shall not be named? That sounds too much like something out of a > fantasy novel. "Don't speak Sarumon's name out loud, or you will draw his > attention!" And we're not trying to prevent the string from having a name > (as you just said that the user can assign an alias to the string), we're > preventing the text from being displayed and/or read aloud. > -My $0.02 Thanks for passing the attention test. :) > > I propose to replace section 7.6 [1] by the following text, to > > address ISSUE-125: > > > > Some text strings are of sufficiently high value that the > > risk of onlookers or bystanders evesdropping on the > > communication between machine and user is deemed > > unacceptable, e.g., in the case of a password displayed on a > > screen or read aloud by a screen reading tool. > > > > The text entry tool history menu MUST provide a means for > > the user to mark a text string as one who shall not be > > named. Invoking this function MUST enable the user to ... to mark a text string as sensitive. > > assign an alias to this string, which can then be used in > > subsequent interactions with the safe form editor. > > > > 1. http://www.w3.org/TR/wsc-xit/#safebar-onscreenmask > > > > Regards, > > -- > > Thomas Roessler, W3C <tlr@w3.org> > > > > -- Thomas Roessler, W3C <tlr@w3.org>
Received on Thursday, 17 January 2008 18:26:09 UTC