<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Chris Messina wrote:<br>
<blockquote
cite="mid:1bc4603e0902141658x7321a4f9g1a1fe416a3f5ef16@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
(2) Can we kill two birds with one stone here and make this the UX (as<br>
opposed to popup) extension, and add stuff like language?</blockquote>
<div><br>
</div>
<div>If we're going that route (which I generally favor), I think we
should probably use UI as opposed to UX for the appropriate acronym.
Since we're talking about the superficial OpenID experience here
(rather than the holistic "user experience" -- which encompasses much
more than just language and window mode), I think this extension should
be called the OpenID User Interface Extension or OpenID Uniform User
Interface Experience. </div>
<div> </div>
</div>
</blockquote>
I'm concerned about increasing the scope of the extensions, as both the
Language Preference and PopupUX both seem to be very obvious
improvements with universal support that can be implemented very
rapidly by almost all OPs, so I would like to finalize both extensions
quickly and to keep the scope limited so that we can move forward.<br>
<br>
<blockquote
cite="mid:1bc4603e0902141658x7321a4f9g1a1fe416a3f5ef16@mail.gmail.com"
type="cite">
<div class="gmail_quote"><br>
<div><span class="Apple-style-span"
style="font-family: 'courier new',monospace;">openid.ns.ui = </span><a
moz-do-not-send="true" href="http://specs.openid.net/extensions/ux/1.0"
target="_blank"><span class="Apple-style-span"
style="font-family: 'courier new',monospace;">http://specs.openid.net/</span><span
class="Apple-style-span" style="font-family: 'courier new',monospace;">extensions/ui/1.0</span></a><br>
<span class="Apple-style-span"
style="font-family: 'courier new',monospace;">openid.ui.mode =
popup|aural|braille|embossed|handheld|mobile|tv</span> </div>
<div> (largely inherited from CSS media types, where "handheld" is
differentiated from "mobile" by the capability expectations of the
browser)<br>
</div>
</div>
</blockquote>
<br>
I fully agree that we should address multiple form factors and modes,
however I don't think there's an immediate short term need to formally
specify this.<br>
<br>
<blockquote
cite="mid:1bc4603e0902141658x7321a4f9g1a1fe416a3f5ef16@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div><span class="Apple-style-span"
style="font-family: 'courier new',monospace;">openid.ui.language =
en_NZ</span><br>
</div>
<div><br>
</div>
</div>
</blockquote>
I have no problem with combining the popup and the language extensions
into one, if there is consensus to do that. <br>
<br>
I do have a problem with expanding the scope to cover use cases that
have not really been discussed yet. (accessibility, TVs, etc)<br>
<br>
<br>
<br>
<blockquote
cite="mid:1bc4603e0902141658x7321a4f9g1a1fe416a3f5ef16@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div>Also, I might tweak this (section 4):</div>
<div><br>
</div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;"><span
class="Apple-style-span" style="font-family: verdana;">The RP SHOULD
open the popup centered above the main browser window, and SHOULD dim
the contents of the parent window while the popup is active.</span><br>
</blockquote>
<div> </div>
<div>...to suggest that if you DIM the contents of the parent window,
that you also provide an indication of what's happening and how to
cancel/escape the dimmed effect (i.e. if you close the popup and no
communication happens back to the parent).</div>
<div><br>
</div>
</div>
</blockquote>
My concern here is that the RP and the OP would both be competing for
the user's attention. I'd prefer that the user focus on the popup, and
that the OP take care of the messaging.<br>
<br>
<blockquote
cite="mid:1bc4603e0902141658x7321a4f9g1a1fe416a3f5ef16@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div>Should we also cover the case where the parent window is closed
before authentication is completed?</div>
<div><br>
</div>
</div>
</blockquote>
Ah, I hadn't thought of this case. <br>
<br>
<blockquote
cite="mid:1bc4603e0902141658x7321a4f9g1a1fe416a3f5ef16@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div>Lastly, typo in Section 5: "recieving" should be "receiving".</div>
<div><br>
</div>
</div>
</blockquote>
Thanks for pointing that, I'll take care of that in the next rev.<br>
<br>
Allen<br>
<br>
<br>
<br>
<blockquote
cite="mid:1bc4603e0902141658x7321a4f9g1a1fe416a3f5ef16@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div>Chris</div>
<div><br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div>
<div class="Wj3C7c"><br>
On Fri, Feb 13, 2009 at 7:51 PM, Allen Tom <<a moz-do-not-send="true"
href="mailto:atom@yahoo-inc.com">atom@yahoo-inc.com</a>> wrote:<br>
><br>
> I uploaded draft #0. Comments welcome:<br>
><br>
> <a moz-do-not-send="true"
href="http://wiki.openid.net/f/openid_popup_extension_draft0.html"
target="_blank">http://wiki.openid.net/f/openid_popup_extension_draft0.html</a><br>
><br>
> I was really hoping to make the OP's default popup size
discoverable,<br>
> but I couldn't figure out how to cleanly embed the dimensions into
the<br>
> XRDS. Based on discussions at the Facebook meetup this week, it
sounds<br>
> like 450px width is the magic size, as both Google and Facebook<br>
> independently chose 450px for their popups. My designers have
indicated<br>
> that 450x500 should be doable, so I've set that as the recommended
size.<br>
><br>
> From a implementation standpoint, having the default popup size be<br>
> discoverable might not be worth the added complexity.<br>
><br>
> Based on the PuffyPoodles and MadStreams demos, it looks like the
popup<br>
> is already working well with iPhones, so perhaps we can just
recommend<br>
> that RPs just use the Popup UX for mobile devices as well as for
desktops.<br>
><br>
> Allen<br>
><br>
><br>
> ><br>
><br>
<br>
--~--~---------~--~----~------------~-------~--~----~<br>
You received this message because you are subscribed to the Google
Groups "Step2" group.<br>
To post to this group, send email to <a moz-do-not-send="true"
href="mailto:step2@googlegroups.com">step2@googlegroups.com</a><br>
To unsubscribe from this group, send email to <a moz-do-not-send="true"
href="mailto:step2%2Bunsubscribe@googlegroups.com">step2+unsubscribe@googlegroups.com</a><br>
For more options, visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/step2?hl=en" target="_blank">http://groups.google.com/group/step2?hl=en</a><br>
-~----------~----~----~----~------~----~------~--~---<br>
<br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div> </div>
</div>
<br>
<br clear="all">
<br>
-- <br>
Chris Messina<br>
Citizen-Participant &<br>
Open Web Advocate-at-Large<br>
<br>
<a moz-do-not-send="true" href="http://factoryjoe.com">factoryjoe.com</a>
# <a moz-do-not-send="true" href="http://diso-project.org">diso-project.org</a><br>
<a moz-do-not-send="true" href="http://citizenagency.com">citizenagency.com</a>
# <a moz-do-not-send="true" href="http://vidoop.com">vidoop.com</a><br>
This email is: [ ] bloggable [X] ask first [ ] private<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
user-experience mailing list
<a class="moz-txt-link-abbreviated" href="mailto:user-experience@openid.net">user-experience@openid.net</a>
<a class="moz-txt-link-freetext" href="http://openid.net/mailman/listinfo/user-experience">http://openid.net/mailman/listinfo/user-experience</a>
</pre>
</blockquote>
<br>
</body>
</html>