Closed
Bug 1055427
Opened 10 years ago
Closed 10 years ago
Create more direct way of killing apps than calling an invalid permissions assert
Categories
(Core Graveyard :: DOM: Apps, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla34
People
(Reporter: qdot, Assigned: tedders1)
References
Details
(Whiteboard: [systemsfe])
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
Right now, to do security kills on apps from the parent while in chrome js, we make up a stupid permission name and call assertPermission on it. We should just expose kill to chrome js.
Comment 1•10 years ago
|
||
I think Tedders did that in one his "privileged homescreen" patches.
Flags: needinfo?(tclancy)
Assignee | ||
Comment 2•10 years ago
|
||
Yeah, this patch is part of Bug 1000313, but we might as well land it right now.
Assignee: nobody → tclancy
Status: NEW → ASSIGNED
Flags: needinfo?(tclancy)
Assignee | ||
Comment 3•10 years ago
|
||
Successful TBPL run: https://tbpl.mozilla.org/?tree=Try&rev=0be7b43caf9e
Keywords: checkin-needed
Comment 4•10 years ago
|
||
Keywords: checkin-needed
Comment 5•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
Comment 6•10 years ago
|
||
This is currently causing Gij to go perma-red. We will either need to fix it tonight, or backout in conjunction with bug 1000315 and bug 1042797.
Depends on: 1058362
Updated•10 years ago
|
Whiteboard: [systemsfe]
Updated•7 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•