summaryrefslogtreecommitdiffstats
path: root/browser/components/customizableui/test/browser_reset_builtin_widget_currentArea.js
diff options
context:
space:
mode:
Diffstat (limited to 'browser/components/customizableui/test/browser_reset_builtin_widget_currentArea.js')
-rw-r--r--browser/components/customizableui/test/browser_reset_builtin_widget_currentArea.js26
1 files changed, 26 insertions, 0 deletions
diff --git a/browser/components/customizableui/test/browser_reset_builtin_widget_currentArea.js b/browser/components/customizableui/test/browser_reset_builtin_widget_currentArea.js
new file mode 100644
index 0000000000..fa9e497734
--- /dev/null
+++ b/browser/components/customizableui/test/browser_reset_builtin_widget_currentArea.js
@@ -0,0 +1,26 @@
+/* Any copyright is dedicated to the Public Domain.
+ * https://creativecommons.org/publicdomain/zero/1.0/ */
+
+"use strict";
+
+// Check that if we move a non-default, but builtin, widget to another area,
+// and then reset things, the currentArea is updated correctly.
+add_task(async function reset_should_not_keep_currentArea() {
+ CustomizableUI.addWidgetToArea(
+ "save-page-button",
+ CustomizableUI.AREA_FIXED_OVERFLOW_PANEL
+ );
+ // We can't check currentArea directly; check areaType which is based on it:
+ is(
+ CustomizableUI.getWidget("save-page-button").areaType,
+ CustomizableUI.TYPE_PANEL,
+ "Button should know it's in the overflow panel"
+ );
+ CustomizableUI.reset();
+ ok(
+ !CustomizableUI.getWidget("save-page-button").areaType,
+ "Button should know it's not in the overflow panel anymore"
+ );
+});
+
+registerCleanupFunction(() => CustomizableUI.reset());