Closed
Bug 833392
Opened 11 years ago
Closed 11 years ago
Send RP ID within mozChromeEvents
Categories
(Core Graveyard :: Identity, defect)
Tracking
(blocking-b2g:tef+, firefox19 wontfix, firefox20 wontfix, firefox21 fixed, b2g18 fixed, b2g18-v1.0.0 fixed)
People
(Reporter: ferjm, Assigned: ferjm)
References
Details
(Whiteboard: [qa-])
Attachments
(1 file)
1.54 KB,
patch
|
jedp
:
review+
|
Details | Diff | Splinter Review |
This is the identity counterpart of Bug 832951. More info at https://bugzilla.mozilla.org/show_bug.cgi?id=832948#c0
Assignee | ||
Updated•11 years ago
|
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #704964 -
Flags: review?(jparsons)
Assignee | ||
Comment 2•11 years ago
|
||
Comment on attachment 704964 [details] [diff] [review] v1 Review of attachment 704964 [details] [diff] [review]: ----------------------------------------------------------------- ::: b2g/components/SignInToWebsite.jsm @@ +180,5 @@ > let detail = { > type: kReceivedIdentityAssertion, > showUI: aGaiaOptions.showUI || false, > + id: kReceivedIdentityAssertion + "-" + uuid, > + requestId: aRpOptions.id oops, white space, I'll remove it from the final version.
Comment 3•11 years ago
|
||
Comment on attachment 704964 [details] [diff] [review] v1 r=me! And the corresponding gaia patch is lovely. As soon as this lands, we can go ahead and merge that. Thanks for your work on this, j
Attachment #704964 -
Flags: review?(jparsons) → review+
Comment 4•11 years ago
|
||
Triage is a bit puzzled on this one. Can this actually reproduce with our v1 requirements? We only have one payment flow for v1. How would I reproduce this with our existing v1 constraints? Can you explain a bit more?
Flags: needinfo?(ferjmoreno)
Assignee | ||
Comment 5•11 years ago
|
||
This bug is a dependency for bug 832948 so the same reply at https://bugzilla.mozilla.org/show_bug.cgi?id=832948#c8 applies here.
Flags: needinfo?(ferjmoreno)
Assignee | ||
Comment 6•11 years ago
|
||
Thanks Jed! https://hg.mozilla.org/integration/mozilla-inbound/rev/61f5684286e6
Updated•11 years ago
|
blocking-b2g: tef? → tef+
Comment 7•11 years ago
|
||
I see the counterpart bug 832951 has already landed in b2g18. Do we need to set any additional flags on this for it to get the same treatment?
Keywords: checkin-needed
Assignee | ||
Comment 8•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g18/rev/491dd35f1ca8
Keywords: checkin-needed
Updated•11 years ago
|
status-b2g18:
--- → fixed
status-firefox19:
--- → wontfix
status-firefox20:
--- → wontfix
status-firefox21:
--- → fixed
Target Milestone: --- → mozilla21
Comment 9•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/61f5684286e6
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Whiteboard: [qa-]
Comment 10•11 years ago
|
||
Landed on mozilla-b2g18/gaia master prior to the 1/25 branching to mozilla-b2g18_v1_0_0/v1.0.0, updating status-b2g-v1.0.0 to fixed.
status-b2g18-v1.0.0:
--- → fixed
Updated•5 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•