[OpenID] UI extension... useful with popup blockers?

[Andrew Arnott]

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.
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.

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.

Has anyone else run into this issue?  Are there any workarounds or
approaches I'm not seeing?

Thanks.
--
Andrew Arnott
"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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20090615/08a3821f/attachment.htm>