<br><br><div class="gmail_quote">On Sat, Feb 14, 2009 at 4:58 PM, Chris Messina <span dir="ltr"><<a href="mailto:chris.messina@gmail.com">chris.messina@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
A couple pieces of feedback.<br><br><div class="gmail_quote"><div class="Ih2E3d">On Sat, Feb 14, 2009 at 9:59 AM, Dirk Balfanz <span dir="ltr"><<a href="mailto:dirk.balfanz@gmail.com" target="_blank">dirk.balfanz@gmail.com</a>></span> wrote:<br>
</div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
(1) Why are the height and width sent in the request? Isn't the OP<br>
gonna know how big its popup window is (window.innerWidth and<br>
window.innerHeight)?</blockquote><div><br></div></div><div>+1. It seems to me that focusing on specific browser windows sizes in the request could limit the use of this part of the spec (see below).</div><div class="Ih2E3d">
<div> </div><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><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 class="Ih2E3d">
<div> </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>Something like this:<br>
<br>
openid.ns.ux = <a href="http://specs.openid.net/extensions/ux/1.0" target="_blank">http://specs.openid.net/extensions/ux/1.0</a><br>
openid.ux.style = popup<br>
openid.ux.language = en_NZ<br>
<br>
What do you think?</blockquote><div><br></div></div><div>Or like this:</div><div><br></div><div><span style="font-family: 'courier new',monospace;">openid.ns.ui = </span><a href="http://specs.openid.net/extensions/ux/1.0" target="_blank"><span style="font-family: 'courier new',monospace;">http://specs.openid.net/</span><span style="font-family: 'courier new',monospace;">extensions/ui/1.0</span></a><br>
<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>
<span style="font-family: 'courier new',monospace;">openid.ui.language = en_NZ</span></div></div></blockquote><div><br>+1. We can then just discuss recommendations for popup and if the need arises to establish best practices for other environments then this can be tackled in the future. So the extension is not any more complex, but has built-in extensibility.<br>
<br>Putting the language here also eliminates the need for a new WG/spec and a new namespace -> shorter URLs.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div><br></div><div><br></div><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 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>Should we also cover the case where the parent window is closed before authentication is completed?</div><div><br></div><div>Lastly, typo in Section 5: "recieving" should be "receiving".</div>
<div><br></div><div>Chris</div><div class="Ih2E3d"><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><br>
On Fri, Feb 13, 2009 at 7:51 PM, Allen Tom <<a href="mailto:atom@yahoo-inc.com" target="_blank">atom@yahoo-inc.com</a>> wrote:<br>
><br>
> I uploaded draft #0. Comments welcome:<br>
><br>
> <a 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 href="mailto:step2@googlegroups.com" target="_blank">step2@googlegroups.com</a><br>
To unsubscribe from this group, send email to <a href="mailto:step2%2Bunsubscribe@googlegroups.com" target="_blank">step2+unsubscribe@googlegroups.com</a><br>
For more options, visit this group at <a 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></div><font color="#888888"><br><br clear="all"><br>-- <br>Chris Messina<br>Citizen-Participant &<br> Open Web Advocate-at-Large<br><br><a href="http://factoryjoe.com" target="_blank">factoryjoe.com</a> # <a href="http://diso-project.org" target="_blank">diso-project.org</a><br>
<a href="http://citizenagency.com" target="_blank">citizenagency.com</a> # <a href="http://vidoop.com" target="_blank">vidoop.com</a><br>This email is: [ ] bloggable [X] ask first [ ] private<br>
</font><br>_______________________________________________<br>
user-experience mailing list<br>
<a href="mailto:user-experience@openid.net">user-experience@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/user-experience" target="_blank">http://openid.net/mailman/listinfo/user-experience</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>--Breno<br><br>+1 (650) 214-1007 desk<br>+1 (408) 212-0135 (Grand Central)<br>MTV-41-3 : 383-A <br>PST (GMT-8) / PDT(GMT-7)<br>