av9ash/GitBugs huggingface dataset:
Bug: Intermittent browser/components/places/tests/browser/browser_editBookmark_tags_liveUpdate.js | single tracking bug
Status: NEW
Priority: P5
Created: 2022-12-08 00:54:55+00:00
Resolved: 2024-02-27 18:04:16+00:00

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

---
```
[task 2022-12-08T00:16:04.923Z] 00:16:04     INFO - TEST-PASS | browser/components/places/tests/browser/browser_editBookmark_tags_liveUpdate.js | Sanity check: gEditItemOverlay is in context - 
[task 2022-12-08T00:16:04.923Z] 00:16:04     INFO - TEST-PASS | browser/components/places/tests/browser/browser_editBookmark_tags_liveUpdate.js | Correctly added tag to a single bookmark - 
[task 2022-12-08T00:16:04.924Z] 00:16:04     INFO - TEST-PASS | browser/components/places/tests/browser/browser_editBookmark_tags_liveUpdate.js | Editing a single bookmark shows the added tag. - "test-tag" == "test-tag" - 
[task 2022-12-08T00:16:04.924Z] 00:16:04     INFO - Buffered messages finished
[task 2022-12-08T00:16:04.925Z] 00:16:04     INFO - TEST-UNEXPECTED-FAIL | browser/components/places/tests/browser/browser_editBookmark_tags_liveUpdate.js | Check tags list - Got +0, expected 1
[task 2022-12-08T00:16:04.925Z] 00:16:04     INFO - Stack trace:
[task 2022-12-08T00:16:04.925Z] 00:16:04     INFO - chrome://mochikit/content/browser-test.js:test_is:1477
[task 2022-12-08T00:16:04.925Z] 00:16:04     INFO - chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_editBookmark_tags_liveUpdate.js:checkTagsSelector:5
[task 2022-12-08T00:16:04.925Z] 00:16:04     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-12-08T00:16:04.926Z] 00:16:04     INFO - TEST-UNEXPECTED-FAIL | browser/components/places/tests/browser/browser_editBookmark_tags_liveUpdate.js | Found expected number of tags in the tags selector - Got +0, expected 1
[task 2022-12-08T00:16:04.926Z] 00:16:04     INFO - Stack trace:
[task 2022-12-08T00:16:04.927Z] 00:16:04     INFO - chrome://mochikit/content/browser-test.js:test_is:1477
[task 2022-12-08T00:16:04.927Z] 00:16:04     INFO - chrome://mochitests/content/browser/browser/components/places/tests/browser/browser_editBookmark_tags_liveUpdate.js:checkTagsSelector:8
[task 2022-12-08T00:16:04.928Z] 00:16:04     INFO - TEST-PASS | browser/components/places/tests/browser/browser_editBookmark_tags_liveUpdate.js | The tag has been removed - 
```
Bug: Intermittent browser/actors/test/browser/browser_nested_link_clicks.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2022-12-08 07:20:58+00:00
Resolved: 2023-01-03 17:01:15+00:00

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

