av9ash/GitBugs huggingface dataset:
Bug: [Experiment] The "Nightly" channel name is used instead of the "Firefox" one in the title of the default browser prompt notification
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-12-04 12:57:56+00:00
Resolved: 2024-12-05 15:56:44+00:00

**[Notes]:**
- This issue is reproducible only on Windows on MSIX and non-MSIX Firefox builds that are not pinned to the taskbar. If the browser is pinned to the taskbar the issue is not reproducible and the correct title is displayed. 

**[Affected versions]:**
- Firefox Beta 134.0b4 - Build ID: 20241202091515

**[Affected Platforms]:**
- Windows 10
- Windows 11

**[Prerequisites]:**
- Have a Firefox profile with the `nimbus.debug` pref set to `true` in the "about:config" page.
- Firefox is not pinned to the taskbar.
  
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to "about:studies?optin_slug=set-to-default-prompt-style-spotlight&optin_branch=treatment-a&optin_collection=nimbus-preview".
3. Restart the browser and observe the default browser prompt's title.

**[Expected result]:**
- The "Make Firefox your default browser?" title is displayed in the default browser prompt.
    
**[Actual result]:**
- The "Make Nightly your default browser?" title is displayed instead.

**[Additional Notes]:**
- This issue is not reproducible on macOS and Linux platforms.
- Attached a screenshot of the issue.
Bug: Uncontrolled connections
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-12-04 13:23:46+00:00
Resolved: 2024-12-05 13:27:24+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.6613.127 Safari/537.36

Steps to reproduce:

Start firefox with following policies.json

{
    "policies": {
        "AppAutoUpdate": false,
        "BackgroundAppUpdate": false,
        "DisableAppUpdate": true,
        "DisableFeedbackCommands": true,
        "DisableFirefoxAccounts": true,
        "DisableFirefoxStudies": true,
        "DisablePocket": true,
        "DisableSystemAddonUpdate": true,
        "DisableTelemetry": true,
        "ExtensionUpdate": false
    }
}


Actual results:

But uncontrolled connections to the following addresses continue anyway:
* firefox.settings.services.mozilla.com
* aus5.mozilla.org

There are thousands of options in the browser but there is no way to set up full control of outgoing connections on browser startup.


Expected results:

The ability to fully control all outgoing connections that are not related to user web requests.
Bug: Uncontrolled connections
Status: RESOLVED
Priority: P4
Resolution: WONTFIX
Created: 2024-12-04 13:43:03+00:00
Resolved: 2024-12-18 17:08:11+00:00

Steps to reproduce:

Start firefox with following policies.json

```
{
    "policies": {
        "AppAutoUpdate": false,
        "BackgroundAppUpdate": false,
        "DisableAppUpdate": true,
        "DisableFeedbackCommands": true,
        "DisableFirefoxAccounts": true,
        "DisableFirefoxStudies": true,
        "DisablePocket": true,
        "DisableSystemAddonUpdate": true,
        "DisableTelemetry": true,
        "ExtensionUpdate": false
    }
}
```


Actual results:

But uncontrolled connections to the following addresses continue anyway:
* firefox.settings.services.mozilla.com
* aus5.mozilla.org

There are thousands of options in the browser but there is no way to set up full control of outgoing connections on browser startup.


Expected results:

The ability to fully control all outgoing connections that are not related to user web requests.
Bug: Secondary button in the Firefox View Discoverability panel is missing accessible name and haspopup and state indications
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2024-12-04 21:18:07+00:00
Resolved: 2025-03-05 11:56:14+00:00

