[Wg-ulx] Is a login button in scope?

[Paul Trevithick]

Now that I¹ve seen a couple examples of identity-enabled browsers (browsers
with add-ons) having login buttons in the chrome...



...I wonder if we should design a regular (non-chrome) login button for the
unmodified browser case.

Why? 

1. Consistency & familiarity. If we designed a login button that sites could
use on their web pages and that was visually similar to the login button in
the chrome, then one would reinforce the other. The user would hopefully say
to themselves ³oh, I get it. It doesn¹t matter whether it¹s in the chrome or
on the page it does basically the same thing; it logs me in².
2. Reducing confusion. If we had a regular login button, then
identity-enabled browsers could parse the web page, find the ³regular²
button, and do something smart with it. Like maybe:
> * Grey it out. And if you click instead of the login button in the chrome that
> you were supposed to click use this as a teaching moment: have a little bit of
> text pop up and explain that you¹ll have a better experience click the one in
> the chrome. 
> * Hide it. [Mozilla weave used to do this with OpenID text fields]. Of course,
> hiding widgets is considered heretical by many.
> * Hook it. The id-enabled browser could hook the form submit event and
> automatically do the same thing as if you had clicked the chrome login button.

Besides, it seems like some kind of custom-designed login (more often called
³Sign in²) button/link is really popular:
> 
> BestBuy: 
> Amazon: 
> Oracle: 
> 
> Ohio State University: [well okay they don¹t have one on the home page]
> 
> New York Times: 

So if we designed one, we¹d just be offering up a ³standardized² icon for
this function as our recommended ³best practice² if indeed this is what we
decide.

Reactions?

--Paul




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kantarainitiative.org/pipermail/wg-ulx/attachments/20091130/a508b69c/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 10207 bytes
Desc: not available
Url : http://kantarainitiative.org/pipermail/wg-ulx/attachments/20091130/a508b69c/attachment-0005.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 12929 bytes
Desc: not available
Url : http://kantarainitiative.org/pipermail/wg-ulx/attachments/20091130/a508b69c/attachment-0006.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 11342 bytes
Desc: not available
Url : http://kantarainitiative.org/pipermail/wg-ulx/attachments/20091130/a508b69c/attachment-0007.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 7510 bytes
Desc: not available
Url : http://kantarainitiative.org/pipermail/wg-ulx/attachments/20091130/a508b69c/attachment-0008.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 7335 bytes
Desc: not available
Url : http://kantarainitiative.org/pipermail/wg-ulx/attachments/20091130/a508b69c/attachment-0009.png