From af181e17f04d9b041aad7ec30fb233fca3a48031 Mon Sep 17 00:00:00 2001 From: Alexander Surkov Date: Mon, 22 Apr 2019 20:18:02 +0000 Subject: [PATCH] Bug 1519514 - make sure document.l10n is initialized before triggering conext menu over a tab in browser_ext_menus_activeTab.js test r=Gijs Differential Revision: https://phabricator.services.mozilla.com/D28366 --HG-- extra : moz-landing-system : lando --- .../extensions/test/browser/browser_ext_menus_activeTab.js | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/browser/components/extensions/test/browser/browser_ext_menus_activeTab.js b/browser/components/extensions/test/browser/browser_ext_menus_activeTab.js index 0066a9b3f2aa..f7ea876e4a17 100644 --- a/browser/components/extensions/test/browser/browser_ext_menus_activeTab.js +++ b/browser/components/extensions/test/browser/browser_ext_menus_activeTab.js @@ -39,6 +39,10 @@ async function openTwoTabsAndOpenTabMenu(onTabMenuClicked) { await extension.startup(); await extension.awaitMessage("ready"); + // Focus a selected tab to to make tabbrowser.js to load localization files, + // and thereby initialize document.l10n property. + gBrowser.selectedTab.focus(); + // The .tabbrowser-tab selector matches the first tab (tab1). let menu = await openChromeContextMenu("tabContextMenu", ".tabbrowser-tab", window); let menuItem = menu.getElementsByAttribute("label", "menu item on tab")[0];