Bug 845862 - Transitively apply waivers for accessor descriptors. r=mrbkap
Bug 843829 - Fix incorrect test. r=mrbkap

This wasn't actually testing anything, because |is| is defined in the scope of
the content, so by passing the objects as arguments, we end up re-wrapping them
in the content scope, where the distinction between waived and non-waived
objects doesn't exist.

We're actually just about to remove this test in the next patch, but I wanted
to make it correct first. :-)
Bug 843829 - Apply transitive waivers for nativeCall. r=mrbkap
Bug 843829 - Stop using IsTransparent for XBL field access, and explicitly waive instead. r=mrbkap
Bug 843829 - Explicitly add a waiver in FieldGetter and FieldSetter. r=mrbkap
Bug 843829 - Wrap unwaived content JS objects in opaque wrappers for XBL scopes. r=mrbkap
Bug 843829 - Convert XUL mochitest to a chrome test. r=me

This is testing a XUL element that could never exist in content, and so its
XBL implementation isn't set up to deal with the bound element potentially
being in a less-privileged scope. This means that the call to
appendNotification here ends up passing in an unprivileged object as the
|aButtons| argument (see notification.xml), which we now wrap with an opaque
wrapper.

The whole situation here is totally artification and an artifact of our
automation infrastructure. Now that we have mochitest-chrome, this should
certainly be switched.