---
```
[task 2022-12-08T06:36:44.749Z] 06:36:44     INFO - TEST-START | browser/actors/test/browser/browser_nested_link_clicks.js
[task 2022-12-08T06:36:59.810Z] 06:36:59     INFO - GECKO(924) | 2022-12-08 06:36:59.808 firefox[924:14476] Persistent UI failed to open file file:///Users/cltbld/Library/Saved%20Application%20State/org.mozilla.nightly.savedState/window_1.data: No such file or directory (2)
[task 2022-12-08T06:37:29.801Z] 06:37:29     INFO - TEST-INFO | started process screencapture
[task 2022-12-08T06:37:29.936Z] 06:37:29     INFO - TEST-INFO | screencapture: exit 0
[task 2022-12-08T06:37:29.937Z] 06:37:29     INFO - Buffered messages logged at 06:36:44
[task 2022-12-08T06:37:29.937Z] 06:37:29     INFO - Entering test bound nested_link_click_opens_single_tab
[task 2022-12-08T06:37:29.937Z] 06:37:29     INFO - Buffered messages finished
[task 2022-12-08T06:37:29.937Z] 06:37:29     INFO - TEST-UNEXPECTED-FAIL | browser/actors/test/browser/browser_nested_link_clicks.js | Test timed out - 
[task 2022-12-08T06:37:29.937Z] 06:37:29     INFO - GECKO(924) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2022-12-08T06:37:29.937Z] 06:37:29     INFO - GECKO(924) | MEMORY STAT | vsize 402267MB | residentFast 330MB | heapAllocated 116MB
[task 2022-12-08T06:37:29.937Z] 06:37:29     INFO - TEST-OK | browser/actors/test/browser/browser_nested_link_clicks.js | took 45055ms
```
Bug: Datepicker is closed when trying to reach its controls using Tab and Shift + Tab
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-12-08 10:53:42+00:00
Resolved: 2022-12-08 11:05:50+00:00

**Found in**
* Firefox Nightly 109.0a1

**Affected versions**
* Firefox Nightly 109.0a1

**Tested platforms**
* Affected platforms: Windows 10
* Unaffected platforms: to be checked

**Preconditions**
* Firefox Nightly installed

**Steps to reproduce**
1. Open datepicker and leave it open
2. Click on either the  mm, dd or yyyy from date input field using the mouse
3. Use TAB key to navigate inside the date input field and reach calendar button
4. Hit TAB key again

**Expected result**
* The datepicker should be kept open and user should be able to reach its controls using Tab and Shift + Tab.


**Actual result**
* The datepicker is closed when using TAB as described in STR.

**Regression range**
* Not a regression because these improvements were recently implemented through Bug 1676068.
Bug: Orca and Voice Over screen readers do not read out loud the Datepicker fields correctly
Status: NEW
Priority: --
Created: 2022-12-08 13:55:17+00:00
Resolved: 2022-12-14 00:40:25+00:00

**Found in**
* 109.0a1 (2022-12-07)

**Affected versions**
* Firefox Nightly 109.0a1 (2022-12-07)

**Affected platforms**
* Ubuntu, Mac

**Preconditions**
* Enable Orca - Ubuntu
* Enable Voice over - Mac

**Steps to reproduce**
1. Reach url: data:text/html,<input type='datetime-local'>
2. Reach each field from the Date picker using Tab key.

**Expected result**
* Each field should be read out loud correctly by the screen readers i.e. Month spin button, Day spin button

**Actual result**
* Orca reads: mm spin button, dd spin button.
* Voice Over reads: nan month stepper, nan day stepper

**Regression range**
This issue is not a regression.
Bug: mm/dd/yyyy from date input field incorrectly read out loud by screen reader NVDA
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-12-08 14:24:15+00:00
Resolved: 2023-01-05 03:21:28+00:00

**Found in**
*  Firefox Nightly 109.0a1

**Affected versions**
*  Firefox Nightly 109.0a1

**Tested platforms**
* Affected platforms: Windows 10
* Unaffected platforms: similar Bug 1804674

**Preconditions**
* Firefox Nightly installed
* Screen Reader NVDA is enabled

**Steps to reproduce**
1. Reach data:text/html, <input type='date'>
2. Hover over the mm/dd/yyyy placeholder in the date input field

**Expected result**
* Each element inside the date input field should be read out loud correctly by the screen reader(Month spin button, Day spin button, Year spin button)

**Actual result**
* The elements inside the date input field are read out loud by the screen reader mm,dd,yyyy.

**Regression range**
* Not a regression because these improvements were recently implemented through Bug 1676068.
Bug: Space bar scrolls down when used in the month/year spin selection buttons
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-12-08 15:18:41+00:00
Resolved: 2022-12-21 14:59:25+00:00

**Found in**
* Firefox Nightly 109.0a1

**Affected versions**
* Firefox Nightly 109.0a1

