av9ash/GitBugs huggingface dataset:
Bug: Intermittent browser/base/content/test/keyboard/browser_cancel_caret_browsing_in_content.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2022-08-25 06:32:08+00:00
Resolved: 2022-09-20 17:03:58+00:00

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

---
```
[task 2022-08-25T05:41:37.055Z] 05:41:37     INFO - TEST-START | browser/base/content/test/keyboard/browser_cancel_caret_browsing_in_content.js
[task 2022-08-25T05:42:22.060Z] 05:42:22     INFO - TEST-INFO | started process screenshot
[task 2022-08-25T05:42:22.157Z] 05:42:22     INFO - TEST-INFO | screenshot: exit 0
[task 2022-08-25T05:42:22.162Z] 05:42:22     INFO - Buffered messages logged at 05:41:37
[task 2022-08-25T05:42:22.163Z] 05:42:22     INFO - Entering test bound 
[task 2022-08-25T05:42:22.163Z] 05:42:22     INFO - Waiting reply F7 keypress event...
[task 2022-08-25T05:42:22.163Z] 05:42:22     INFO - TEST-PASS | browser/base/content/test/keyboard/browser_cancel_caret_browsing_in_content.js | F7 key should enable caret browsing mode - 
[task 2022-08-25T05:42:22.164Z] 05:42:22     INFO - Waiting for reply F7 keydown event...
[task 2022-08-25T05:42:22.164Z] 05:42:22     INFO - Checking reply keypress event is not fired...
[task 2022-08-25T05:42:22.164Z] 05:42:22     INFO - Buffered messages finished
[task 2022-08-25T05:42:22.165Z] 05:42:22     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/keyboard/browser_cancel_caret_browsing_in_content.js | Test timed out - 
[task 2022-08-25T05:42:22.165Z] 05:42:22     INFO - TEST-PASS | browser/base/content/test/keyboard/browser_cancel_caret_browsing_in_content.js | F7 key shouldn't enable caret browsing mode because F7 keydown event is consumed by web content - 
[task 2022-08-25T05:42:22.166Z] 05:42:22     INFO - Leaving test bound 
[task 2022-08-25T05:42:30.352Z] 05:42:30     INFO - GECKO(2924) | MEMORY STAT | vsize 2104163MB | vsizeMaxContiguous 67605046MB | residentFast 251MB | heapAllocated 119MB
[task 2022-08-25T05:42:30.355Z] 05:42:30     INFO - TEST-OK | browser/base/content/test/keyboard/browser_cancel_caret_browsing_in_content.js | took 53299ms
[task 2022-08-25T05:42:30.362Z] 05:42:30     INFO - checking window state
[task 2022-08-25T05:42:30.369Z] 05:42:30     INFO - TEST-START | browser/base/content/test/keyboard/browser_popup_keyNav.js
```
Bug: Firefox updates erase my "applications" settings everytime !
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-08-25 07:32:36+00:00
Resolved: 2022-09-19 10:08:32+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0

Steps to reproduce:

I did nothing : eache new updates erase my settings éapplications" and I need to restore some handlers.json I have backupped before



Actual results:

"Settings/general/applications" are changed and so I have to set them up again and again !


Expected results:

Let my previous settings unchanged !
Bug: The user's theme is changed to the system's one if the "Skip this step" or "current colors" button from the existing's user "Colorways" modal is clicked
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-08-25 09:00:28+00:00
Resolved: 2022-09-09 13:21:31+00:00

**[Affected versions]:**
- Firefox Nightly 106.0a1 - Build ID: 20220824213405

**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6.7
- Linux Mint 20.2 x64

**[Prerequisites]:**
- Have the following prefs in the "about:config" page:
  - "devtools.chrome.enabled" set to "true";
- Have the "Browser Console" opened.
- Have a custom theme applied from "about:addons>Themes".

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Focus the "Browser Console" and run the `Cc["@mozilla.org/browser/browserglue;1"].getService().wrappedJSObject._showUpgradeDialog();` code.
3. Navigate through the Onboarding modals until the "Colorways" one is displayed.
4. Click the "Skip this step" button and observe the browser's theme.

**[Expected result]:**
- The existing user theme is still enabled.

**[Actual result]:**
- The theme is changed to the system theme.

**[Additional Notes]:**
- The user set theme is also reset to the system one if the "Default" theme option from the "Colorways" modal is selected.
- Attached a screen recording of the issue.
Bug: [Localization] Private Browsing icon remains on Start menu after uninstall for localized builds.
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-08-25 09:42:55+00:00
Resolved: 2022-10-05 05:48:22+00:00

