av9ash/GitBugs huggingface dataset:
Bug: normalize.scss breaking some stuff on Firefox View
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-09-12 05:56:20+00:00
Resolved: 2022-09-23 10:27:38+00:00

Our sheet aboutwelcome.css is only [loaded](https://searchfox.org/mozilla-central/rev/9ddf68cc9e603276fc4c5253328cb3aeed6f0a55/browser/components/firefoxview/featureCallout.mjs#80-82) into firefox view when a feature callout is shown, so it doesn't always apply to about:firefoxview. When it is loaded, it affects the layout of the page and of some elements (see attachment) because of [normalize.scss](https://searchfox.org/mozilla-central/source/browser/components/newtab/content-src/styles/_normalize.scss). For example, check out the `.last-active-badge` - it's inheriting `box-sizing: border-box` from its parent. (That rule is a bit odd, since box-sizing is not supposed to be an inherited property anyway. Maybe `revert` would make more sense)
Bug: Firefox View text is slightly too large (which seems to break the layout of e.g. "Last Active" badge) after Firefox View feature tour landed
Status: RESOLVED
Priority: P2
Resolution: DUPLICATE
Created: 2022-09-12 06:29:19+00:00
Resolved: 2022-09-12 16:01:58+00:00

It looks like the tour in bug 1779427 somehow breaks the sizing/layout of Firefox View, even when the tour is not active.

Two different sets of STR:
EASY STR:
(1) Open Firefox with a fresh profile, in a build after bug 1779427 landed.
(2) Visit Firefox View (leftmost tab in tab strip)
(3) Click the "x" button on the tour.
Pay close attention to the size of the text...
(4) Refresh with Ctrl+R.

ACTUAL RESULTS:
The text (e.g. "Firefox View" heading at top left) noticeably shrinks in step 4.

EXPECTED RESULTS:
Text should not shrink.


MY ACTUAL STR:
(1) Use an older Nightly to configure Firefox View and log in with Sync.
(2) Update to current Nightly (a build after bug 1779427 landed).
(3) Check Firefox View -- particularly the "last active" tab.

ACTUAL RESULTS:
- The text is a bit larger, and "last active" badge text is too large for the badge, for some reason.
- I never see any tour on Firefox View (maybe because I've already used all of its features?), so I have no way to dismiss the tour and get back smaller text (as I can do in above "EASY STR")
- However, if I manually set about:config pref `browser.firefox-view.feature-tour` to `	{"message":"FIREFOX_VIEW_FEATURE_TOUR","screen":"","complete":true}`, then I get back smaller text and a properly-laid-out "Last Active" badge.
Bug: In a profile with sync configured from before featureTour was enabled, the `browser.firefoxView.featureTour` pref stays at its default value indefinitely
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-09-12 06:50:27+00:00
Resolved: 2022-09-23 10:13:52+00:00

This is related to bug 1790319, but I figured it'd be worth spinning off separately.

In my regular browsing profile (where I have Firefox Sync configured and have other devices syncing as well), I didn't get any particular tour-invitation when running a Nightly with the Firefox View feature-tour enabled.  (I checked on two different machines; no tour on either machine in my regular profile, though I do get a tour in a fresh profile.)

I'm not sure if this lack-of-a-tour-for-existing-sync-users was intentional or not; but it seems to mean that the tour pref is just left at its default value indefinitely (since taking the tour is what changes the pref value).

And this persistent/stuck "tour not yet seen" pref-status impacts the layout of the page (perhaps unintentionally) as described in bug 1790319; and I suspect it might have other side effects as well?

Anyway, just filing this bug to be sure it's something that's known/understood.  If we'd like for existing users with Sync configured to see the Firefox View tour and to get this pref eventually set to its `TRUE`-flavored value, we need to take some sort of action to make that happen, because it's not happening right now.
Bug: Button numeration is incorrectly read by NVDA in Application (Hamburger) Menu
Status: NEW
Priority: P3
Created: 2022-09-12 11:25:56+00:00
Resolved: 2024-03-14 00:34:58+00:00

**Note**
* When the user navigates the "Application Menu" using a screen reader, he will notice that the buttons in the third group have an incorrect enumeration. When navigating the buttons using the TAB or DOWN ARROW, the screen reader will read "Find in page button, 3 of 8, and then it will read "Zoom out button, 5 of 8".

** Found in**
* NIghtly v106.0a1

**Affected versions**
* NIghtly v106.0a1
* Esr91 v91.13.0esr

**Affected platforms**
* Windows 10

**Steps to reproduce**
1. Launch NVDA.
2. Launch Firefox.
3. Navigate to the menu bar and open the "Application Menu" (Hamburger Menu)
4. Using the TAB or DOWN ARROW, scroll through the third group of buttons.

**Expected result**
* Numeration is correct: There are 7 buttons and the readers reads:
"Find in page button, 3 of 7, and then it will read "Zoom out button, 4 of 7".

**Actual result**
* Numeration is incorrect: 
"Find in page button, 3 of 8, and then it will read "Zoom out button, 5 of 8".

**Regression range**
* Not a recent regression.

**Additional notes**
* This is a trivial bug, but it could cause confusion to screen reader users.
* This issue does not occur on Mac (with VoiceOver) or Ubuntu (with ORCA) since they don't read a numeration when navigating the menu.
Bug: Feature call out onboarding container is not showing properly after pinning/unpinning to overflow menu
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2022-09-12 12:58:35+00:00
Resolved: 2022-11-02 21:29:19+00:00

**Found in**
* Firefox Nightly 106.0a1

**Affected versions**
* Nightly 106.0a1

**Tested platforms**
* Affected platforms: Windows 10x64, macOS 10.12.6 and Ubuntu 18.4


**Steps to reproduce**
1. Launch Firefox 
2. Right Click on the Firefox View tab and choose Pin to the Overflow menu option
3. Go to the Overflow menu right click on the Firefox View and select unpin from Overflow menu
4. Open the Firefox View tab
5. Minimize the browser using the toolbar button
6. Click on Firefox browser to bring it back in view
7. Observe the Firefox View feature call out onboarding container


**Expected result**
* Onboarding container is displayed properly in the Firefox View tab pickup.

**Actual result**
* Feature call out onboarding container is not showing properly after pinning and unpinning Firefox View tab while minimizing the browser.

**Note**: It may be necessary to repeat the reproducing steps a couple of times to catch the onboarding defect
**Note**: See the attached screenshot
**Regression range** New Feature
Bug: Update Firefox View Feature Callout so that screenreaders read expected content in the proper order
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-09-12 13:15:48+00:00
Resolved: 2022-11-01 15:00:17+00:00

Per :ayeddi 

- "When the `about:firefoxview` is opened, the screen reader focus jumps to the onboarding callout, which is expected (I assume), but when the screen reader completes reading its content, it proceeds to read the main page content from the middle - from the Colorways section and then to the Recently closed one. This will cause users missing the top of the page, incl. the synced tabs."

- "on MacOS the dialog title is not announced by VoiceOver - the code looks good, so this is likely more general bug?"

See `featureCallout.mjs` for feature callout code.
Bug: In feature callout, screenreaders should announce the stepper before the CTA
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-09-12 13:17:46+00:00
Resolved: 2022-09-12 13:36:09+00:00

Per :ayeddi - "Programmatic reading order of the first callout is not following the visual reading order - the Next button is announced before the stepper which is placed on the left (for English and other LTR, stepper needs to be announced first)"

See `featureCallout.mjs` for feature callout code.
Bug: Make Feature Callout step indicator more accessible
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2022-09-12 13:27:07+00:00
Resolved: 2023-02-15 17:13:14+00:00

Per :ayeddi - 
- "Stepper is marked up as a meter while that widget is not expected to be used in this case. Instead, the progress bar is expected (either preferred HTML <progress> or ARIA-powered role="progressbar")"
- "Stepper announces that it's on the step 0 of 4, while 1 of 4 would be expected to be more human-friendly :) Plus, the aria-valuemin is set to 1"
- "Stepper is announcing that it is a vertical level indicator on macOS - it should be horizontal (which is implied for either progress bar pattern, see above)"
- "The stepper indications are hard to see: without HCM/Increase contrast on dark mode the color contrast for the future steps is only 2.2:1 while minimum per WCAG is 3:1 and higher is better. Users may find it difficult to predict how many steps are left or are passed as the inactive dots are hard to see. With HCM on, the contrast is still low. Maybe, using WindowText for inactive dots and SelectedItemtext for the current step dot be appropriate?"
- "Programmatic reading order of the first callout is not following the visual reading order - the Next button is announced before the stepper which is placed on the left (for English and other LTR, stepper needs to be announced first)"

See `featureCallout.mjs` for feature callout code.
See [MultiStageAboutWelcome.jsx](https://searchfox.org/mozilla-central/source/browser/components/newtab/content-src/aboutwelcome/components/MultiStageAboutWelcome.jsx#246) for progress / step indicator code.
Bug: Ensure Feature Callout messages are accessible in HCM (High Contrast Mode)
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-09-12 13:39:12+00:00
Resolved: 2022-09-30 06:27:10+00:00

per :ayeddi -
- "The dialog does not follow the HCM styling for controls on hover: Close and Next/Got it! should have their colors reversed on hover, but the Close icon disappears on Win and is almost invisible on mac."
- "Next does not follow Windows HCM colors for buttons: expected to use ButtonText and ButtonFace, but the outline is using text color (white on WinOS 11 Night Sky HCM, as an example, while yellow is expected)"

See featureCallout.mjs for feature callout code.
See [here](https://searchfox.org/mozilla-central/source/browser/components/newtab/content-src/aboutwelcome/components/MultiStageProtonScreen.jsx) in AboutWelcome for screen content code.
Bug: Address bar dropdown flickers after enabling/disabling Quick Actions
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-09-12 14:16:13+00:00
Resolved: 2023-12-04 16:52:55+00:00

**Note**
* Small address bar flash right after enabling/disabling Quick Actions, first time interacting with address bar dropdown

**Found in**
* 106.0a1

**Affected versions**
* Nightly 106.0a1 2022-09-12

**Tested platforms**
* Affected platforms: Win 10 64-bit, OSX 10.14, Ubuntu 22.04 64-bit
* Unaffected platforms: -

**Steps to reproduce**
1. Go to about:preferences#privacy - Address Bar section and disable Quick Actions
2. Expand address bar
3. Reenable Quick Actions
4. Expand address bar

**Expected result**
* Quick action items are not visible added/removed when turning the pref on/off

**Actual result**
* Small flicker in the address bar dropdown when enabling/disabling Quick Actions

**Regression range**
* Not a regression
Bug: Close button is not working for the mobile pick up card
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-09-12 14:16:18+00:00
Resolved: 2022-09-14 10:05:18+00:00

**Found in**
* Nightly 106.0a1

**Affected versions**
* Nightly 106.0a1

**Tested platforms**
* Affected platforms: Windows 10x64, Ubuntu 18.4 and macOS 10.12.6


**Steps to reproduce**
1. Launch Firefox
2. Go to Firefox View tab pick up
3. Click Continue button to sign in with FxA account
4. Sign In with account
5. Return to Firefox View and click Close on the mobile pick up card button

**Expected result**
* Mobile pick up message card is closed.

**Actual result**
* Close button is not working for the mobile pick up card

**Regression range**
* First bad: 106.0a1 (2022-09-09)
* Last good: 106.0a1 (2022-09-08)
* Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2b0f7a20d14a3b1c4ea192a85028288c8b3d2df7&tochange=0e3963842e57b86dd0fb9e5f2e8eb8eab02192ed
* Potentially regressed by: Bug 1789226 - Show zap gradient border for tab pickup cards. r=sclements
Bug: Zap gradient border on firefox view setup cards looks wonky on non-integer DPI
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2022-09-12 14:26:13+00:00
Resolved: 2022-09-13 21:32:56+00:00

STR:

1. set Windows display to 150% scaling
2. open firefox view when not set up

ER:
zap border is the same size everywhere

AR:
zap border is 1 device pixel at the top, 2 device pixels on the bottom/left/right.
Bug: [Existing users] The “Make Firefox Home your colorful homepage" option from the “Colorways” modal is not visible when resizing the browser
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-09-12 15:32:57+00:00
Resolved: 2022-09-12 19:01:51+00:00

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

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

**[Prerequisites]:**
- Have the latest version of the Firefox Nightly build installed/extracted and opened.
- Have the “devtools.chrome.enabled” pref set to true.
- Have a custom homepage set on the “about:preferences#home” page.
- Have the “Cc["@mozilla.org/browser/browserglue;1"].getService().wrappedJSObject._showUpgradeDialog();” syntax copied to the Clipboard.

**[Steps to reproduce]:**
1. Focus the Browser Console and paste the syntax from prerequisites.
2. Press the “Enter” key.
3. Click the “Skip this step” button until the “Colorways” modal is focused.
4. Horizontally resize the browser to half of its width.
5. Observe the elements from the modal.

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

**[Actual result]:**
 -  The “Make Firefox Home your colorful homepage" option is not visible and the secondary button is cut off.

**[Notes]:**
- This issue is also reproducible on the “Pin to taskbar” modal, where the "Also pin Firefox private browsing" checkbox is not visible when the browser is resized.
- Attached is a screen recording of the issue.
Bug: ExperimentFakes.enrollWithRollout skips enrollment logic
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2022-09-12 15:43:22+00:00
Resolved: 2024-05-17 07:54:45+00:00

It directly calls [ExperimentStore.addEnrollment](https://searchfox.org/mozilla-central/rev/9ddf68cc9e603276fc4c5253328cb3aeed6f0a55/toolkit/components/nimbus/test/NimbusTestUtils.jsm#216), skipping all logic in `ExperimentManager.enroll()`.
Bug: Open PDF in firefox is downloading the PDF instead of opening in browser when using "always ask me what to do with this file"
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-09-12 22:52:37+00:00
Resolved: 2022-10-14 13:14:08+00:00

Steps to reproduce:

1. Set PDF options to "always ask"
2. Try to open the file with "open with firefox"


Actual results:

This will automatically save the file in the "downloads folder."


Expected results:

"Open with firefox" should open the file in the browser, and not download it.
Bug: Poor contrast in about:plugins with dark theme
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-09-12 23:51:11+00:00
Resolved: 2022-09-14 12:19:59+00:00

(I'm not sure if this is the correct component or not; apologies if it isn't.)

The box at the top of about:plugins that says "Missing something? Some plugins are no longer supported. Learn More." has very poor contrast when Firefox and/or the OS is in dark mode.

STR:
1. Enable dark mode
2. Go to about:plugins

Mozregression points to this being caused by bug 1735800, i.e. enabling the dark theme on about: pages.

(As a side note: apparently the option to take a screenshot doesn't appear in the context menu on about: pages.  Completely unrelated, but interesting.)
Bug: Tabs from other devices menu not showing synced tabs
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-09-13 03:10:08+00:00
Resolved: 2022-11-16 03:10:23+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 click the "Show tabs from other devices" menu button in the top bar of Firefox on desktop. 


Actual results:

The menu appears and just shows the "sync now" and "manage account" buttons. Both these buttons work as expected, though even after syncing, no tabs are shown, from either the current device or any other devices.


Expected results:

This menu is supposed to show tabs from other devices. In some past experiences, this menu will only load synced tabs once the current device is synced, but it will show the tabs open in other sessions with the same sync account signed in.
Bug: Backgrounds on buttons/fields can be close to visible (e.g. with Inverted colours option enabled on Light theme)
Status: NEW
Priority: P3
Created: 2022-09-13 06:55:05+00:00
Resolved: 2023-06-02 15:23:45+00:00

**Found in**
* 106.0a1

**Affected versions**
* 106.0a1
* 105.0

**Affected platforms**
* macOS 11
* Windows 10

**Steps to reproduce**
1. Go to System Preferences => Accessibility (mac) or  Settings => Accessibility => Color Filter (win) and set the Inverted Colours option
2. Have the Light theme  set at the level os and the System theme - auto enabled inside the browser or enable Light theme from about:addons#themes
3. Observe different buttons/fields (eg. about:preferences page, location/ addon popups, colorways/ printing modals etc)

**Expected result**
*  The background of buttons and fields is distinguishable. 

**Actual result**
* The background of buttons and fields is invisible, only the labels show the presence of each element.

**Regression range**
* Last good revision: b85e871f6a8d57cdc744634dadb2b0af88422504 (2021-04-06)
* First bad revision: b740f950e4971e9e17c16b0e19e569cd3b07ceb5 (2021-04-07)
* Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b85e871f6a8d57cdc744634dadb2b0af88422504&tochange=b740f950e4971e9e17c16b0e19e569cd3b07ceb5

**Additional notes**
* The buttons/fields are visible on hover.
Bug: after last update/upgrade THE NIGHTLY foxy proxy , google-translate and some of extension aren't working at all
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2022-09-13 06:58:55+00:00
Resolved: 2022-09-15 14:06:57+00:00

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

Steps to reproduce:

I updated/ upgraded the Nightly browser.


Actual results:

After that, when I tried to use my extensions which includes "google-translate , foxyproxy-standard and bitwarden" didn't works at all.
so I closed Nightly, totally I emphasize totally and I repeated, I suppose three times.
but didn't change.


Expected results:

I don't understand. work well. not any more.
Bug: Multiple "*" characters were added editing, print preview and saving the file multiple time
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-09-13 07:41:40+00:00
Resolved: 2022-10-21 09:36:58+00:00

**Found in**
* Firefox 106.0a1

**Affected versions**
* Firefox 106.0a1

**Tested platforms**
* Affected platforms: Windows 10 x64, macOS 10.15
* Unaffected platforms: Ubuntu 22 x64

**Steps to reproduce**
1. Launch Firefox and verify if pref is set to:  pdfjs.annotationEditorMode = 0
2. Access any *.pdf form.
3. Toggle on Text or Draw button and write or draw a few separate texts on pdf.
4. After typing a text and click somewhere outside of editing text area, then on the pdf tab name is added a '*' character as first character, indicates that any edits were made.
5. Click on print button and from destination select the "Microsoft Print to PDF" option.
6. Save the document.
7. Drag and drop in the Firefox tab bar the saved pdf document, edit again, add a text, will see that a second "*" added to the tab name.
8.  Print preview again, select "Microsoft Print to PDF" for the second time.
9. Save the document.

**Expected result**
* No "*" character were added to the pdf tab name.

**Actual result**
*  "*" characters were added every edited, print and save with "Microsoft Print to PDF"

**Regression range**
* I will come back with regression range ASAP.

**Additional notes**
* The issue is not reproducible on Windows 10 x64 and Ubuntu 22 x64 by selecting "Save to PDF" from print/destination dropdown but reproduced on macOS 10.15 with "Save to PDF" option.
Bug: Cannot switch to presentation mode in using the keyboard because of transient activation
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-09-13 10:16:38+00:00
Resolved: 2022-12-02 20:52:42+00:00

STR:
 - open a pdf
 - hit ctrl+alt+p to switch to presentation mode.

Nothing happen because of transient activation but once something is clicked, then it works as expected.
Bug: The invisible drop marker in the tab list is kept after tab item drag-and-drop
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-09-13 10:32:15+00:00
Resolved: 2022-12-26 22:29:25+00:00

Steps to reproduce:
  1. open 10 tabs
  2. open "List all tabs" menu
  3. move one tab at the end of the list
  4. close 5 tabs
  5. open "List all tabs" menu again

Actual result
the menu is opened with 5 items and extra padding at the bottom, with scroll bar

Expected result
the menu is opened with 5 items. no extra scroll or padding

this is caused by the invisible drop marker, positioned at the bottom of the menu at step 3
Bug: Exclude the Firefox View tab from tab multiselection
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2022-09-13 12:19:35+00:00
Resolved: 2022-09-28 10:00:21+00:00

In https://phabricator.services.mozilla.com/D154099#5052935, @Gijs wrote:
> Seems you can also (yay, all the edgecases!) multiselect tabs including FxView and then open the context menu on another item in the selection and attempt to move both tabs (without even using the all tabs menu)
Bug: [New users] The label of the “Continue in [downloading browser language]" button from the “Choose Your Language” screen is not visible on hover when the High Contrast Mode is enabled
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-09-13 12:28:41+00:00
Resolved: 2022-09-20 02:59:06+00:00

**[Affected versions]:**
- Firefox Nightly 106.0a1 (Build ID: 20220913092817)
- Firefox Beta 105.0 RC (Build ID: 20220912145803)

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

**[Prerequisites]:**
- Have the latest version of the Firefox Nightly build installed/extracted and opened.
- Have the following prefs:
 - "intl.multilingual.downloadEnabled" set to true;
 - "intl.multilingual.enabled" set to true;
 - "intl.multilingual.liveReload" set to true;
 - "intl.multilingual.aboutWelcome.languageMismatchEnabled" set to true;
 - "extensions.getAddons.langpacks.url" set to "https://mock-amo-language-tools.glitch.me/?app=firefox&type=language&appversion=%VERSION%" value;
- Have the High Contrast Mode enabled.

**[Steps to reproduce]:**
1. Restart the browser and navigate to the “about:welcome” page.
2. Click the “Skip this step” button from the first screen.
3. Hover the “Continue in [downloading browser language]" button.
4. Observe the button.

**[Expected result]:**
 - The button label is visible.

**[Actual result]:**
 -  The button label is not visible at all.

**[Notes]:**
- Attached is a screenshot of the issue.
Bug: about:networking page elements are not accessible using the keyboard only
Status: NEW
Priority: --
Created: 2022-09-13 12:32:27+00:00
Resolved: 2023-06-02 15:23:46+00:00

**Found in**
106.0a1

**Affected versions**
Release 104.0.2
Beta 105.0b9
Nightly 106.0a1

**Tested platforms**
Windows 7, Windows 10, macOS 11, Ubuntu 22
**Affected platforms**
Windows 7, Windows 10, macOS 11, Ubuntu 22

**Steps to reproduce**
1.  Go to about:networking and using the keyboard try to reach the left section (HTTP, Sockets, DNS, etc.)

**Expected result**
The user can access the left section items using the keyboard only.

**Actual result**
The left section cannot be reached using the keyboard.

**Regression range**
Not a regression.