av9ash/GitBugs huggingface dataset:
Bug: Intermittent TV browser/components/preferences/tests/browser_privacy_syncDataClearing.js | single tracking bug
Status: NEW
Priority: P5
Created: 2024-04-26 09:00:22+00:00
Resolved: 2024-05-27 07:03:43+00:00

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

---
```
[task 2024-04-26T08:36:19.047Z] 08:36:19     INFO - TEST-PASS | browser/components/preferences/tests/browser_privacy_syncDataClearing.js | DeleteOnClose is set accordingly to the private Browsing autostart pref, selected - 
[task 2024-04-26T08:36:19.048Z] 08:36:19     INFO - Buffered messages logged at 08:36:18
[task 2024-04-26T08:36:19.048Z] 08:36:19     INFO - Leaving test bound test_initialState
[task 2024-04-26T08:36:19.049Z] 08:36:19     INFO - Buffered messages finished
[task 2024-04-26T08:36:19.050Z] 08:36:19     INFO - TEST-UNEXPECTED-FAIL | browser/components/preferences/tests/browser_privacy_syncDataClearing.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-04-26T08:36:19.050Z] 08:36:19     INFO - GECKO(1066) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2024-04-26T08:36:19.051Z] 08:36:19     INFO - GECKO(1066) | MEMORY STAT | vsize 16266MB | residentFast 355MB | heapAllocated 176MB
[task 2024-04-26T08:36:19.051Z] 08:36:19     INFO - TEST-OK | browser/components/preferences/tests/browser_privacy_syncDataClearing.js | took 49230ms
```
Bug: [Experiment]The experiment's What's New page is not localized
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-04-26 11:13:52+00:00
Resolved: 2024-04-30 11:41:14+00:00