**Found in**
* Beta 105.0b2

**Affected versions**
* Beta 105.0b2

**Tested platforms**
* Affected platforms: Windows (7, 10).
* Unaffected platforms: Ubuntu20.4, MacOs.

**Steps to reproduce**
1. Uninstall all FF builds from desktop.
2. Delete registry and App Data from PC.
3. Perform a clean install of a localized build (I used fr build).
4. Set prefs “browser.privacySegmentation.enabled” and “browser.privacySegmentation.windowSeparation.enabled” to true.
5. Restart FF.
6. Open a Private Window.
7. Close and uninstall FF.
8. Check programs in Start for FF icons.

**Expected result**
* No FF icons should be displayed in Start->Programs.

**Actual result**
* Private FF icon is  displayed in Start->Programs after uninstall. If trying to open the remaining icon a screen if displayed (see second screenshot).

**Regression range**
* Will add one asap.

**Additional notes**
* Issue reproduces on French(.fr) and Spanish (.es-ES) localized builds but might affect all localizations. 
* If Private icon is pinned to Start Menu, icon is displayed on Start Menu after uninstall also.
* Issue is not reproducing on EN.
Bug: The "Skip this step" label from the secondary CTA button is too small on higher resolutions
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2022-08-25 09:53:36+00:00
Resolved: 2022-09-15 08:56:32+00:00

**[Affected versions]:**
- Firefox Nightly 106.0a1 - Build ID: 20220824213405

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

**[Prerequisites]:**
- Have the following prefs in the "about:config" page:
 - "devtools.chrome.enabled" set to "true";
 - "browser.aboutwelcome.templateMR" set to "true".
- Have a screen with a 2560x1440 resolution set (scaling 100%).

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Navigate to the "about:welcome" page.
3. Observe the label from the "Skip this step" secondary button.

**[Expected result]:**
- The label is correctly displayed and visible.

**[Actual result]:**
- The "Skip this step" label is too small.

**[Notes]:**
- This issue is also reproducible with the "Skip this step" button from the existing users modals.
- This issue is less visible on macOS, Linux Mint 20.2 x64, or normal resolutions.
- Attached a screenshot of the issue.
Bug: The version set by the Update Pin policy is not respected on release channel
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-08-25 09:57:08+00:00
Resolved: 2022-09-05 12:26:15+00:00

**Found in**
* 102

**Affected versions**
* 102/103

**Affected platforms**
* Windows 10
* macOS 11.5/13
* Ubuntu 20.04/22.04

**Steps to reproduce**
1. Install an older Firefox (version 102)
2. Add the Update Pinning policy inside the Firefox installation folder with the pin version set to 102
3. Open the browser and confirm that the Update Pinning policy has an active status inside about:policies
4. Attempt to update the browser

**Expected result**
* Firefox can’t be updated, it remains to the pinned version (102)

**Actual result**
* Firefox updates to 103.0.2.

**Regression range**
* N/A

**Additional notes**
* Once the policy is removed the browser is updated to the latest version available (104)
* Update Pinning policy seemed to work until this morning, a complete round of tests were executed yesterday on macOS without any issue. As for Windows 10, we saw that the very first time when setting the policy on a build will not actually respect it (it does appear in about:policy) and update past the pin (repeating a second time and so on will respect the pin every time). As of today the pin is not respected at all. 
* ESR respects the pin policy, no issue on this channel.
Bug: Perma browser/base/content/test/performance/browser_startup_images.js | single tracking bug when Gecko 106 merges to Beta on 2022-09-19
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-08-25 12:24:02+00:00
Resolved: 2022-09-12 06:28:22+00:00

[Central-as-beta simulation](https://treeherder.mozilla.org/jobs?repo=try&resultStatus=testfailed%2Cbusted%2Cexception&revision=04f4e278448ca4201d345e3a07b6372806db5d29u)

[How to run these simulations](https://wiki.mozilla.org/Sheriffing/How_To/Beta_simulations#TRUNK_AS_EARLY_BETA)

[Failure log:](https://treeherder.mozilla.org/logviewer?job_id=388454960&repo=try&lineNumber=3639)

```
[task 2022-08-25T11:14:39.323Z] 11:14:39     INFO - TEST-PASS | browser/base/content/test/performance/browser_startup_images.js | Loaded image chrome://global/skin/icons/pocket-outline.svg should have been shown. - 
[task 2022-08-25T11:14:39.324Z] 11:14:39     INFO - Buffered messages finished
[task 2022-08-25T11:14:39.327Z] 11:14:39     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/performance/browser_startup_images.js | Loaded image chrome://branding/content/icon32.png should have been shown. - 
[task 2022-08-25T11:14:39.328Z] 11:14:39     INFO - Stack trace:
[task 2022-08-25T11:14:39.329Z] 11:14:39     INFO - chrome://mochikit/content/browser-test.js:test_ok:1440
[task 2022-08-25T11:14:39.330Z] 11:14:39     INFO - chrome://mochitests/content/browser/browser/base/content/test/performance/browser_startup_images.js:null:120
[task 2022-08-25T11:14:39.339Z] 11:14:39     INFO - TEST-PASS | browser/base/content/test/performance/browser_startup_images.js | Loaded image chrome://browser/content/static-robot.png should have been shown. - 
```
Hello Scott, could you please take a look at this failure? It could be regressed by Bug 1782318. Thanks
Bug: SVG rendering not complete when switching tabs
Status: NEW
Priority: --
Created: 2022-08-25 12:24:28+00:00
Resolved: 2022-10-31 15:14:39+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0

Steps to reproduce:

Show page, Javascript genertes a set of SVG elements in tables and/or Div's.
Render is as expected.
Scroll down a bit, or resize window to obscure part of the SVG.
Switch to any other tab, switch back to original and scroll to view hidden part of SVG element.


Actual results:

Part of the SVG filter is not shown in the part that comes back into view.


Expected results:

Render as originally rendered before swiching Tabs. Resizing browser window fixes the issue, moving the browser around the screen does not.
Bug: Layout issue with “Last active” pill with longer translations
Status: RESOLVED
Priority: P1
Resolution: DUPLICATE
Created: 2022-08-25 12:52:52+00:00
Resolved: 2022-08-30 12:33:30+00:00

Hi,

I noticed the French translation doesn’t fit in the “Last active” pill, causing some layout issues. Other locales may have similar issues.

Attaching a screenshot from the latest Nightly
Bug: The elements from the first screen of the Firefox View Tour feature overlap with the elements from the “Independent Voices” section when resizing the browser on RTL builds
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-08-25 13:14:10+00:00
Resolved: 2022-08-26 05:28:32+00:00

**[Affected versions]:**
- Firefox Nightly 106.0a1 (Build ID: 20220824213405)

**[Affected Platforms]:**
- macOS 12.5.1
- Windows 10 x64
- Ubuntu 20.04 x64

**[Prerequisites]:**
- Have the Firefox browser installed/extracted and opened.
- Have the “browser.firefox-view.feature-tour” pref set to “{"message":"FIREFOX_VIEW_FEATURE_TOUR","screen":"","complete":false}” value.
- Have the “intl.l10n.pseudo” pref set to “bidi” value.

**[Steps to reproduce]:**
1. Navigate to the “about:firefoxview” page.
2. Resize the browser horizontally.
3. Observe the elements from the first screen of the Firefox View Tour feature.

**[Expected result]:**
 - All elements are correctly displayed and visible.

**[Actual result]:**
 -  The elements overlap the “Independent Voices” section. 

**[Regression Window]:**
- The issue is not reproducible with older Nightly 105.0a1 builds. Considering this using mozregression tools, I have found the regression range. Here are the results:
 Last good revision: 35007c92b9a6171b637d3c44c95c693704468ec0
 First bad revision: 2e07ab0665e6d20839daccd0d6c7473d2ac7e684
 Pushlog: [link](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=35007c92b9a6171b637d3c44c95c693704468ec0&tochange=2e07ab0665e6d20839daccd0d6c7473d2ac7e684)

From this pushlog it seems that [Bug 1781088](https://bugzilla.mozilla.org/show_bug.cgi?id=1781088) may have introduced this behavior.

**[Notes]:**
- This issue is not reproducible on the 2nd and 3rd screens of the Firefox View Feature Tour.
- Attached is a screen recording of the issue.
Bug: [Win 11] Firefox PBM icon is briefly displayed in taskbar when opening
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-08-25 14:33:26+00:00
Resolved: 2022-09-27 16:28:10+00:00

**Found in**
* Beta 105.0b2

**Affected versions**
* Beta 105.0b2

**Tested platforms**
* Affected platforms:
Win 11 x64
* Unaffected platforms: 
Win 10 x64

**Steps to reproduce**
1. Download, unzip [this](https://archive.mozilla.org/pub/firefox/candidates/99.0b1-candidates/) build and open it.
2. Navigate to `about:config` and add the following prefs as true:
browser.privacySegmentation.enabled
browser.privacySegmentation.windowSeparation.enabled - this pref needs to be manually created
3. Update the build to the latest beta version available.
4. Close the build.
6. Open again the Firefox build, and observe the Win taskbar.

**Expected result**
* Firefox icon is the regulator one, not the PBM icon, as briefly is displayed in the taskbar.

**Actual result**
* Firefox PBM icon is briefly displayed in the taskbar, then it changes to the regular one.

**Regression range**
* Not a regression.

**Additional notes**
* Please observe the attached screencast.
* I was unable to reproduce the problem if updating from 104.0b1 to the latest version. So, maybe, this issue is triggered by the fact that we manually create the pref `browser.privacySegmentation.windowSeparation.enabled` in 99.0b1, before updating the build.
Bug: Website login popup prompt not following content color scheme
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-08-25 15:39:06+00:00
Resolved: 2022-09-26 09:37:09+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:106.0) Gecko/20100101 Firefox/106.0

Steps to reproduce:

When a website or web server popups a login prompt, it should follow the system theme. Currently it is no long dark.
Bug: Cache2 files recreated on opening FF W11 24.0KB and W10 PC 36.0KB Privacy breach?
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-08-25 15:48:53+00:00
Resolved: 2022-08-31 13:38:52+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0

Steps to reproduce:

Empty Cookies, Data and Cache files. 
Close FireFox
Open FireFox
Empty Cookies, Data and Cache files. 
Close FireFox
Open FireFox
36.0KB three Files recreated On W10PC


Actual results:

Two PC's same independent profile used on both:
W10 PC three files 36.0KBs always recreated on opening FF
W11 PC two files 24.0KBs recreated on opening FF

I also booted into a Linux PC and the Cache stayed at 0.0KBs on restarting FF. So Linux is fine. 


Expected results:

To my naivety when emptied the Cache should be empty and stay empty. 
The recreation of these same files to me would allow fingerprinting of the browser irrespective of how strong a privacy mode you set FF to.  I have it clear everything on closing FF. 

Whilst I could be wrong I got suspicious with my location being detected whilst using a VPN server not in my country.
Bug: Extend bounding box for domain name / URL in tab pickup cards
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2022-08-25 15:55:29+00:00
Resolved: 2022-10-05 12:12:27+00:00

Actual: URL/Domain name is wrapping very early and with a lot of space to expand before wrapping
Expected. URL/Domain name expands to 8px from edge of tab pickup card before wrapping.

Screenshot attached of actual behavior
Bug: Firefox View button not visible to users of vertical tabs addons
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2022-08-25 16:12:57+00:00
Resolved: 2022-08-25 19:01:46+00:00

I  use Tab Center Reborn but this is likely to be impacting other vertical tab extensions.

The Firefox View button is not visible in the UI because alongside the installation of the addon, we hide the tab bar via userchrome.css:

```css
#TabsToolbar:not([customizing="true"]) {
  visibility: collapse !important;
}
```
Bug: PDF file is opend in firefox, settings say user should be aksed
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-08-25 16:13:00+00:00
Resolved: 2022-10-14 13:28:14+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0

Steps to reproduce:

Firefox settings for mime type pdf is set to ask the user each time to choose an action. There are different PDF mime types. All are set to ask the user.
Links to PDF files are clicked. Selection windows are shown. PDF files are saved to disk, opened in a reader software or processes are stoped. The option to show PDF file in firefox wasn't used once.


Actual results:

After a while PDF files are opened in firefox, ignoring the setting "ask the user for an action".
Settings are still the same, but they do not work.


Expected results:

The user should each time be asked by selection windows what action he wants to happen with the PDF file.
Bug: H1 styles should be 1.5em and 600 weight
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2022-08-25 16:18:58+00:00
Resolved: 2022-09-08 04:56:23+00:00

Actual: "Independent Voices" is 1.8em and font-weight: bold. Tab pickup and Recently closed are 1.5em and font-weight: 500
Expected: "Independent Voices", "Tab pickup" and "Recently closed" are 1.5em and font-weight: bold
Bug: Documentation for quick actions on Mozilla Support still missing
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-08-25 17:00:14+00:00
Resolved: 2022-08-25 18:09:05+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:105.0) Gecko/20100101 Firefox/105.0

Steps to reproduce:

In Firefox Developer Edition 105.0b2, quick actions are enabled for me in the address bar. I clicked on the question mark at the right. I wanted to find out how to disable the feature because I don't want to use it.


Actual results:

The browser openend a tab at https://support.mozilla.org/de/kb/quick-actions-firefox-search-bar?as=u&utm_source=inproduct which does not seem to exist.


Expected results:

I would have expected a webpage that informs me about the new feature and mentions customization options and how to disable the feature.

I've disabled the feature by setting browser.urlbar.suggest.quickactions to false via about:config.
Bug: Some newtab instrumentation module(s) don't parse ES2020 constructs
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2022-08-25 17:39:11+00:00
Resolved: 2024-01-11 09:55:42+00:00

It would be good to update the jsm/jsx compilation and unit tests to handle more modern ES syntax. We are currently using babel plugins to parse and transpile nullish coalescing and optional chaining operators, but they make the output far less readable. We could remove them, but for istanbul-instrumenter-loader.

According to [this report](https://github.com/skylock/cypress-angular-coverage-example/issues/6), we may be able to use babel-plugin-istanbul instead.
Bug: Perma [tier 2] browser/base/content/test/static/browser_all_files_referenced.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: WORKSFORME
Created: 2022-08-25 18:16:27+00:00
Resolved: 2022-10-13 12:48:01+00:00

**Filed by:** abutkovits [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=388483441&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/YMKtJECUQnuPsT_d3G-byA/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/YMKtJECUQnuPsT_d3G-byA/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---
```
[task 2022-08-25T16:02:10.869Z] 16:02:10     INFO - TEST-PASS | browser/base/content/test/static/browser_all_files_referenced.js | there should be no unreferenced files - 
[task 2022-08-25T16:02:10.869Z] 16:02:10     INFO - ignored unused whitelist entry: resource://app/blocklist.xml
[task 2022-08-25T16:02:10.870Z] 16:02:10     INFO - ignored unused whitelist entry: resource://gre/gmp-clearkey/0.1/manifest.json
[task 2022-08-25T16:02:10.870Z] 16:02:10     INFO - ignored unused whitelist entry: resource://gre/res/test.properties
[task 2022-08-25T16:02:10.870Z] 16:02:10     INFO - Buffered messages logged at 16:01:40
[task 2022-08-25T16:02:10.871Z] 16:02:10     INFO - missing file: chrome://devtools/skin/images/editor-error.png referenced from chrome://devtools/content/debugger/src/utils/editor/source-editor.css
[task 2022-08-25T16:02:10.871Z] 16:02:10     INFO - Buffered messages logged at 16:01:44
[task 2022-08-25T16:02:10.872Z] 16:02:10     INFO - missing file: resource://devtools/shared/platform/chrome/stack.js referenced from resource://devtools/client/devtools-client.js,resource://devtools/shared/DevToolsUtils.js,resource://devtools/shared/event-emitter.js,resource://devtools-client-shared/telemetry.js,resource://devtools/shared/protocol/Front.js
[task 2022-08-25T16:02:10.872Z] 16:02:10     INFO - missing file: resource://app/localization/en-US/devtools/shared/locales/en-US/debugger-paused-reasons.ftl referenced from resource://devtools/shared/constants.js
[task 2022-08-25T16:02:10.872Z] 16:02:10     INFO - Buffered messages finished
[task 2022-08-25T16:02:10.873Z] 16:02:10     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/static/browser_all_files_referenced.js | Test timed out - 
[task 2022-08-25T16:02:10.873Z] 16:02:10     INFO - GECKO(1574) | MEMORY STAT | vsize 8090MB | residentFast 627MB | heapAllocated 308MB
[task 2022-08-25T16:02:10.874Z] 16:02:10     INFO - TEST-OK | browser/base/content/test/static/browser_all_files_referenced.js | took 274462ms
```
Bug: The arrow from the “Skip this step” button has a black color when the browser's dark theme is enabled
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-08-26 05:20:50+00:00
Resolved: 2022-08-30 20:25:41+00:00

**[Affected versions]:**
- Firefox Nightly 106.0a1 (Build ID: 20220825222149)

**[Affected Platforms]:**
- macOS 12.5.1
- Windows 10 x64
- Ubuntu 20.04 x64

**[Prerequisites]:**
- Have the Firefox browser installed and opened.
- Have the “browser.aboutwelcome.templateMR” pref set to true.
- Have the dark theme of the browser enabled.

**[Steps to reproduce]:**
1. Navigate to the “about:welcome” page.
2. Observe the arrow from the “Skip this step” button.

**[Expected result]:**
 - The arrow is correctly displayed and visible.

**[Actual result]:**
 -  The arrow is black and is hardly visible.

**[Notes]:**
- This issue is also reproducible on existing users’ onboarding.
- Based on [Figma](https://www.figma.com/file/2TrMkNefxzhMCXjUqM8KIy/MR1-2022-Onboarding?node-id=4855%3A118871), the arrow should have the same color as the “Skip this step” text.
- Attached is a screenshot of the issue.