<br><br><div class="gmail_quote">On Sun, Feb 15, 2009 at 10:57 AM, 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="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000"><div class="Ih2E3d">
Breno wrote:
<blockquote type="cite">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>
</blockquote></div>
The downside is the JS has to load first.<div class="Ih2E3d"><br>
<br>
<blockquote type="cite">
<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><a href="http://.../popup?width=450&height=550" target="_blank">http://.../popup?width=450&height=550</a></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><a href="http://.../popup" target="_blank">http://.../popup</a></Type> </div>
<div>
<div><Type><a href="http://.../popup?width=450&height=550" target="_blank">http://.../popup?width=450&height=550</a></Type></div>
<div><br>
</div>
<div>Or more generally (if the OP provides a choice of
configurations):</div>
<div><br>
</div>
<div>
<div><Type><a href="http://.../popup" target="_blank">http://.../popup</a></Type> </div>
<div>
<div><Type><a href="http://.../popup?width=450&height=550" target="_blank">http://.../popup?width=450&height=550</a></Type></div>
<div><Type><a href="http://.../popup?width=300&height=400" target="_blank">http://.../popup?width=300&height=400</a></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>
</blockquote></div>
I would like to be able to have OPs publish their default popup size
(or advertise their available sizes), and to make the extension future
proofed to support new popup form factors, however this could just add
to the complexity without adding much short term benefit. There is
also a short term benefit of having a consistent popup size across all
OPs to make the overall experience similar across OPs.<br>
<br>
At the very end of the Yadis spec there's mention of an elemement
called a "complex type" but I have not seen any examples of that used
in OpenID. <br>
<br>
<a href="http://yadis.org/wiki/Yadis_1.0_(HTML)" target="_blank">http://yadis.org/wiki/Yadis_1.0_(HTML)</a><br>
<br>
I am fine with adding Breno's suggestion for listing the available
popup sizesas additional <Types> using the base popup extension
url followed with the dimensions as query params. It seems a little
hackish though, but it'll work and it seems straightforward.</div></blockquote><div><br></div><div>I agree that it is hackish, but I couldn't think of anything else. I also do not think that the "complex type" of YADIS is not being used by OpenID. Maybe this will be addressed better in the new XRD format being discussed by the XRI TC.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor="#ffffff" text="#000000"><br>
<br>
Allen<br>
<br>
<br>
<br>
<blockquote type="cite">
<div><div><div></div><div class="Wj3C7c">
<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" target="_blank">dirk.balfanz@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"><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><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>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br></div></div>
Breno de Medeiros<br>
<br>
</div>
<br>
<br>
</blockquote><div class="Ih2E3d">
<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><br clear="all"><br>-- <br>Breno de Medeiros<br><br>