**Tested platforms**
* Affected platforms: Windows 10, Ubuntu 18, macOS 11
* Unaffected platforms: none

**Preconditions**
*  Firefox Nightly installed

**Steps to reproduce**
1. Open the datepicker
2. Click on month/year button
3. Focus by hitting TAB the month or year spin toggle button
4. Hit Space bar

**Expected result**
* Space bar should have identical behavior as the Enter key it should *close the month-year selection panel, returning the focus to the month-year toggle button. Closing the entire panel would also suffice, because technically the panel with spinners replaces the calendar panel*.

**Actual result**
* Space bar scrolls down when used in the month/year spin selection buttons

**Regression range**
* Not a regression because these improvements were recently implemented through Bug 1676068.
Bug: [MacOS] Unable to reach and navigate between Datepicker controls using Voice Over commands
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-12-08 15:20:32+00:00
Resolved: 2023-03-28 07:37:04+00:00

**Found in**
* 109.0a1 (2022-12-07)

**Affected versions**
* Firefox Nightly 109.0a1 (2022-12-07)

**Affected platforms**
* Mac

**Preconditions**
* Enable Voice over - Mac

**Steps to reproduce**
1. Reach url: data:text/html,<input type='datetime-local'>
2. Use the Voice over commands to reach the Calendar button from the Datepicker.

**Expected result**
* VO Shift Down/UP, Vo Left/Right arrows and VO Space should work with the Datepicker controls.
* Reaching the Month/Day/Year/Hour/Minute/PM/AM fields should allow the user to change their values with the Up/Down arrow keys, or VO UP/Down ? maybe.

**Actual result**
* Unable to reach the Datepicker fields or the Calendar button using Voice Over commands.
* Jumping inside the Datepicker using the Tab key will not allow the user to change its Values using Up/Down arrow keys.
* Left/Right arrow keys also do not work when Voice Over is enabled and the user is unable to switch between Month/Day/Year with them.

**Regression range**
15:44.81 INFO: Last good revision: ab4472f175ecce33ae405f205ac40ef64fbe4a5d
15:44.81 INFO: First bad revision: 5fae4f191812aa1cd68b66e4e5d2e88c1725969e
15:44.81 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ab4472f175ecce33ae405f205ac40ef64fbe4a5d&tochange=5fae4f191812aa1cd68b66e4e5d2e88c1725969e

It seems that bug 1798438 is the cause of this issue.
Bug: Make Search SERP Telemetry work with multiple providers using the same ad provider
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2022-12-08 18:53:54+00:00
Resolved: 2023-07-10 06:21:46+00:00

As our telemetry is currently instrumented, when different search engines show SERP ads that are served from the same ad provider, we have no way of distinguishing between those search engines. We need to correct this bug before adding any new telemetry for SERPs where different search engines are using the same ad provider.
Bug: [QuickActions] Regression: Buttons no longer have the same size when shrinking the window to a smaller size
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-12-08 20:12:48+00:00
Resolved: 2023-01-09 16:33:50+00:00

Nightly 109.0a1 (2022-12-08) (64-Bit)
macOS 12.6.1

Steps to reproduce:

1.) Click into the Addressbar, so that the Dropdown opens
2.) Shrink the window to its smallest width

Actual: The Quickactions Button for Bookmarks and Downloads are larger than the other buttons

Expected: They all should calculate the same size.

This is a recent regression.
Bug: Enzyme assertions in unit tests are always passing
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-12-08 23:22:51+00:00
Resolved: 2022-12-13 04:14:21+00:00

Many of our React unit tests have this form `assert.ok(wrapper.find(selector))` (the wrapper is from enzyme). But that is always going to pass unless the selector is not a valid string, because ReactWrapper::find always returns a ReactWrapper, it's just an empty wrapper if nothing was found. The result is that our unit tests can't catch many regressions, because these assertions always pass for any string value.

Instead, I think we should use `assert.ok(wrapper.find(selector).exists())`

