On Aug 10, 2013, at 4:39 PM, Gavin Sharp <[email protected]> wrote:
> I'm assuming we're talking about all of the screens on > http://people.mozilla.com/~zfang/FirefoxAccount/PiCL_0710.pdf > excluding "manage account" and "sign out". > > Using existing web content for that seems like a good idea to me. > Getting the chrome/content interaction right (for the fundamentals > like "make auth work", but also for more trivial stuff like "make > Privacy Policy link behave correctly" and "update syncing state on the > reset password success page") will certainly push this beyond "just > raise a container" in terms of complexity, but it's likely overall > simpler than building a custom UI (and it has the other benefits you > mention). > > Gavin > Good point. I still need to walk through all the UI flows in conjunction with the API calls to identify some of those subtleties. -chris _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
