Closed Bug 462483 Opened 16 years ago Closed 5 years ago

Eliminate use of enablePrivilege in mochitest

Categories

(Testing :: Mochitest, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bzbarsky, Unassigned)

References

(Blocks 1 open bug)

Details

As discussed in today's meeting, we want to nuke enablePrivilege from orbit.  This means that we need a different solution for mochitests.  Some of these should probably just be chrome tests.  For others we were considering exposing some sort of global object that can be used to evaluate privileged code (especially including EventUtils stuff) or something.
Component: Testing → Mochitest
Product: Core → Testing
QA Contact: testing → mochitest
Version: Trunk → unspecified
I think if we could provide a privileged object with test-only APIs that we could hack whatever we needed into it (like most of the helpers in SimpleTest.js), we would not need any privileged code in tests.
Depends on: 533306
Blocks: 546848
bug 523896 would be a great way to fix this, IMO.
Assignee: benjamin → ted.mielczarek
Depends on: 523896
No longer depends on: 533306
No longer depends on: 523896
For the record, since this bug hasn't been updated in a year, bug 582472 added a "SpecialPowers" object that has privileges, and we're going to add a bunch of APIs to it and fix all the tests. Bugs blocking this one will track that work.
Depends on: 621362
Depends on: 649124
Depends on: 649563
Depends on: 653145
Depends on: 508710
Depends on: 451630
Depends on: 657973
Depends on: 659263
Depends on: 659315
Depends on: 659338
Depends on: 659341
Blocks: 429070
Depends on: 750638
No longer depends on: 750638
Depends on: 750638
Depends on: 791975
Depends on: 844505
No longer depends on: 645695
Depends on: 871323
Depends on: 1149966
No longer depends on: 659341
No longer depends on: 649563
No longer depends on: 451630
Depends on: 1365199
Assignee: ted → nobody
Blocks: 1448967

We've already done.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.