**[Affected versions]:**
- Firefox Beta 126.0b5 (Build #20240424091756)

**[Affected Platforms]:**
- Windows 11 x64
- macOS 13.6.2
- Ubuntu 22.04 x64

**[Prerequisites]:**
- Have the latest Firefox Beta 125 installed using a non-English locale (DE or FR).
- Have a browser profile enrolled in the Control or Treatment A branches of the [WNP Messaging System + Nimbus Tooling](https://experimenter.services.mozilla.com/nimbus/wnp-messaging-system-nimbus-tooling/summary) experiment.

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Update the browser to Beta 126.
3. Observe the 126 What's New page.

**[Expected result]:**
- The WNP is localized in the build's language.

**[Actual result]:**
- The WNP is displayed in English regardless of the build language.

**[Notes]:**
- The issue is most likely caused by the Nimbus override URL, since the en-US locale is hardcoded in the link. 
"overrideUrl": "https://www.mozilla.org/en-US/firefox/126.0beta/whatsnew/?nimbusBranch=control"
- Attached a screenshot of the issue:
Bug: Intermittent browser/components/translations/tests/browser/browser_translations_select_panel_select_same_from_and_to_languages_from_dropdown_menu.js (finished) | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2024-04-26 13:09:27+00:00
Resolved: 2025-01-08 12:09:47+00:00

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

---
```
[task 2024-04-26T12:41:24.873Z] 12:41:24     INFO - TEST-OK | browser/components/translations/tests/browser/browser_translations_select_panel_select_same_from_and_to_languages_from_dropdown_menu.js | took 3121ms
[task 2024-04-26T12:41:24.879Z] 12:41:24     INFO - checking window state
[task 2024-04-26T12:41:24.880Z] 12:41:24     INFO - GECKO(2857) | must wait for focus
[task 2024-04-26T12:47:34.972Z] 12:47:34     INFO - TEST-UNEXPECTED-TIMEOUT | browser/components/translations/tests/browser/browser_translations_select_panel_select_same_from_and_to_languages_from_dropdown_menu.js (finished) | application timed out after 370 seconds with no output
[task 2024-04-26T12:47:34.972Z] 12:47:34     INFO - TEST-INFO 
```
Bug: Pin notification does not appear anymore in a Windows session if stressed enough (no clear steps for now)
Status: NEW
Priority: --
Created: 2024-04-26 13:58:56+00:00
Resolved: 2024-05-18 20:27:57+00:00

**Found in**
* Latest Nightly 127.0a1

**Affected versions**
* Latest Nightly 127.0a1

**Tested platforms**
* Affected platforms: Windows 11 Dev and Canary channels only - 24h2 (26080.1 and 26100.1)
* Unaffected platforms: MacOS and Ubuntu

**Steps to reproduce**
1. Install latest Nightly (.exe)
2. Visit about:welcome page
3. Leave only `Pin Nightly to taskbar` checked
4. Click on the `Save and continue` button
5. Repeat the above steps a few more times

**Expected result**
* A system notification is displayed asking the user to pin Firefox to taskbar.

**Actual result**
* We reach a point where the notification does not appear anymore even after a browser restart, the only "cure" we found is to restart the Windows machine. 

**Regression range**
* Not a regression since this is a new implementation.

**Additional notes**
* Unfortunately we don't have exact steps for this at this time, we'll try and find some asap. 
* I said to have this logged for now and edit it as soon as we have clear steps for this scenario.
Bug: Revamped sidebar buttons are displaying with a repeated background, wrong background color
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-04-26 14:15:18+00:00
Resolved: 2024-05-06 14:20:20+00:00

Looks like this is due to an issue with some recent `moz-button` changes interpreting white space as a label, and styling these buttons as if they have a label. Because the white space is likely coming from how the code is formatted, we should address this in `moz-button`.
Bug: Extensions in revamped sidebar aren't being disabled/enabled as expected
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2024-04-26 15:38:21+00:00
Resolved: 2024-05-08 03:50:58+00:00

With a clean profile, when disabling the extension, the entrypoint disappears from the new sidebar as expected. However, the extension never seems to reappear after re-enabling the extension.

Updated STR:
Enable the sidebar.revamp pref by setting to true
Install a sidebar extension such as Sidebery
Restart the browser with the extension installed/enabled
On the manage extensions page, disable the Sidebery extension
Re-enable the extension and notice the entrypoint never returns to the sidebar

This doesn't seem to occur the same way whenever you load the browser with an extension not already installed/enabled beforehand.

Two console errors I'm seeing consistently when hitting this issue that I will attach a screenshot of. One seems to be about removing an event listener for the extension, and the other seems to occur when you attempt to re-enable the extension. `sidebar` is undefined `[here](https://searchfox.org/mozilla-central/source/browser/components/sidebar/browser-sidebar.js#659)`.

Jonathan, maybe you can take a look?
Bug: CFR 'addon_recommendation' layout renders broken page action buttons in urlbar
Status: NEW
Priority: P3
Created: 2024-04-26 15:43:46+00:00
Resolved: 2024-05-13 15:50:06+00:00

Pr-requisite
Create CFR with layout as `addon_recommendation` , template as `CFR_doorhanger` and `skip_address_bar_notifier` as false similar to [YOUTUBE_ENHANCE_3 message here](https://searchfox.org/mozilla-central/rev/279e588a6d5fcb2f652fc26345ddb2a3b4d58b0e/browser/components/asrouter/modules/CFRMessageProvider.sys.mjs#221)

STR:
1.  Go to devtools
2. Click Show button next to YOUTUBE_ENHANCE_3 message
3. Page Action buttons in UrlBar doesn't render correct

This could be an underlying reason for intermittent seen in [browser_asrouter_cfr tests](https://searchfox.org/mozilla-central/rev/279e588a6d5fcb2f652fc26345ddb2a3b4d58b0e/browser/components/asrouter/tests/browser/browser_asrouter_cfr.js#29) that uses above properties for most of its test cases

Noticed Page Action buttons shows correct with layout `icon_and_message` that  was fixed with Bug 1840867 and Bug 1831198
Bug: Tab previews don't show content PID
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-04-26 16:12:28+00:00
Resolved: 2024-04-26 16:15:35+00:00

Tab tooltips on Nightly normally show the process PID that the tab content is running in. This is pretty helpful for developers. However the new tab previews do not show this.
Bug: [RTL] The preview screenshots state is not visible
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-04-26 16:34:27+00:00
Resolved: 2024-05-05 00:55:02+00:00

In an RTL and on a page that has horizontal scrolling, the preview container is not visible or partially visible depending on the scrollX position.

See attached screenshot for issue
Bug: Update wallpaper onbaording to use updated prefs for setting wallpapers
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-04-26 18:20:41+00:00
Resolved: 2024-05-01 22:27:23+00:00

`browser.newtabpage.activity-stream.newtabWallpapers.wallpaper-dark` and `browser.newtabpage.activity-stream.newtabWallpapers.wallpaper-light`
Bug: Firefox logo on the about:newtab is hidden from the assistive technology
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2024-04-26 18:52:16+00:00
Resolved: 2024-10-03 09:49:11+00:00

The Firefox brand logo is not exposed to the assistive technology, while it does provide meaningful information for the user which is not duplicated in text elsewhere on the page.

Provide [a textual alternative](https://www.w3.org/WAI/tutorials/images/informative/) to the image, i.e. `Firefox` - this would ensure screen reader users who cannot see or understand the screen visually would still be provided the same level of assurance and transparency where this whole page is coming from (from the Fx).

I.e. `<div class="logo-and-worldmark">` could get `role="image" aria-label="Firefox"` to achieve that.

Note that this bug is a high severity `access-S3` because the lack of the brand information exposure may affect the trust in the content for a screen reader user.
Bug: `...` Open menu buttons on the about:newtab are missing the expanded state
Status: NEW
Priority: --
Created: 2024-04-26 19:04:14+00:00
Resolved: 2024-10-02 17:37:11+00:00

### STR:
1. Ensure a screen reader is running
1. Using keyboard alone, navigate to one of `...` buttons and activate it with `Enter` or `Space` key
1. Observe the announcement

### Current:
1. The `...` Open Menu buttons that are provided for each of the tiles and cards on the `about:newtab` page does not indicate to a screen reader user when the menu is opened

### Expected:
When a menu is opened, a screen reader is made aware of that either by:
* `expanded` state being announced, per [WAI ARIA design pattern](https://www.w3.org/WAI/ARIA/apg/patterns/menu-button/):
> When the menu is displayed, the element with role button has `aria-expanded` set to `true`. When the menu is hidden, `aria-expanded` is set to `false`. 
* by focus moving to the topmost option in the menu
Bug: Links of cards on the discovery stream on the about:newtab are missing context
Status: NEW
Priority: --
Created: 2024-04-26 19:31:06+00:00
Resolved: 2025-02-10 05:25:35+00:00

### STR:
1. Ensure a screen reader is running
1. Using keyboard alone, navigate to one of cards in the `Thought-provoking stories` section and focus it with `Tab`
1. Observe the announcement
1. In [browse mode of a screen reader](https://www.accessibility-developer-guide.com/knowledge/screen-readers/desktop/browse-focus-modes/) (i.e. by using `Down Arrow` with NVDA and `ctrl+opt+Down Arrow` by default with VoiceOver) review the content of each card

### Current:
1. (with `Tab`) Only the title of the link is announced by a screen reader while the short URL, description, and sponsored tag (when present) are skipped while they are all visually included in the focused element, i.e. the card on the screenshot visually has the following content (marked what's ignored/announced):
    1. business.walmart.com URL *[skipped]*
    1. `Catch these Lightning Deals` title *[announced]*
    1. `Save up to 65% in the Walmart Business flash sale.` text *[skipped]*
    1.  `Sponsored by Walmart Business` footer text *[skipped]*
1. (with browsing) The title of the link is injected at the beginning of the card and then repeated after the URL that creates a redundancy and does not follow the visual reading order.

### Expected:
1. (with `Tab`) Each link should provide a context for a . Otherwise, screen reader users may While it does not have to be visually marked up as a link, it could be referred from the hyperlink via `aria-describedby`, or included in the grouping like `<article>`
1. (with browsing) Avoid redundancy in the announcement and ensure the visual reading order of the page is followed by the programmatic reading order

### Recommendation:
use any of the Card guidance provided by [Adrian Roselli's blog](https://adrianroselli.com/2020/02/block-links-cards-clickable-regions-etc.html) or [Heydon Pickering's Inclusive Components](https://inclusive-components.design/cards/)
Bug: Ensure the about:newtab supports HCM on Windows, incl. support for the focus indication
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-04-26 19:41:18+00:00
Resolved: 2024-12-04 03:33:51+00:00

Ensure the Windows High Contrast Mode is supported by providing [forced-colors](https://blogs.windows.com/msedgedev/2020/09/17/styling-for-windows-high-contrast-with-new-standards-for-forced-colors/) styling in accordance with the [HCM references (internal only)](https://www.figma.com/file/w4zKuXo3sn4y9q2NdMCXY4/High-Contrast-Mode?type=design&node-id=1220-13131&mode=design). 

Please refer to the [documentation on how these queries are used in source docs](https://firefox-source-docs.mozilla.org/accessible/HCMMediaQueries.html). You can also view [this live Media Query Checker site](https://mreschenberg.com/MediaQueryChecker.html) to play around with your OS/browser settings and see which queries are activated or deactivated and how the system colors like `ButtonText` and `ButtonFace` are expected to be rendered on your version of Windows OS (for the `forced-colors` mode).
Bug: Save to Pocket buttons on the about:newtab cards are missing the Pocket in their accessible name
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-04-26 19:49:57+00:00
Resolved: 2024-10-03 09:49:16+00:00

### STR:
1. Ensure a screen reader is running
1. Using keyboard alone, navigate to one of `Save to Pocket` buttons on the activity stream cards in the `Thought-provoking stories` section
1. Observe the announcement

### Current:
1. The Save to Pocket buttons do not indicate to a screen reader user that the Pocket is involved, it is only announced as `Save`

### Expected:
1. The button's visual label is the same as the accessible/programmatic one - i.e. `Save to Pocket` or `Pocket: Save`, etc. - ensure the Pocket is mentioned since it is included in the visual label and provides important information of the function of the button. 

Note: since there is an on-screen image, it is possible to follow the [Informative images](https://www.w3.org/WAI/tutorials/images/informative/) guide to provide its with an textual alternative, which would be then automatically included in the accessible name calculation for the button.
Bug: The only heading on the about:newtab is H3
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-04-26 19:55:02+00:00
Resolved: 2024-10-15 21:47:12+00:00

The `Thought-provoking stories. Learn more` is the only heading that the New Tab page has. And this heading is `<h3>`.

Per [the WebAIM Screen Reader User Survey #10 results](https://webaim.org/projects/screenreadersurvey10/#problematic), `Missing or improper headings` were included in Top-10 list of problematic itemd in the overall rating of difficulty and frustration for screen reader users. [80% of the responders are relying on some form of markup to find information on a lengthy page](https://webaim.org/projects/screenreadersurvey10/#finding), among them 71.6% of responders are likely to use headings first. The reported usefulness of heading levels for navigation has increased over time, and [88.8% of respondents find them very or somewhat useful](https://webaim.org/projects/screenreadersurvey10/#heading).

While there are no other visual headings, there is no requirement to add any other (programmatic) headings (at the same time, the Firefox logo could be made in a heading based on its visual position and importance, as well as the importance of its meaning), but it is expected that the heading hierarchy would be appropriate. Each page has to have one and only one heading level 1 (`<h1>`). It’s like a title to a book.

The heading level should be adjusted in this case. I.e. if the Firefox logo is marked up as `<h1>`, the stories heading would be `<h2>`.
Bug: Confirm before closing multiple tabs - Strings don't match expectation
Status: NEW
Priority: P3
Created: 2024-04-26 20:03:34+00:00
Resolved: 2024-07-15 18:50:19+00:00

Steps to reproduce:

Go to about:preferences 
1. Check ON "Confirm before closing multiple tabs"

Open several tabs and right-click on a tab to open the context menu and select" Close Multiple Tabs" - Select any of the options that would close multiple tabs (i.e "Close tabs to the left" if you have several tabs on the left of the selected tab). 

Expected:
I get a confirmation about if I want to close multiple tabs

Actual:
No warning is given and tabs are closed. The warning is triggered when a user closes a window with 25 tabs or more. 

Recommendation:
Rather than change the behaviour, I would recommended we change the strings in the settings menu to something like "Confirm before closing a window with multiple tabs" or "Confirm before closing a window" since this is what actually happens. The confirmation appears when you close a window with multiple tabs opened. Also I'm not sure if it needs to be 25 tabs or more to see the confirmation which it currently does now.
Bug: Nothing is announced by NVDA after hovering over card images and the "..." button on activity stream
Status: NEW
Priority: --
Created: 2024-04-26 20:09:19+00:00
Resolved: 2024-05-13 12:13:58+00:00

### STR:
1. Ensure a NVDA screen reader is running
1. Hover over one of cards in the `Thought-provoking stories` section
1. Observe the announcement
1. Hover over one of the `...` Open menu buttons on cards in the `Thought-provoking stories` section
1. Observe the announcement

### Current:
1. Nothing is announced by NVDA after hovering over card images and the `...` buttons on activity stream

### Expected:
1. Card title would be announced when hovered, the button label would be announced when hovered

### Note:
While a button or a link does not have any visible text always, NVDA will not read the label, which is a [known issue with NVDA mouse tracking](https://github.com/nvaccess/nvda/issues/12047).

Since the button does have an accessible name provided (which can be checked in the Devtools Accessibility inspector), the lack of on-hover announcement, in this case, is the NVDA bug. That's being said, it as `access-s3` since this is not a delightful pattern in any case + the on-hover nature of the `...` controls and lack of any alternative way to access their functionality (covered in bug 1893509) does show that the Firefox could do better even while there is an issue with the assistive technology software.

#### Recommendation is either:
1. to add an on-screen text (like the `Save` to Pocket button does which at least has this text announced on hover), so there is an on-screen text (that is included in the markup) - this should be announced by the NVDA.
1. to add an invisible `<span>` in the button as Calixte offered in [the bug 1886964#c1](https://bugzilla.mozilla.org/show_bug.cgi?id=1886964#c1) and in the attached patch. This would also work as an accessible name source for the button.
Bug: Keyboard navigation within lists of tiles, cards, and footer improvements for about:newtab
Status: NEW
Priority: --
Created: 2024-04-26 20:39:55+00:00
Resolved: 2024-11-21 22:09:38+00:00

The keyboard navigation on the New Tab page is cumbersome and the headings and other landmarks are absent making it harder to navigate within the page (bug 1893734). To get to the footer links, a user has to press `Tab` *75 times* (while visually there are 33 focusable elements).

Because the 8 tiles (items 2-17 in the focus order) and 21 story cards (items 19-75) as well as footer list of links (items 76-81) are groups of similar items, we could use the arrow navigation within each of these groups to allow keyboard-only, switch control, and other alternative input devices users to quicker navigate between these groups. 

### Expected focus order (with `Tab` key presses):
1. Settings button
1. Search input (bug 1865210)
1. First tile
1. `Learn more` link
1. First story card/link
1. First link in the footer (`Self improvement` popular topic at the time of reporting)
1. `Privacy policy` link

The other elements within these groups are focusable with arrow keys as a spacial navigation. Follow the Firefox View navigation example within the `<main>` area
Bug: Intermittent browser/components/urlbar/tests/browser/browser_UrlbarInput_overflow_resize.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2024-04-26 21:03:45+00:00
Resolved: 2024-05-22 12:03:26+00:00

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

---
```
[task 2024-04-26T19:30:05.698Z] 19:30:05     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_UrlbarInput_overflow_resize.js | Check The input field overflows - 5527 > 268 - 
[task 2024-04-26T19:30:05.699Z] 19:30:05     INFO - Buffered messages finished
[task 2024-04-26T19:30:05.700Z] 19:30:05     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_UrlbarInput_overflow_resize.js | Uncaught exception in test bound  - The urlbar input field is completely scrolled to the end - timed out after 50 tries.
[task 2024-04-26T19:30:05.701Z] 19:30:05     INFO - Leaving test bound 
[task 2024-04-26T19:30:05.701Z] 19:30:05     INFO - Closing the view directly
[task 2024-04-26T19:30:05.702Z] 19:30:05     INFO - Waiting for the view to close
[task 2024-04-26T19:30:05.702Z] 19:30:05     INFO - Urlbar view closed
[task 2024-04-26T19:30:05.703Z] 19:30:05     INFO - GECKO(2860) | console.warn: SessionStore: "Discarding window with 0 saveable tabs and 0 closed tabs"
[task 2024-04-26T19:30:05.704Z] 19:30:05     INFO - GECKO(2860) | console.warn: SessionStore: "Discarding window with 0 saveable tabs and 0 closed tabs"
[task 2024-04-26T19:30:05.839Z] 19:30:05     INFO - GECKO(2860) | MEMORY STAT | vsize 941MB | vsizeMaxContiguous 1293MB | residentFast 241MB | heapAllocated 89MB
[task 2024-04-26T19:30:05.840Z] 19:30:05     INFO - TEST-OK | browser/components/urlbar/tests/browser/browser_UrlbarInput_overflow_resize.js | took 10554ms
```