<div>sorry for joining late but couple from me:</div>
<ul>
<li> as an RP when using a popup for login, I prefer knowing the smallest possible window size that the OP can support before hand so I can set the window size accordingly without any assumptions or guesses. So I vote for OP declaring the dimensions of it's "popup" type window in it's XRDS so I know what width and height I should be setting when a user wants to use that OP to login. That makes it possible for the OP to change the size of the popup in future without requiring all RPs to make code changes too.</li>
<li>-1 for allowing OP to resize the window - though it's possible programmatically, it leaves bad user experience as focus will be changed to the popup and if the window resizes after loading the page (because the JS has to load) it looks odd IMO (almost like those popup ads)</li>
<li>Section4: looks like a typo - it says "When requesting OpenID authentication using the <strong>checkid_immediate</strong> mode, the Relying Party MUST " - I beleive you meant "When requesting OpenID authentication using the <strong>checkid_setup</strong> mode, the Relying Party MUST ". Probably worth mentioning this extension doens't apply for checkid_immediate mode at all.</li>
<li>+1 for adding a recommendation for the RP to dim the contents of the parent window while the popup is active and also to provide a status message ("please complete login from the popup window...." or so ) with a "cancel login" and/or "use standard login" options so if the popup doesn't show up or work the way we wanted (since it's JS in a browser - too many possibilities for it to go wrong), the user has an alternative way</li>
<li>Section2: I would suggest to remove this "Another optimization is that the OP can close the popup, rather than returning a negative assertion if the user choses cancel the authentication request. " - if a user cancels out of login, then it will be helpful for the RP to know that so it can take some action (for example, if the RP is using something like an IDSelector, it can remove or move down the OP button in the list or show other login options to the user for that session). </li>
</ul>
<div>Not sure if it has been discussed at the UX summit last week, but it might be useful for the RP to specify a user-friendly name in it's XRDS file that the OP can use in addition to the realm in the login page. This will be particularly useful when a user tries to login with multiple RPs on the same domain (just a hypothetical example: <a href="http://mail.aol.com">mail.aol.com</a>, <a href="http://pictures.aol.com">pictures.aol.com</a>, <a href="http://journals.aol.com">journals.aol.com</a>, etc..) at the same time using same OP and all popups look exactly same.</div>
<div> </div>
<div> </div>
<div> </div>
<div class="gmail_quote">On Sun, Feb 15, 2009 at 5:10 PM, Allen Tom <span dir="ltr"><<a href="mailto:atom@yahoo-inc.com">atom@yahoo-inc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div text="#000000" bgcolor="#ffffff">
<div class="Ih2E3d">Breno wrote:<br>
<blockquote type="cite">
<div class="gmail_quote">
<div><br></div>
<div>Ok. In the interest of expediency, we could at this point define only ui.mode=popup which is extensible in principle without introducing any new other use cases at the present.</div>
<div> </div></div></blockquote><br></div>OK, let's just agree that mode=popup implies 450x500, and there may be other modes defined in the future.<br><br>Will this work for your mobile users? The puffypoodles example looks good on my iphone, so I'm thinking that we'll just use mode=popup for desktop browsers and for advanced smartphones.
<div class="Ih2E3d"><br><br><br><br>
<blockquote type="cite">
<div class="gmail_quote">
<div><br></div>
<div>I agree that we shouldn't have too much going on simultaneously with the popup. However, it may prove useful for the RP to provide some context "before the popup opens and the RP screen goes dim".</div>
</div></blockquote></div>We can add some text that describes this, however I'm not sure if this is really necessary, and could just make the overall experience heavier and wordier.
<div class="Ih2E3d"><br><br>
<blockquote type="cite">
<div class="gmail_quote">
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<div text="#000000" bgcolor="#ffffff">
<div><br><br>
<blockquote 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></div>Ah, I hadn't thought of this case. </div></blockquote>
<div><br></div>
<div>This can be addressed as follows:</div>
<div><br></div>
<div>When the user completes the authentication and is returned at the RP, the RP should proceed as follows:</div>
<div><br></div>
<div>Check if window.opener.location is defined and within its realm. If so, it should close the popup after ensure that all side-effects (set cookies, etc) that follow the login operation have completed.<br></div>
<div><br></div>
<div>If window.opener.location is not defined, not accessible (attempt to read it throws a security exception, for instance) or not recognized to be part of the RP's site, then the RP should try to load its normal landing page for full-page redirects.</div>
<div> </div></div></blockquote></div>Sounds good!<br><font color="#888888"><br>Allen</font>
<div class="Ih2E3d"><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></div></div><br></blockquote></div><br>