[step2] Re: OpenID Popup Extension - Draft 0

Breno breno.demedeiros at gmail.com
Sun Feb 15 22:10:50 UTC 2009


On Sun, Feb 15, 2009 at 10:57 AM, Allen Tom <atom at yahoo-inc.com> wrote:

>  Breno wrote:
>
> Yes, I agree that we do not need to send the window geometry in the
> request. This can be auto-detected by the OP.
>
> The downside is the JS has to load first.
>
>  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.
>
>  If matching "Type" in URLs was restricted to the path component, we could
> have
>
>  <Type>http://.../popup?width=450&height=550</Type>
>
>  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:
>  <Type>http://.../popup</Type>
>  <Type>http://.../popup?width=450&height=550</Type>
>
>  Or more generally (if the OP provides a choice of configurations):
>
>  <Type>http://.../popup</Type>
>  <Type>http://.../popup?width=450&height=550</Type>
> <Type>http://.../popup?width=300&height=400</Type>
>
>   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.
>
>  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.
>
> 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.
>
> http://yadis.org/wiki/Yadis_1.0_(HTML)
>
> 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.
>

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.


>
>
> Allen
>
>
>
>  On Sat, Feb 14, 2009 at 9:59 AM, Dirk Balfanz <dirk.balfanz at gmail.com>wrote:
>
>>
>> Hi Allen,
>>
>> thanks for putting this together. Two comments:
>>
>> (1) Why are the height and width sent in the request? Isn't the OP
>> gonna know how big its popup window is (window.innerWidth and
>> window.innerHeight)?
>> (2) Can we kill two birds with one stone here and make this the UX (as
>> opposed to popup) extension, and add stuff like language?
>>
>> Something like this:
>>
>> openid.ns.ux = http://specs.openid.net/extensions/ux/1.0
>> openid.ux.style = popup
>> openid.ux.language = en_NZ
>>
>> What do you think?
>>
>> Dirk.
>>
>> On Fri, Feb 13, 2009 at 7:51 PM, Allen Tom <atom at yahoo-inc.com> wrote:
>> >
>> > I uploaded draft #0. Comments welcome:
>> >
>> > http://wiki.openid.net/f/openid_popup_extension_draft0.html
>> >
>> > I was really hoping to make the OP's default popup size discoverable,
>> > but I couldn't figure out how to cleanly embed the dimensions into the
>> > XRDS. Based on discussions at the Facebook meetup this week, it sounds
>> > like 450px width is the magic size, as both Google and Facebook
>> > independently chose 450px for their popups. My designers have indicated
>> > that 450x500 should be doable, so I've set that as the recommended size.
>> >
>> >  From a implementation standpoint, having the default popup size be
>> > discoverable might not be worth the added complexity.
>> >
>> > Based on the PuffyPoodles and MadStreams demos, it looks like the popup
>> > is already working well with iPhones, so perhaps we can just recommend
>> > that RPs just use the Popup UX for mobile devices as well as for
>> desktops.
>> >
>> > Allen
>> >
>> >
>> > >
>> >
>>
>>
>>
>
>
> --
> Breno de Medeiros
>
>
>
>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "Step2" group.
> To post to this group, send email to step2 at googlegroups.com
> To unsubscribe from this group, send email to
> step2+unsubscribe at googlegroups.com <step2%2Bunsubscribe at googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/step2?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>


-- 
Breno de Medeiros
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-user-experience/attachments/20090215/9828588d/attachment-0002.htm>


More information about the user-experience mailing list