This thread feels great. The only objection I've seen is that the complexity of the proposed bits in web content is insufficient to justify the change. I don't really agree with that, especially when you consider all of the devices we have to support and natural version fragmentation.
So I'm going to claim a decision has been made here. We'll build a container to handle authentication screens but not management. afaik, zcarter is already wiring up the existing user tested mocks to interact with the account server, and we'll be able to integrate it. From the "client implementation" team side, it means we need to craft a container that we can put this content in as one of our first jobs. Patches coming your way this week. If anyone wants to help, inquire within. Obviously, if once implemented there are clear reasons to make the additional investment and make the thing native, we can go there. good? lloyd On Aug 9, 2013, at 7:01 PM, 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. > > <snip> > >> Is there any really good reason not to explore this option? > > Technical question. IIUC, the Persona shim stores private user details in > localStorage (and in persona.org cookies). What happens when the user clears > local data? It's my belief that Persona just expects you to re-authenticate > to the email address you entered. If my understanding is correct, we'll need > to be more durable than that: we can't forget the user's account and we can't > expect re-auth. So that means the UI shim can't be authoritative for this > data. > > 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
