зеркало из https://github.com/mozilla/gecko-dev.git
Bug 1577180 - Get a profile before accessing BrowserGlue in test_getPotentialBreachesByLoginGUID.js. r=jaws
I'm not sure of the exact cause since that would require doing a local Windows beta build and the getService error doesn't indicate what failed inside the component. I mostly guessed that this was the problem by looking at other tests which do the same thing. Differential Revision: https://phabricator.services.mozilla.com/D43899 --HG-- extra : moz-landing-system : lando
This commit is contained in:
Родитель
7a0e27bfdd
Коммит
1faa130d15
|
@ -8,6 +8,10 @@ const { RemoteSettings } = ChromeUtils.import(
|
||||||
"resource://services-settings/remote-settings.js"
|
"resource://services-settings/remote-settings.js"
|
||||||
);
|
);
|
||||||
const { Services } = ChromeUtils.import("resource://gre/modules/Services.jsm");
|
const { Services } = ChromeUtils.import("resource://gre/modules/Services.jsm");
|
||||||
|
|
||||||
|
// Initializing BrowserGlue requires a profile on Windows.
|
||||||
|
do_get_profile();
|
||||||
|
|
||||||
const gBrowserGlue = Cc["@mozilla.org/browser/browserglue;1"].getService(
|
const gBrowserGlue = Cc["@mozilla.org/browser/browserglue;1"].getService(
|
||||||
Ci.nsIObserver
|
Ci.nsIObserver
|
||||||
);
|
);
|
||||||
|
|
Загрузка…
Ссылка в новой задаче