Re: mochitest-plain and e10s OOP tabs

On 12/1/09 4:07 PM, Jonathan Griffin wrote:

> UniversalXPConnect (mostly for managing preferences and initiating
> events using EventUtils.js), and these tests all fail with the message
> "A script from http://localhost:8888 was denied UniveralXPConnect
> privileges."
>
> Can someone confirm that this will remain the case, and that content
> will not be able use XPConnect in an e10s world?

Well, we would like to remove the .enablePrivilege API altogether, but not 
as part of e10s. universalxpconnect should still  be available, if the right 
preferences are set. What's happening here is that mochitest is setting 
preferences (in the profile) which only apply to the chrome process. The 
content process doesn't have a profile, and therefore doesn't load the prefs.

This will eventually be solved by bug 506269. However, note that the 
environment that universalxpconnect gives you will be very different. For 
instance, you will be able to *read* preferences, but not to write them.

> If so, I propose to deal with this by moving the affected tests (~370 of
> them) to mochitest-chrome. There are possibly other ways to deal with
> this, but this seems to be the most efficient fix.

This sounds reasonable to me. If we can remove .enablePrivilege from our 
automated tests, that makes it much easier to remove it as an API altogether.

--BDS