Closed
Bug 775829
Opened 12 years ago
Closed 12 years ago
Updating browser id to use the new permission manager api
Categories
(Core Graveyard :: Identity, defect)
Core Graveyard
Identity
Tracking
(blocking-basecamp:+)
People
(Reporter: mounir, Assigned: mounir)
References
Details
(Whiteboard: [qa-])
Attachments
(1 file)
|
1.84 KB,
patch
|
sicking
:
review+
|
Details | Diff | Splinter Review |
Jonas, feel free to redirect the review to a BrowserID peer (if such thing exist) if you don't feel comfortable reviewing that.
Attachment #644152 -
Flags: review?(jonas)
Attachment #644152 -
Flags: review?(jonas) → review+
blocking-basecamp: --- → +
|
||
Comment 1•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/d60807c526a5
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
|
||
Comment 2•12 years ago
|
||
Mounir, Jonas: can you explain what this change does?
|
Assignee | |
Comment 3•12 years ago
|
||
Instead of using the permission manager using an URI, this code is using the permission manager using a principal, which carries more information than an URI. The idea is to have at some point, when all consumers of the permission manager will be changed, to have the permission manager using the principal's appid.
|
||
Updated•12 years ago
|
Whiteboard: [qa-]
|
||
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
•