Hopefully most of our tests will still work after fixing this issue, though some of the tests are only passing because of this issue. For example, [this test](https://searchfox.org/mozilla-central/rev/9423bbd90c59ef7739c8453c265d04d8cf07ce73/browser/components/newtab/test/unit/aboutwelcome/MultiStageAboutWelcome.test.jsx#274-286) looks like it's for an old version of the StepsIndicator component. There is no currentScreen property, and the StepsIndicator component itself does not render a `<div class="steps"/>` element, it just returns the children. The actual `div.steps` is the parent element. So tests like this will need to be updated to account for the current source code.

Bug 1778409 intends to ditch Enzyme, but I would still like to fix this in the meantime.
Bug: Add Glean equivalent for legacy telemetry reach/impression/exposure event used by Nimbus
Status: RESOLVED
Priority: P1
Resolution: WORKSFORME
Created: 2022-12-09 00:01:55+00:00
Resolved: 2024-02-21 19:24:49+00:00

I went to implement Bug 1790448 only to discover that the relevant reach/impression/exposure event is reported only by legacy Telemetry and not by Glean.  This ticket tracks adding the Glean equivalent in [_ASRouter._recordReachEvent](https://searchfox.org/mozilla-central/rev/9423bbd90c59ef7739c8453c265d04d8cf07ce73/browser/components/newtab/lib/ASRouter.jsm#1837).

But perhaps these reach events are already covered by the Glean exposure event in [ASRouter.jsm](https://searchfox.org/mozilla-central/rev/9423bbd90c59ef7739c8453c265d04d8cf07ce73/browser/components/newtab/lib/ASRouter.jsm#1883)?  I believe these are distinct concepts but this isn't my area of expertise.
Bug: [QuickActions] Translations are missing
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-12-09 08:13:51+00:00
Resolved: 2023-01-05 05:21:28+00:00

109.0a1 (2022-12-08) (64-Bit)
macOS 12.6.1

1.) Use Nightly in Language DE
2.) Take a look at the Quickactions descriptions

Actual: A lot of translations are missing. They are shown in Language EN/US. 
Expected: They should be translated.

Thanks :)
Bug: NVDA screen reader doesn't read the prev/next arrows of the datepicker on hover
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2022-12-09 08:56:22+00:00
Resolved: 2023-01-05 03:10:19+00:00

**Found in**
* Firefox Nightly 109.0a1

**Affected versions**
* Firefox Nightly 109.0a1
*  Firefox 102.5.0esr
* Firefox 107.0.1
* Firefox 108.0b9

**Tested platforms**
* Affected platforms: Windows 10
* Unaffected platforms: none

**Preconditions**
* Firefox Nightly installed
* NVDA screen reader is enabled

**Steps to reproduce**
1. Open the datepicker available on one of the websites:

https://mathislucka.github.io/a11y-datepicker/
https://duetds.github.io/date-picker/
https://fymmot.github.io/inclusive-dates/
https://www.w3.org/WAI/ARIA/apg/example-index/dialog-modal/datepicker-dialog.html
https://dequeuniversity.com/library/aria/date-picker
https://hanshillen.github.io/jqtest/#goto_datepicker
https://haltersweb.github.io/Accessibility/date-picker.html
https://assets.cms.gov/resources/framework/2.0/Pages/datepicker.html
https://z01z2.csb.app/
https://react-dates.github.io/react-dates/?path=/story/daterangepicker-drp--default

2. Hover over the prev/next arrows for year or month inside the datepicker

**Expected result**
* NVDA screen reader should read out loud the arrows  of the datepicker on hover.

**Actual result**
* NVDA screen reader doesn't read the arrows of the datepicker on hover(such as prev/next year and month arrows)

**Regression range**
* Not a regression.
Bug: The autoplay permission for about:welcome does not save the user choice
Status: NEW
Priority: P3
Created: 2022-12-09 09:15:06+00:00
Resolved: 2022-12-14 14:37:24+00:00

**Found in**
* 109.0a1 (2022-12-09)

**Affected versions**
* 109.0a1

