<p>Discovery documents are cacheable, so one solution is to issue the small size to all OPs that you know in advance to support it. </p>
<p>This strategy interacts well with other optimizations. For instance, if there is a persistent cookie indicating the user's OP choice, discovery can also happen prior to page load. </p>
<p>If you have an email- or URL based form entry you need to make an AJAX request to look up the provider. Then I suggest you show the button then. That requires the same number of clicks (the AJAX lookup does not require a click for activation, it can send individual characters as they are typed, or be activated on <enter>, <tab>, etc.</p>
<p>The point here is that discovery needs to happen prior to button display.</p>
<p><blockquote type="cite">On Jun 15, 2009 10:08 PM, "Andrew Arnott" <<a href="mailto:andrewarnott@gmail.com">andrewarnott@gmail.com</a>> wrote:<br><br>How can an RP leverage the UI extension? They must perform discovery on the Identifier in order to find out if the OP supports the UI extension. But if discovery comes between the user click and the popup window (via AJAX to the RP server) then popup blockers generally keep the popup from ever coming up. And if the user click causes a POST to the RP server itself, which then performs discovery and sends a new page to the user agent with a script to popup the OP window, then again popup blockers will knock it out. <div>
<br></div><div>For popup login to work with OpenID, the popup window must come up immediately after the user types in their identifier (i.e. before discovery takes place), so the dimensions of the window cannot be based on whether the OP supports the UI extension or not.</div>
<div><br></div><div>This is too bad because I've got an RP that's using popup windows already... but because most OPs aren't prepared to render in a small window as defined by the UI spec, the window is pretty large. I don't want to shrink it down to UI extension size unless identifier discovery suggests the OP will be able to handle it... but by the time discovery occurs the window must already be popped up.</div>
<div><br></div><div>Has anyone else run into this issue? Are there any workarounds or approaches I'm not seeing?</div><div><br></div><div>Thanks.<br clear="all">--<br>Andrew Arnott<br>"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre<br>
</div>
<br>_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@openid.net">general@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><br>
<br></blockquote></p>