The FX_VIEW_DISCOVERABILITY_ALL_USERS panel includes a secondary `submenu-button` button that is not labeled (has no name and is announced just as `button`) and it does not indicate that there is a menu attached to it. Users of assistive technologies would not have a way to know what is the purpose of this control (`access-S2`-[level issue](https://wiki.mozilla.org/Accessibility/Triage)) and, if they activate it, that the menu is expected to appear (`access-S3`) and that the menu is currently not visible / in a collapsed state (`access-S3`)

Observed in Release for the "Didn't mean to close that tab?" alertdialog treatment after closing a few tabs in a row. 

*Recommendation* is to follow [the menu button pattern](https://www.w3.org/WAI/ARIA/apg/patterns/menu-button/) by: 
1. Add accessible name, i.e. via `aria-label` - it could be `More options`, for instance
2. Add `aria-haspopup=menu` to the `<button>` to indicate there is a menu attached
3. Add `aria-expanded` set to `false` by default and dynamically changed to `true` when a menu is open/shown to indicate the state of this menu
Bug: Callout container and its secondary buttons on the Firefox View Discoverability panel are missing proper HCM treatments
Status: NEW
Priority: P1
Created: 2024-12-04 21:35:32+00:00
Resolved: 2025-03-03 18:05:30+00:00

The FX_VIEW_DISCOVERABILITY_ALL_USERS panel includes the following issues with [the High Contrast](https://firefox-source-docs.mozilla.org/accessible/ColorsAndHighContrastMode.html#operating-system-high-contrast-mode-os-hcm) themes on Windows that may resolve in some themes not providing an expected, readable experience for the text of the container and missing an expecting indication that both `Dismiss` and `V` buttons are, in fact, active UI elements that could be clicked (`access-S3`-[level issues](https://wiki.mozilla.org/Accessibility/Triage)) 

Observed in Release for the "Didn't mean to close that tab?" alertdialog treatment after closing a few tabs in a row. 

*Recommendation* is to follow [the HCM secondary button pattern (Figma reference, requires SSO to access)](https://www.figma.com/design/VHRA9hZ54oJqKKJwPd6FWa/High-Contrast-Mode?node-id=0-1) and [HCM media queries for forced-colors mode](https://firefox-source-docs.mozilla.org/accessible/HCMMediaQueries.html) by: 
1. Secondary buttons:
    1. Adding 1px border to each `Dismiss` and `V` secondary buttons - use `ButtonText` color (the background of buttons should be `ButtonFace`)
    2. Ensure hover styling is provided for both secondary buttons - use `SelectedItem` for the background and `SelectedItemText` for the border and label text (color pair)
    3. `:active` state would get the hover styling combo with `ButtonText` used for the border alone
2. The callout container is using button treatments for its static text elements:
    1. use `Canvas` for the background of the container
    2. use `CanvasText` for the foreground color of the container (its headings text)
Bug: Cancelling a tab group creation puts the tabs into an existing tab group
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-12-04 22:24:31+00:00
Resolved: 2024-12-10 15:29:22+00:00

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0

Steps to reproduce:

- Have 5 tabs open and create a tab group (named group1) with the last 3 tabs
- Drag the second tab onto the first tab
- Click 'Cancel" on the 'Create tab group' dialog


Actual results:

The two tabs from the cancelled tab group are added to the beginning of 'group1'.


Expected results:

The two tabs should be put back to their original position (ungrouped).
Bug: "Search with Amazon" quick search eats a single input character
Status: NEW
Priority: P3
Created: 2024-12-04 23:27:13+00:00
Resolved: 2024-12-16 16:55:32+00:00

STR:

1. Type "Amazon.com" into the search bar, or enough characters to trigger the "tab to search with amazon" quick search option
2. Hit tab to quick search
3. Begin typing "abcd"

Expected: 
"abcd" is visible in the url bar

Actual:
"bcd" is visible in the url bar


4. Hit enter to search

Expected:
"abcd" is searched on amazon.com

Actual:
"bcd" is searched on amazon.com
Bug: Open New Tab and List All Tabs buttons are not providing expected HCM treatments
Status: ASSIGNED
Priority: P2
Created: 2024-12-04 23:45:36+00:00
Resolved: 2025-01-31 17:58:38+00:00

When Windows HCM are active, `+` Open New Tab and `List All Tabs` toolbar buttons are not as expected by default and when hovered they are hard to discern.

The lack of the semantic styling in the High Contrast Mode (HCM) is an [access-S3 issue](https://wiki.mozilla.org/Accessibility/Triage) since it makes it difficult to discern which element is, in fact, an active UI and could be activated if clicked, which one is now hovered and which one is not, for HCM users (those with low vision, users with cognitive disabilities, users with dyslexia, with colorblindness, and others).

We need to ensure the appropriate color pairs are used for `forced-colors` [media query (HCM on Win)](https://firefox-source-docs.mozilla.org/accessible/HCMMediaQueries.html): `ButtonFace` with `ButtonText` for the border/label text and for the control background. The hovered state is expected to use `SelectedItem` and `SelectedItemText` color combination in place of the Button colors of the default state.

*Recommendation* is to follow [the HCM Tab Strip pattern (Figma reference, requires SSO to access)](https://www.figma.com/design/VHRA9hZ54oJqKKJwPd6FWa/High-Contrast-Mode?node-id=1366-5996) and [HCM media queries for forced-colors mode](https://firefox-source-docs.mozilla.org/accessible/HCMMediaQueries.html) by: 
1. Default - use `ButtonText` color for both the border and foreground/icons and the background of buttons should be `ButtonFace`
2. Ensure hover styling is provided for buttons - use `SelectedItem` for the background and `SelectedItemText` for the border and label text (color pair)
3. `:active` state would get the hover styling combo with `ButtonText` used for the border alone
Bug: [RTL] Icons on the customize sidebar page are not horizontally centered between the checkbox and the label
Status: NEW
Priority: P3
Created: 2024-12-05 00:16:21+00:00
Resolved: 2025-01-06 12:10:59+00:00

See attached, in RTL the icons are shifted to the right. This doesn't seem to be an issue with missing use of CSS logical properties.
Unchecking this line fixes this locally:
https://searchfox.org/mozilla-central/rev/7fb746f0be47ce0135af7bca9fffdb5cd1c4b1d5/toolkit/content/widgets/moz-input-common.css#39-41

I noticed the only icon that doesn't suffer from this is the sparkles one, and incidentally its SVG is the only one that doesn't specify `width="16" height="16"`.
Bug: Intermittent TV browser/components/translations/tests/browser/browser_translations_about_preferences_settings_ui.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N)
Status: RESOLVED
Priority: P5
Resolution: FIXED
Created: 2024-12-05 00:48:49+00:00
Resolved: 2024-12-09 07:03:11+00:00

**Filed by:** amarc [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=485397389&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/aE8hb-8YTZypdBKX3Bbd9g/runs/0/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/aE8hb-8YTZypdBKX3Bbd9g/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---
```
[task 2024-12-04T22:29:56.338Z] 22:29:56     INFO - TEST-PASS | browser/components/translations/tests/browser/browser_translations_about_preferences_settings_ui.js | translateDownloadLanguagesLearnMore is visible. - 
[task 2024-12-04T22:29:56.339Z] 22:29:56     INFO - Buffered messages logged at 22:29:56
[task 2024-12-04T22:29:56.339Z] 22:29:56     INFO - Leaving test bound test_translations_settings_about_preferences_translations_tab
[task 2024-12-04T22:29:56.339Z] 22:29:56     INFO - Buffered messages finished
[task 2024-12-04T22:29:56.340Z] 22:29:56     INFO - TEST-UNEXPECTED-FAIL | browser/components/translations/tests/browser/browser_translations_about_preferences_settings_ui.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - 
[task 2024-12-04T22:29:56.340Z] 22:29:56     INFO - GECKO(1039) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2024-12-04T22:29:56.341Z] 22:29:56     INFO - GECKO(1039) | MEMORY STAT | vsize 16935MB | residentFast 409MB | heapAllocated 204MB
[task 2024-12-04T22:29:56.341Z] 22:29:56     INFO - TEST-OK | browser/components/translations/tests/browser/browser_translations_about_preferences_settings_ui.js | took 75431ms
[task 2024-12-04T22:29:56.342Z] 22:29:56     INFO - checking window state
[task 2024-12-04T22:29:56.342Z] 22:29:56     INFO - GECKO(1039) | Completed ShutdownLeaks collections in process 1039
[task 2024-12-04T22:29:56.342Z] 22:29:56     INFO - TEST-START | Shutdown
```
Bug: Intermittent browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_unload_telemetry.js | single tracking bug
Status: NEW
Priority: P5
Created: 2024-12-05 01:21:40+00:00
Resolved: 2025-03-03 06:51:09+00:00

**Filed by:** amarc [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=485415388&repo=mozilla-central
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/bdN3jJ1KQEWIimgtP1H4iw/runs/0/artifacts/public/logs/live_backing.log

---
```
task 2024-12-05T00:51:47.448Z] 00:51:47     INFO - TEST-PASS | browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_unload_telemetry.js | correct name - "tab_explicit_unload" == "tab_explicit_unload" - 
[task 2024-12-05T00:51:47.449Z] 00:51:47     INFO - Buffered messages finished
[task 2024-12-05T00:51:47.449Z] 00:51:47     INFO - TEST-UNEXPECTED-FAIL | browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_unload_telemetry.js | Memory should go down after unload (before: 1276440104, after 1278438776) - 1998672 < 100000 - 
[task 2024-12-05T00:51:47.449Z] 00:51:47     INFO - Stack trace:
[task 2024-12-05T00:51:47.449Z] 00:51:47     INFO - chrome://mochitests/content/browser/browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_unload_telemetry.js:checkEventCommon:68
[task 2024-12-05T00:51:47.449Z] 00:51:47     INFO - chrome://mochitests/content/browser/browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_unload_telemetry.js:test_unload_selected_tab:227
[task 2024-12-05T00:51:47.449Z] 00:51:47     INFO - chrome://mochikit/content/browser-test.js:handleTask:1147
[task 2024-12-05T00:51:47.449Z] 00:51:47     INFO - chrome://mochikit/content/browser-test.js:_runTaskBasedTest:1219
[task 2024-12-05T00:51:47.449Z] 00:51:47     INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1360
[task 2024-12-05T00:51:47.449Z] 00:51:47     INFO - chrome://mochikit/content/browser-test.js:nextTest/<:1136
[task 2024-12-05T00:51:47.449Z] 00:51:47     INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/<:1058
[task 2024-12-05T00:51:47.450Z] 00:51:47     INFO - TEST-PASS | browser/components/tabbrowser/test/browser/tabs/browser_multiselect_tabs_unload_telemetry.js | time_to_unload should be >= 0 - 0 >= 0 - 

```
Bug: Focus ring appears in New tab page customize dropdown & checkmark buttons when clicked
Status: NEW
Priority: P3
Created: 2024-12-05 07:46:14+00:00
Resolved: 2025-01-07 18:11:31+00:00

**Found in**
* Firefox 134.0b3

**Affected versions**
* Firefox 134.0b3
* Latest Nightly 135.0a1

**Tested platforms**
* Affected platforms: Windows 11, macOS 13 and Ubuntu 22.04
* Unaffected platforms: none

**Preconditions**
* none

**Steps to reproduce**
1. Open new tab
2. Click on the Gear button (Personalize New Tab)
3. Click on the Shortcuts dropdown

**Expected result**
* There is no focus ring around the dropdown button when clicked

**Actual result**
* A light blue focus ring flashes on the dropdown button when clicked

**Regression range**
* First bad: eb7d5e82aaea1a9696cfa1393b5fa318e73b07de
* Last good: 8cdd018168b025a36b6188eb9afed96e550c8cb0
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=8cdd018168b025a36b6188eb9afed96e550c8cb0&tochange=eb7d5e82aaea1a9696cfa1393b5fa318e73b07de
* Potentially regressed by: Bug 1893053 - Select and checkbox controls on the about:newtab page's settings dialog have subtle focus indication

**Additional notes**
* On macOS it is a bit harder to see since the results from the dropdown is overlapping the dropdown button itself but it can still be seen if looking close. 
* This is also seen if clicking on the Checkmark from "Sponsored shortcuts" but it might need to click multiple times and faster on Mac, on Win and Linux it is clearly visible.
Bug: [Experiment] Multiple "Make Firefox your primary browser" prompt screens have the "Make Firefox your default browser?" title
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-12-05 09:54:29+00:00
Resolved: 2024-12-06 15:32:18+00:00

**[Affected versions]:**
- Firefox Beta 134.0b4 - Build ID: 20241202091515

**[Affected Platforms]:**
- Windows 10 x64
- macOS 14.4
- Ubuntu 22.04 x64

**[Prerequisites]:**
- Have a Firefox profile with the nimbus.debug pref set to true in the "about:config" page.
- Firefox is not pinned to the taskbar and is not the default browser.

**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to "about:studies?optin_slug=set-to-default-prompt-style-spotlight&optin_branch=treatment-a&optin_collection=nimbus-preview".
3. Restart the browser and observe the default browser prompt's title.

**[Expected result]:**
- The "Make Firefox your primary browser?" title is displayed.

**[Actual result]:**
- "Make Firefox your default browser?" title is displayed instead.

**[Notes]:**
- The issue is reproducible using the following prompts: "NEED_PIN_MAC", "NEED_PIN_MSIX", "NEED_PIN_OTHERS"
- Attached a screenshot of the issue:
Bug: The "WNP_MOMENTS_22" page is not triggered on the Firefox 127.0.1 and 127.0.2 versions
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-12-05 11:28:24+00:00
Resolved: 2024-12-10 02:39:44+00:00

**[Affected versions]:**
- Firefox Release 127.0.1 - Build ID: 20240618110440
- Firefox Release 127.0.2 - Build ID: 20240624183754

**[Affected Platforms]:**
- Windows 10
- Windows 11
- macOS 15.1.1
- Ubuntu 24.04

**[Prerequisites]:**
- Have a Firefox Release 127.0.1 or 127.0.2 installed.
- Have any of the following Firefox locales installed: en, fr, ru, es, zh, de, pt, pl, it, ja, id, hu, cs, ar, and el.
- Have the "services.settings.default_bucket" pref set to "main-preview" in the "about:config" page.
  
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Change the system time to any date between the 10th of December and the 4th of January and restart the browser.
3. Restart the browser again and observe the behavior.

**[Expected result]:**
- The "WNP_MOMENTS_22" page is successfully triggered.
    
**[Actual result]:**
- The "WNP_MOMENTS_22" page is NOT triggered.

**[Notes]:**
- The issue is not reproducible on the 127.0 Firefox version where the "WNP_MOMENTS_22" page is successfully triggered.
- I have evaluated the "version|versionCompare('127.0.*') <= 0" targeting expression in the ASRouter page while on a Firefox 127.0.2 build and the result was "false"
Bug: Drag and dropping a Tab outside of a Group and placing it between a 2nd group and a free Tab will automatically add it to the 2nd Group
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2024-12-05 13:14:42+00:00
Resolved: 2025-02-25 09:38:01+00:00

**Found in**
* 135.0a1 (2024-12-04) 

**Affected versions**
* 135.0a1 (2024-12-04)

**Preconditions**
Set browser.tabs.groups.enabled	true

**Affected platforms**
* Windows

**Steps to reproduce**
1. Have a Few Tabs opened.
2. Create 2 New Tab Groups.
3. Have a Free Tab to the right of the 2nd group.
4. Drag a Tab from the First Group outside of the groups past the 2nd group right before the Free Tab.

**Expected result**
* Users should be able to move a Tab past a 2nd group and place it outside of any group.

**Actual result**
* Dragging a Tab from the first Group and placing it past a 2nd Group before a Free Tab will add the moving Tab to the 2nd group.

**Regression range**
Not a Regression.
Bug: Forced capitalisation caps with text-transform
Status: NEW
Priority: P3
Created: 2024-12-05 13:37:33+00:00
Resolved: 2025-01-15 22:56:39+00:00

This was noticed in Tor Browser development.

I'm not sure if "General" was the best component, but this is meant to cover firefox desktop localisation

A few components force all-caps or title cases [using `text-transformation`](https://searchfox.org/mozilla-central/search?q=text-transform%3A&path=&case=false&regexp=false).

Forcing capitalisation can have bad effects in some locales, like gaelic and greek. See https://mozilla-l10n.github.io/documentation/localization/dev_best_practices.html#css-issues.

In these cases where all caps is desirable, the `en-US` string itself should be capitalised, but the localisers should determine the capitalisation of the translation.

I'm hoping this could be a meta-issue to remove the forced-capitalisation.
Bug: Clicking and dragging the `This connection is not secure` panel will make the contents invisible
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-12-05 14:11:13+00:00
Resolved: 2024-12-16 12:19:29+00:00

**Found in**
* 135.0a1 (2024-12-04)

**Affected versions**
* 135.0a1 (2024-12-04)


**Tested platforms**
* Affected platforms:  Windows 10x64
* Unaffected platforms: macOS 12, Ubuntu 24



**Steps to reproduce**
1. Open http://jsbin.testim.io/soviruvalo/1/edit?html,output.
2. Click on the username or password field.
3. Click and hold the insecure connection panel.

****Expected result****
* The panel is visible and has a selected effect.

**Actual result**
* The panel contents are not visible.



**Regression range**
* pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=e6f1ff3702cb37c8f402577cb55cfd544c02f049&tochange=e2a09f7c430ea6f7d06fadf270f5093136621826  

**Additional notes**
* Attached a screen recording.
* This reproduces with a dark/ white/ system theme.
Bug: [Experiment] A larger "Set as Default" prompt is displayed for a second before the experiment one, causing a flicker on Windows
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-12-05 14:44:30+00:00
Resolved: 2024-12-06 15:32:04+00:00

**[Affected versions]:**
- Firefox Beta 134.0b4 - Build ID: 20241202091515
- FIrefox Beta MSIX 134.0b5, Build ID 20241204091850

**[Affected Platforms]:**
- Windows 11 x64
- Windows 10 x64

**[Prerequisites]:**
- Have a Firefox profile with the nimbus.debug pref set to true in the "about:config" page.
- Firefox is not pinned to the taskbar and is not the default browser.

**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to "about:studies?optin_slug=set-to-default-prompt-style-spotlight&optin_branch=treatment-a&optin_collection=nimbus-preview".
3. Restart the browser and observe the default browser prompt.

**[Expected result]:**
- The experiment's "Set as Default" prompt is displayed.

**[Actual result]:**
- A larger "Set to Default" prompt with pagination bullets is displayed for a second, causing the experiment message to flicker as it resizes.

**[Notes]:**
- The issue is ONLY reproducible on Windows with regular and MS Store builds.
- Attached a screenshot of the larger prompt:
- Attached a video (10% speed) of the messages: