Replace use of services/aitc/modules/browserid.js with Identity.jsm from bug 753238 when it is ready!
Could you explain the importance of this? Just wondering if this is a k9o nom or not, given that the dependency got a +.
Yes, please nom for k9o. This significantly improves the login UX for AITC.
Is this purely backend? Or is it about making AITC's UX consistent with the native Persona support? (implies - for the former, + for the latter).
jsmith_ anant: Could you give some more background behind why bug 767220 is important? anant jsmith_: in bug 745345, we promised gavin that we'd move over to the native ID implementation as soon as possible, and that's what 767220. Using the native ID module instead of the in-built BrowserID module will result in a better user experience for AITC logins anant err, *that's what 767220 tracks jsmith_ anant: Okay. Could you explain more on the UX side? Like how does the end-user benefit from this? anant jsmith_: so right now you get the ugly popup when visiting the dashboard. with native ID integration, we'll get a nice doorhanger login with explicit login/logout buttons etc. jsmith_ anant: Oh, that sounds far more plesant
jsmith_ anant: So this falls in line with making the UX consistent with native persona support, right (as Dolske put it)? anant that's exactly what the bug is about, integration with native persona support jsmith_ anant: Gotcha
(In reply to Justin Dolske [:Dolske] from comment #3) > Is this purely backend? Or is it about making AITC's UX consistent with the > native Persona support? (implies - for the former, + for the latter). AITC's UX consistent with native Persona support
No longer depends on: 769519
OS: Mac OS X → All
Hardware: x86 → All
Summary: Use Identity.jsm for ID operations → Use Identity Module for WebApps ID operations
Dead component, closing bugs in it.
Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.