Create more direct way of killing apps than calling an invalid permissions assert

RESOLVED FIXED in mozilla34

Status

defect
RESOLVED FIXED
5 years ago
2 years ago

People

(Reporter: qdot, Assigned: tedders1)

Tracking

unspecified
mozilla34
x86_64
Linux
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [systemsfe])

Attachments

(1 attachment)

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.
I think Tedders did that in one his "privileged homescreen" patches.
Flags: needinfo?(tclancy)
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)
https://hg.mozilla.org/mozilla-central/rev/4b37cddaed77
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
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
Whiteboard: [systemsfe]
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.