- From: Thomas Roessler <tlr@w3.org>
- Date: Wed, 26 Mar 2008 09:24:38 +0100
- To: "Close, Tyler J." <tyler.close@hp.com>
- Cc: "mzurko@us.ibm.com" <mzurko@us.ibm.com>, "public-wsc-wg@w3.org" <public-wsc-wg@w3.org>
On 2008-03-20 16:47:39 +0000, Close, Tyler J. wrote: > Current browsers support creating a bookmark with a single button > press, or keystroke, and no further user interaction. The > hypertext for the bookmark is chosen by the visited page, as > expressed by the HTML TITLE element. Consequently, it is very > easy for a blog post to get itself bookmarked in my browser under > the name "bank account". The next time I go to use my "bank > account" bookmark to do some online banking, I may inadvertently > visit a blog post turned phishing site. > I think keeping the fast, one-click user action for bookmark > creation is important, so instead of working this problem from > the bookmark creation side, I'm going at it from the bookmark > lookup side. Conformance text follows: Generalizing (maybe illegitimately) from my own usage of these features, I often use one-click bookmarking for stuff that's in the "keep that link around, somewhere" category. Things that I consider important, I typically want to have in my bookmark toolbar, and therefore I end up in a multi-click interaction in that case. Ironically, there are some self-signed and untrusted trust roots involved with these important sites; I would actually consider a petname extensio rather useful for them. (Though, actually, the display of certificate-related information that FX3 gives me when browser.identity.ssl_domain_display is activated is somewhat useful even in these situations...) > A web user agent that supports petnames MUST also support a > presentation of bookmarks that presents the association between > each bookmark and the petname of the hosting site. If the hosting > site could be assigned a petname, but the user has not yet done > so, the presentation MUST present those bookmarks as being > associated with a distinct, but not yet petnamed host. If the > hosting site cannot be assigned a petname, since the host does > not support the previously established constraints for assignment > of a petname, the presentation MUST indicate so. This bookmark > presentation MUST support assignment, renaming and deletion of > petnames. I'd love to understand better what you mean by that. Really an additional requirement on the bookmarks managers that typical browsers have? -- Thomas Roessler, W3C <tlr@w3.org>
Received on Wednesday, 26 March 2008 08:26:24 UTC