**Tested platforms**
* Affected platforms: Windows 10, macOS 12, Ubuntu 20.

**Steps to reproduce**
1. Launch Firefox with new profile.
2. Open about:preferences#privacy > Permissions
3. Click on Autoplay Settings
4. Change the about:welcome status value and click Save Changes.
5. Click on Autoplay Settings.

**Expected result**
* The about:welcome changed value is saved.

**Actual result**
* The about:welcome changed value is not saved.

**Regression range**
Not a regression. This is happening since bug 1799997 landed (new implementation).

**Additional notes**
* I'm not sure if the second row from Autoplay Settings is expected, the about:welcome^privateBrowsingld=1 is displayed. Just let me know if I should file a new issue for it.
Bug: The Months and Years spinners from Datepickers are not being read by NVDA on Hover
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2022-12-09 10:57:12+00:00
Resolved: 2023-01-11 00:01:55+00:00

**Found in**
* 109.0a1 (2022-12-09)

**Affected versions**
* Firefox Nightly 109.0a1 (2022-12-09)

**Affected platforms**
* Windows

**Preconditions**
* Enable NVDA.

**Steps to reproduce**
1. Reach url: data:text/html,<input type='datetime-local'>
2. Open the Calendar.
3. Click the Month/Year button from the calendar.
4. Hover the mouse cursor over any other month or year from the spinners.

**Expected result**
* The previous or next months displayed in the Month spinner should be read out loud by the NVDA on Hover.
* Other Years from the Years spinner should also be read out loud on Hover by the NVDA.

**Actual result**
* The Months and Years from the Spinners are not read out loud by the NVDA when we mouse hover them.

**Regression range**
I will try to get a manual regression for this issue later on since builds started with the mozregression tool are not being read by NVDA.
However I think this issue has been caused by the recent implementations to Datepickers.
Bug: Ctrl + Home and Ctrl + End don't select the first day/last of the current month inside Datepicker Dialog Example
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-12-09 11:05:11+00:00
Resolved: 2022-12-21 18:13:21+00:00

**Found in**
* Firefox Nightly 109.0a1

**Affected versions**
* Firefox Nightly 109.0a1

**Tested platforms**
* Affected platforms: Windows 10, Ubuntu 22.04
* Unaffected platforms:  macOS 13

**Preconditions**
* Firefox Nightly installed 

**Steps to reproduce**
1. Go to https://www.w3.org/WAI/ARIA/apg/example-index/dialog-modal/datepicker-dialog.html
2. Reach Calendar button(next to the date input field) by hitting TAB key
3. Once the datepicker is open, hit Ctrl + Home and Ctrl + End 

**Expected result**
* Ctrl + Home and Ctrl + End should select the first day/last of the current month

**Actual result**
* Ctrl + Home and Ctrl + End select the first day/last of the current week

**Regression range**
* Not a regression because these improvements were recently implemented through Bug 1676068.
Bug: NumLock deactivated in the date input field when using the keyboard number pad from the right side
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-12-09 12:10:39+00:00
Resolved: 2023-08-10 15:55:59+00:00

**Found in**
* Firefox Nightly 109.0a1

**Affected versions**
* Firefox Nightly 109.0a1

**Tested platforms**
* Affected platforms: Windows 10, Ubuntu 22.04
* Unaffected platforms: macOS 13

**Preconditions**
*  Firefox Nightly installed

**Steps to reproduce**
1. Reach data:text/html, <input type='date'>
2. Hit TAB to reach the date input field(or use mouse to click inside the field)
3. Use keyboard number pad from the right side to type any month/day/year(press 2)

**Expected result**
* You should be able to type in the date input field using the keyboard number pad from the right side.

**Actual result**
*  NumLock is deactivated once we reach the date input field and nothing can be typed in using the keyboard number pad from the right side.

**Regression range**
* Last good revision: 99052dd249cc79a752aeed699b8cb4633f3d2cd9
* First bad revision: fe7d9416e64121a3e2b356311b669f2a53052e7b
* Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=99052dd249cc79a752aeed699b8cb4633f3d2cd9&tochange=fe7d9416e64121a3e2b356311b669f2a53052e7b
* Potentially regressed by: Bug 1676068

