On Aug 13, 2013, at 2:49 AM, Nick Alexander <[email protected]> wrote:
> On 13-08-09 7:31 AM, Lloyd Hilaiel wrote: >> Chris Karlof and I were talking yesterday, and I was noting how awesome the >> implementation approach of Persona on FirefoxOS has been. The, the relevant >> code that ships with the device is limited to a container capable of running >> web content, and some setup code which invokes a function within the context >> of that web content when necessary. Further, the navigator.id. apis are >> intercepted by firefoxos, and cause raising of the "trusted" content window >> and relaying parameters into it. > > Just to fan the flames, I've posted an Android stub wrapper with the jelly > injected from > > http://idp-mocks.lcip.org/flow. > > See the (trivial) patch and screen shots at > > https://bugzilla.mozilla.org/show_bug.cgi?id=899217 Another trivial patch, this time on the desktop side. I followed Nick's lead, got an education from mfinkle, and this is basically an excuse for me to re-learn firefox development: https://bugzilla.mozilla.org/show_bug.cgi?id=904612 Given all the strong feelings on the list, I'm certainly not dogmatic here. But from where I sit it seems like having a short term milestone of having authentication fully functional with jelly will very well box the work required to implement auth natively when we want to. In walking through Nick's patch and translating to desktop, many small design questions arose that we'll have to work through. The remaining work would really be to get the mock fully wired up (zaach's working on this), which has a nice side benefit of verifying that the API is complete, and another nice side benefit of giving UX folks something they can continue to user test and refine. One other interesting bit is I touched base with Crystal, and she pointed me to the browser.preferences.incontent pref in nightly. Apparently there's a move to eliminate the prefs popup [1]. This is mostly orthogonal to the native vs. content discussion going on, cause the prefs will still be implemented in xul, they'll just occupy the content area. But I did find this bit of context interesting. Mark & Gavin - Do you guys want to pursue this path as a way to get a functional auth implementation working, or skip this step and move straight to native. Your call. lloyd [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=718011 > Best, > Nick > > _______________________________________________ > Sync-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/sync-dev
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
