Yes, I agree that we do not need to send the window geometry in the request. This can be auto-detected by the OP.<div><br></div><div>It is more interesting to see if we can advertize the size of windows favored by the OP. For instance, we might want to have windows smaller than 450 for smart phones that are less screen state-rich than the iPhone.</div>
<div><br></div><div>If matching "Type" in URLs was restricted to the path component, we could have</div><div><br></div><div><Type>http://.../popup?width=450&height=550</Type> </div><div><br></div>
<div>in the OP's discovery document. Maybe we can declare that XRD parsing should match type ignoring query, and then for backward-compatibility, we could add two types:</div><div><div><Type>http://.../popup</Type> </div>
<div><div><Type>http://.../popup?width=450&height=550</Type></div><div><br></div><div>Or more generally (if the OP provides a choice of configurations):</div><div><br></div><div><div><Type>http://.../popup</Type> </div>
<div><div><Type>http://.../popup?width=450&height=550</Type></div><div><Type>http://.../popup?width=300&height=400</Type></div></div></div><div><br></div></div></div><div>This way, RPs using parsing libraries that only do exact string matching would still be able to discovery support of the feature, and may use the default recommended size, while RPs using libraries that match type only to the path could also extract the OP's supported geometries.<br>
<br><div class="gmail_quote">On Sat, Feb 14, 2009 at 9:59 AM, Dirk Balfanz <span dir="ltr"><<a href="mailto:dirk.balfanz@gmail.com">dirk.balfanz@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Hi Allen,<br>
<br>
thanks for putting this together. Two comments:<br>
<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)?<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?<br>
<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?<br>
<font color="#888888"><br>
Dirk.<br>
</font><div><div></div><div class="Wj3C7c"><br>
On Fri, Feb 13, 2009 at 7:51 PM, Allen Tom <<a href="mailto:atom@yahoo-inc.com">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">step2@googlegroups.com</a><br>
To unsubscribe from this group, send email to <a href="mailto:step2%2Bunsubscribe@googlegroups.com">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><br clear="all"><br>-- <br>Breno de Medeiros<br><br>
</div>