**Additional notes**
* This issue is noticeable on other date input fields such as this one data:text/html, <input type='date'>:
data:text/html,<input type='datetime-local'>
https://carmacleod.github.io/playground/value-attr-tests.html
http://research.coolfields.co.uk/forms/html5-date.html
Bug: Tabs text and the "x" button overlap weirdly
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-12-09 12:49:42+00:00
Resolved: 2022-12-14 17:05:17+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:107.0) Gecko/20100101 Firefox/107.0

Steps to reproduce:

Open a page with long title in a tab


Actual results:

The text is cut not very beautifully


Expected results:

Not sure, maybe cut text before "x" button
Bug: attribution code is attempted to be written to the install directory for msix builds
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2022-12-09 13:49:13+00:00
Resolved: 2022-12-16 00:00:11+00:00

...which obviously won't work, because the directory is not writable.

The error, from a recent browser-chrome run:
[task 2022-12-09T00:10:22.073Z] 00:10:22     INFO - TEST-UNEXPECTED-FAIL | browser/components/newtab/test/browser/browser_aboutwelcome_attribution.js | Uncaught exception in test - NotAllowedError: Could not open the file at C:\Program Files\WindowsApps\Mozilla.MozillaFirefoxNightly_109.2212.820.0_x64__5x4grbbqzn2q4\VFS\ProgramFiles\MozillaFirefoxNightly Package Root\postSigningData for writing
Bug: browser/base/content/test/performance/browser_startup.js | resource://gre/modules/Preferences.sys.mjs is not allowed before first paint in MSIX builds
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-12-09 13:59:30+00:00
Resolved: 2022-12-15 09:31:46+00:00

[task 2022-12-09T00:03:07.968Z] 00:03:07     INFO - Stack trace:
[task 2022-12-09T00:03:07.968Z] 00:03:07     INFO - 0 DIST_applyPrefDefaults() ["resource:///modules/distribution.js":407:19]
[task 2022-12-09T00:03:07.968Z] 00:03:07     INFO - 1 DIST_applyCustomizations() ["resource:///modules/distribution.js":291:11]
[task 2022-12-09T00:03:07.969Z] 00:03:07     INFO - 2 BG__beforeUIStartup() ["resource:///modules/BrowserGlue.jsm":1265:33]
[task 2022-12-09T00:03:07.969Z] 00:03:07     INFO - 3 BG_observe() ["resource:///modules/BrowserGlue.jsm":938:13]

It looks like this is caused by the fact that we fail the condition at https://searchfox.org/mozilla-central/rev/196b6aa0427f38058fd43ac90ee94fcf2f436fb6/browser/components/distribution.js#402 and end up at the next statement.

I'm guessing the fix here is either except `mozilla-MSIX` from this check, or decide this is acceptable behaviour for these builds.

Mike, do you have any insight here?
Bug: update toolkit/components/normandy/test/browser/browser_ClientEnvironment.js expectations for MSIX builds
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2022-12-09 14:02:30+00:00
Resolved: 2022-12-16 00:00:13+00:00

This test is currently failing against MSIX builds because:  distribution has a default value - Got "mozilla-MSIX", expected "default"

`mozilla-MSIX` is correct here - and this test needs a minor update.
Bug: Update browser/components/uitour/test/browser_UITour.js expectations for MSIX builds
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2022-12-09 14:08:31+00:00
Resolved: 2022-12-16 00:00:16+00:00

This is [currently failing with](https://treeherder.mozilla.org/jobs?repo=try&revision=fb6e7c73c7e93e1bea50323cf3420206913eca86&selectedTaskRun=FsY_Q86LQOagv-2AKgLiCg.1): Should be "default" without preference set. - Got "mozilla-MSIX", expected "default"

...but `mozilla-MSIX` is the correct value for those builds.