Closed Bug 780223 Opened 14 years ago Closed 14 years ago

Switch to use navigator.id.watch()

Categories

(Marketplace Graveyard :: General, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED
2012-10-18

People

(Reporter: clouserw, Assigned: jrconlin)

References

Details

BrowserID is switching to navigator.id.watch() as their default recommended implementation. We want to use it as it adds functionality we need to work with bluevia (namely, them telling us who we are logged in as). Documentation is at: https://developer.mozilla.org/en-US/docs/DOM/navigator.id.watch The new call should completely replace the old call. :thunder or dcallahan can help with implementation questions.
Target Milestone: --- → 2012-08-09
Target Milestone: 2012-08-09 → 2012-08-16
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: 2012-08-16 → 2012-08-23
Reopening this bug. I'm seeing unusual behaviors with my test install that may be indicative of a bigger problem. Notably: * browserid_support.js not being loaded on some pages. * Browserid identity panel not always being displayed * After login, page seems to stall loading identity.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: 2012-08-23 → 2012-09-06
These fixes are being tracked in bug 789288 (and pull request already exists there). Closing since we don't need multiple bugs open for the same thing.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
I see that this was added to AMO (js/zamboni) but not Marketplace (js/mkt). We need it in the Marketplace: https://github.com/mozilla/zamboni/blob/master/media/js/mkt/browserid.js#L11 Sorry JR for confusing you by having two forks of the code :( That's a long sordid story.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: 2012-09-06 → 2012-10-11
JR is working with Kumar on this.
Target Milestone: 2012-10-11 → 2012-10-18
What's the status on this? I see that watch landed but maybe it needs some refinement?
I've checked the current master (as of 1400PDT 11/01) against my local builds. Login proceeds correctly, with the exception that developer login routes to "/". This appears to be the expected behavior since the "to" is set to "/" outside of my code being called. I've not tested the special admin accounts. The additional patches add a browserid middleware element to AMO user. Since it appears that MKT is not using that section of code, I've not pushed the additional code.
The developer strangeness is a different bug. Minor oddities aside is the main part of this bug (using .watch() on marketplace.m.o) done? If so, we can close it.
My apologies if i've not followed procedure. I'm used to QA verifying that the bug no longer exists and then closing. Since that doesn't appear to be the case here, I'll close it and presume QA will reopen if there's still an issue.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Thanks JR. We generally mark FIXED when we commit the change (with a link to the commit) and QA moves it from RESOLVED -> VERIFIED.
JR, could you also link to the commit that fixed it? We put revision links in the bug to make future spelunking easy. If there are more than one you can add the merge commit or whatever is easiest.
fix incorporated as part of fix for 789288: https://github.com/mozilla/zamboni/pull/457
You need to log in before you can comment on or make changes to this bug.