av9ash/GitBugs huggingface dataset:
Bug: "File Not Download: Potential Security Risk" Pop Up issue
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2024-04-20 17:57:58+00:00
Resolved: 2024-05-10 12:06:46+00:00

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

Steps to reproduce:

Simple: trying to download from a FTP or HTTP site I know is reliable, but the problem is clicking the "File Not Download: Potential Security Risk" prompt does not function as intended...


Actual results:

It should have directed me to what the issue itself is and present the "allow download" option, but didn't. Instead had to open the Download window for it.


Expected results:

It should have directed me to what the issue itself is and present the "allow download" option.
Bug: Domain label spoofing
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-04-20 19:16:39+00:00
Resolved: 2024-04-21 06:29:39+00:00

Steps to reproduce:

Go to the website https://www.xn--80ak6aa92e.com/


Actual results:

I believe this error has already been reported. I don't know the bug number and couldn't find it.
I am still seeing a convincing address bar spoofing in the browser.
Bug: Full browser crash loading chrome://browser/content/browser.xhtml inside a content tab
Status: NEW
Priority: P3
Created: 2024-04-20 21:31:52+00:00
Resolved: 2024-05-09 14:45:34+00:00

Steps to reproduce:

Visit the page chrome://browser/content/browser.xhtml
If the crash did not occur, click on the Account icon


Actual results:

This crash is similar to Bug 1884047. I also observe multiple errors in the console when visiting this address.
The crash occurs at a null address, detailed report attached from Asan.
Bug: top side link on reuters main page not positioned correctly
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2024-04-21 01:37:11+00:00
Resolved: 2024-05-10 14:24:47+00:00

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

Steps to reproduce:

go to reuters.com


Actual results:

top link of links to the right of the main article is not positioned properly. it overlaps with the main article link


Expected results:

links to the right of the main article link should be in a clean column and not overlap with other links
Bug: [Experiment]The "Finish Setup" icon is barely visible using the browser's dark theme
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-04-22 14:05:56+00:00
Resolved: 2024-04-22 17:57:58+00:00

**[Affected versions]:**
- Firefox Release 125.0.1 (Build ID 20240416043247)

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

**[Prerequisites]:**
- Have the latest Firefox Release 125.0.1 installed.
- Have the browser's dark theme enabled.
- Have a browser profile enrolled in the Treatment A or B branches of the [About Welcome post first run onboarding](https://experimenter.services.mozilla.com/nimbus/about-welcome-post-first-run-onboarding/summary) experiment.

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Close the onboarding and open a new tab.
3. Observe the "Finish Setup" button from the toolbar.

**[Expected result]:**
- The button respects the standard dark theme Firefox colors.

**[Actual result]:**
- The button's icon is displayed incorrectly using a dark color.

**[Notes]:**
- On the Treatment B branch, the same icon is displayed using a dark color in the callout message as well.
- Attached a screenshot of the issue:
Bug: [Experiment] The "Learn more about Firefox Suggest" option for Yelp and MDN results is not working on Firefox 125
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-04-22 14:44:48+00:00
Resolved: 2024-04-29 08:52:44+00:00

**[Affected versions]:**
- Firefox Release 125.0.2
- Firefox Release 125.0.1

**[Affected Platforms]:**
- Windows 10
- macOS 13.1
- Ubuntu 22.4

[Prerequisites]:
- Be enrolled in the Yelp experiment.
- Have the browser.search.region set to "US".

**[Steps to reproduce]:**
1. Open the Firefox browser using the profile from prerequisites.
2. In the urlbar type a keyword that triggers a Yelp suggestion (eg: restaurant).
3. Click the "Feedback" button of the Yelp result.
4. Click the "Learn more about Firefox Suggest" option.
5. Observe the behavior.

**[Expected result]:**
- The Firefox Suggest SUMO page is opened in a new tab. 

**[Actual result]:**
- Nothing happens.

**[Regression]**
- The issue is NOT reproducible on Firefox 124 release, considering this using mozregression tools we have found the following pushlog: [Link](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=4199577c0d6419bfad168375b8eb9f8b89df095a&tochange=77104ab988852b524803ce06c1b3d1cc3eabe952).
- Based on the Pushlog link, it seems that Bug 1883378 introduced this behavior. 


**[ Notes]:**
- Due to the changes made starting with Firefox 126, the issue is not reproducible because the "Learn more about Firefox Suggest" option was changed to "Manage Firefox Suggest".
- This issue is also reproducible for MDN suggestions. 
- The issue is NOT reproducible for Pocket, Weather, Navigational, Dynamic Wikipedia 
- Attached is a screen recording of the issue.
Bug: Flickering issue when positioning cursor near bottom line/corners of a tab
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-04-22 15:13:37+00:00
Resolved: 2024-05-03 14:17:58+00:00

**Found in**
* 126.0b3

**Affected versions**
* 127.0a1 (2024-04-22)
* 126.0b3

**Tested platforms**
* Affected platforms: Ubuntu 22.04, Windows 11x64, macOS 13

**Steps to reproduce**
1. Open a few tabs.
2. Hover a random tab and move the cursor on the bottom line or bottom corners of the tab.

**Expected result**
* No flickering is observed.

Actual result
* A flickering behavior is observed when positioning the cursor on the bottom line/corners of the tab.

Regression range
* Will look for one asap if there is one.

**Additional notes**
* Attached a screen recording.
* This issue does not reproduce if the cursor is on the top line or corners.
Bug: 7.69 - 7.11% about_preferences_basic / about_preferences_basic (Linux) regression on Wed April 10 2024
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2024-04-22 15:41:15+00:00
Resolved: 2024-05-01 13:59:13+00:00

Perfherder has detected a talos performance regression from push [ea7ba5f7069f5dfc564e10cfb53446c9e4f71ce0](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=ea7ba5f7069f5dfc564e10cfb53446c9e4f71ce0). As author of one of the patches included in that push, we need your help to address this regression.

### Regressions:

| **Ratio** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)** |  
|--|--|--|--|--| 
| [8%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4767424,1,1)  | [about_preferences_basic](https://firefox-source-docs.mozilla.org/testing/perfdocs/talos.html#about_preferences_basic)  | linux1804-64-shippable-qr | e10s fission stylo webrender | 147.41 -> 158.74 | 
| [7%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,4767424,1,1)  | [about_preferences_basic](https://firefox-source-docs.mozilla.org/testing/perfdocs/talos.html#about_preferences_basic)  | linux1804-64-shippable-qr | e10s fission stylo webrender | 148.10 -> 158.63 | 


Details of the alert can be found in the [alert summary](https://treeherder.mozilla.org/perfherder/alerts?id=42261), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the patch(es) may be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/).

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.

You can run these tests on try with `./mach try perf --alert 42261`

For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
Bug: When clicking with middle mouse button on the "New Tab" button, the previous selection will be pasted and searched for, even though middlemouse.paste is turned off
Status: NEW
Priority: --
Created: 2024-04-22 16:09:35+00:00
Resolved: 2025-02-09 07:36:07+00:00

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

Steps to reproduce:

1. Disabled Middle mouse paste in Gnome Tweaks.
2. Disabled middlemouse.paste in about:config.
3. Middle clicked on the new tab button on the tab bar.


Actual results:

A new tab was opened immediately to the right of the current tab. In the new tab the last highlighted text was input and searched for automatically.


Expected results:

Firefox should have respected at least one of the settings for disabling middle mouse paste, but id did not respect either of them. I think that it's most important to respect the settings in about:config.

I think that being able to open a new tab immediately to the right of the current tab, as opposed to opening a new to the far right, is a useful feature, but it is not possible to use it unless you never highlight text.
Bug: reverse_split property styles are reverted at widths < 800px when no_rdm property is present
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-04-22 16:57:50+00:00
Resolved: 2024-05-02 18:45:46+00:00

When using both the `no_rdm` and `reverse_split` properties in a spotlight screen with split layout, when responsive mode is entered at 800px the spotlight remains in it's full size (as intended), but the layout is un-reversed. This seems to be due to media queries throughout our CSS not appropriately handling the `no-rdm` property appropriately ([example](https://searchfox.org/mozilla-central/rev/8c3ca2f5a74e0ba59c3d9dddf5468a2ffab13467/browser/components/aboutwelcome/content-src/aboutwelcome.scss#827-837)). We should go through the css and add no-rdm negations to each of these media queries.

Alternatively, we could bypass the need for `no-rdm` negations in each of these media queries by leveraging something like a [MediaQueryList change event listener](https://developer.mozilla.org/en-US/docs/Web/API/MediaQueryList/change_event), and applying an attribute or class in the case of the `no_rdm` property being present in content, and ridding the css of media query no-rdm negations.
Bug: Can't close with command-q twice
Status: RESOLVED
Priority: P3
Resolution: DUPLICATE
Created: 2024-04-22 17:01:09+00:00
Resolved: 2024-05-07 09:16:12+00:00

STR
1. Open Firefox
2. Close Firefox with command-q twice

Expected: Firefox quits
Actual: "Close window and quit Firefox?" confirmation dialog comes up repeatedly with each press of command-q.

FWIW I noticed this bug in Release (125.0.2) but can also make it happen in new profiles in Nightly.
Bug: "welcome-text" container is still rendered in the absence of title and subtitle
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2024-04-22 17:05:11+00:00
Resolved: 2024-05-02 05:23:08+00:00

When both a title and subtitle aren't included in a screen's content in the split layout for spotlight, the element that contains them is still rendered, which makes the flex layout behave strangely when there is no title or subtitle.
Bug: Intermittent browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_multistage_experimentAPI.js | single tracking bug
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2024-04-22 21:13:21+00:00
Resolved: 2024-05-06 17:24:02+00:00

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

---
```
[task 2024-04-22T20:20:56.089Z] 20:20:56     INFO - TEST-PASS | browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_multistage_experimentAPI.js | telemetry.event_counts['normandy#expose#nimbus_experiment'] must contain the expected value - 1 == 1 - 
[task 2024-04-22T20:20:56.090Z] 20:20:56     INFO - Leaving test bound test_multistage_aboutwelcome_experimentAPI
[task 2024-04-22T20:20:56.090Z] 20:20:56     INFO - Entering test bound test_multistage_aboutwelcome_backdrop
[task 2024-04-22T20:20:56.090Z] 20:20:56     INFO - Buffered messages finished
[task 2024-04-22T20:20:56.091Z] 20:20:56     INFO - TEST-UNEXPECTED-FAIL | browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_multistage_experimentAPI.js | Uncaught exception in test bound test_multistage_aboutwelcome_backdrop - Should render div.outer-wrapper.onboardingContainer[style*='blue'] in multistage step 1 - timed out after 50 tries.
[task 2024-04-22T20:20:56.091Z] 20:20:56     INFO - Leaving test bound test_multistage_aboutwelcome_backdrop
[task 2024-04-22T20:20:56.092Z] 20:20:56     INFO - Entering test bound test_multistage_aboutwelcome_utm_term
[task 2024-04-22T20:21:12.380Z] 20:21:12     INFO - Not taking screenshot here: see the one that was previously logged
[task 2024-04-22T20:21:12.381Z] 20:21:12     INFO - TEST-UNEXPECTED-FAIL | browser/components/aboutwelcome/tests/browser/browser_aboutwelcome_multistage_experimentAPI.js | Test timed out - 
[task 2024-04-22T20:21:12.382Z] 20:21:12     INFO - GECKO(3040) | Completed ShutdownLeaks collections in process 3688
[task 2024-04-22T20:21:12.382Z] 20:21:12     INFO - TEST-START | Shutdown
[task 2024-04-22T20:21:12.383Z] 20:21:12     INFO - Browser Chrome Test Summary
[task 2024-04-22T20:21:12.384Z] 20:21:12     INFO - Passed:  217
[task 2024-04-22T20:21:12.384Z] 20:21:12     INFO - Failed:  2
[task 2024-04-22T20:21:12.385Z] 20:21:12     INFO - Todo:    0
[task 2024-04-22T20:21:12.385Z] 20:21:12     INFO - Mode:    e10s
[task 2024-04-22T20:21:12.386Z] 20:21:12     INFO - *** End BrowserChrome Test Results ***
[task 2024-04-22T20:21:12.560Z] 20:21:12     INFO - GECKO(3040) | 1713817272560	Marionette	TRACE	Received observer notification quit-application
[task 2024-04-22T20:21:12.562Z] 20:21:12     INFO - GECKO(3040) | 1713817272561	Marionette	INFO	Stopped listening on port 2828
[task 2024-04-22T20:21:12.568Z] 20:21:12     INFO - GECKO(3040) | 1713817272567	Marionette	DEBUG	Marionette stopped listening
[task 2024-04-22T20:21:16.836Z] 20:21:16     INFO - TEST-INFO | Main app process: exit 0
```
Bug: Color of symbols on navigation bar in dark theme is black on almost black
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2024-04-22 21:17:35+00:00
Resolved: 2024-04-22 21:21:24+00:00

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

Steps to reproduce:

Change theme from light to dark


Actual results:

The background turns to almost black, the symbols remain black.


Expected results:

Symbols should turn light
Bug: Cannot sync in Firefox after password-change due to stale client state
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2024-04-23 09:33:44+00:00
Resolved: 2024-05-28 19:23:20+00:00

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

Steps to reproduce:

- I've changed my password
- Had to sign-in again
- Cannot sign-in


Actual results:

There isn't really an error message. It just tells me that my account is disconnected and i need to sign-in again (even if i just signed in...)


Expected results:

Signed in with firefox-account and sync working.
Bug: Closing FF from taskbar gets stuck when "Confirm before closing multiple tabs" is on
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2024-04-23 12:32:11+00:00
Resolved: 2024-12-02 12:33:05+00:00

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

Steps to reproduce:

1. Open FF and open multiple tabs.
2. Run another software in order to make FF run in the background.
3.Close FF from taskbar and press the "close tabs" button in the popup.
4.FF is stuck.....


Actual results:

Firefox is stuck.


Expected results:

FF should close properly.
Bug: Domain highlighting doesn't work when detaching tabs
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2024-04-23 12:39:47+00:00
Resolved: 2024-08-22 10:04:32+00:00

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

Steps to reproduce:

1. Set `browser.uidensity` to 2 and `browser.urlbar.trimHttps` to true.
2. Load https page and add another tab.
3. Right-click on the tab for https page -> Move Tab -> Move to New Window.



Actual results:

* The address is displayed without domain highlighiting.



Expected results:

* Domain highlighiting should be applyed.

Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=dc4bd6ad3d6e01478991aa819de02bf9dcce3099&tochange=bae88db81951e0561249da8a92815ef5d459c933
Bug: Remove "toolkit/branding/accounts.ftl" from revamped sidebar html.
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-04-23 14:45:46+00:00
Resolved: 2024-04-29 21:07:16+00:00

"toolkit/branding/accounts.ftl" in `sidebar.html` references a file that no longer exists.
Bug: Restored SERPs do not record SERP telemetry
Status: NEW
Priority: P3
Created: 2024-04-23 15:25:22+00:00
Resolved: 2024-06-25 16:38:02+00:00

**Found in**
* 126.0b4

**Affected versions**
* 127.0a1 (2024-04-22) 
* 126.0b4
* 125.0.2
    

**Tested platforms**
* Affected platforms: Ubuntu 23.04, Windows 10, Mac 11.*

**Preconditions**
* SERP categorization enabled (*browser.search.serpEventTelemetryCategorization.enabled*)
* SERP telemetry v1 enabled (either by having rollout enabled or manually enabling by running snippet in browser console: *Services.fog.setMetricsFeatureConfig(    JSON.stringify({       "urlbar.abandonment": true,       "urlbar.engagement": true,       "urlbar.impression": true,     })   );*)
* *browser.search.log* true

**Steps to reproduce**
1. Perform some searches.
2. Close the SERPs (for categorization event), followed by restoring the SERPS tabs.
3. SERPs are open (for v1) or reopened by restore after categorization is being recorded.
4. Enable session restore.
5. Restart browser.
6. Click on any links inside any SERP.
7. Close any SERP

**Expected result**
* SERP telemetry v1 / SERP categorization is recorded

**Actual result**
* SERP telemetry is not recorded for restored tabs - TypeError: item is undefined

**Regression range**
* N/A

**Additional notes**
* This affects both SERP categorization and SERP telemetry v1 - steps are catching both.
Bug: Link context menu includes options for unrelated text selection
Status: NEW
Priority: --
Created: 2024-04-23 16:47:25+00:00
Resolved: 2024-05-14 08:31:18+00:00

Steps to reproduce:

* Open https://example.com/
* Select the word "Example"
* Right-click on `More information...`


Actual results:

The context menu confusingly shows options for both the link and the separate selected text.


Expected results:

Right-clicking on a link should either:

* Cancel the text selection or
* Show only items related to the link itself
Bug: address bar suggest window covers address bar
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2024-04-23 17:09:36+00:00
Resolved: 2024-05-30 22:45:10+00:00

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

Steps to reproduce:

typing in address bar brings up suggestions based on browsing history (only option checked)


Actual results:

A window opens that covers the address bar starting as soon as the first letter typed. It is impossible to see the address bar unless user hits escape after each letter.


Expected results:

The suggest window should (and I believe always has) display results *below* the address bar, updating as the  user types, but with all letters typed visible to the user
Bug: Tab preview is stale
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-04-23 17:11:54+00:00
Resolved: 2024-04-24 18:29:46+00:00

Mousing over my Gmail tab, the hover shows "No new mail!" but when I navigate there, I have 3 messages in my inbox. How frequently do we regenerate the previews?

I'm on the 2024-04-22 Nightly on macOS
Bug: Intermittent toolkit/components/shopping/test/browser/browser_shopping_request_telemetry.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2024-04-23 18:48:22+00:00
Resolved: 2024-05-22 12:00:42+00:00

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

---
```
[task 2024-04-23T18:42:22.494Z] 18:42:22     INFO - TEST-PASS | toolkit/components/shopping/test/browser/browser_shopping_request_telemetry.js | {"category":"shopping_product","name":"invalid_ohttp_config"} deepEqual {"category":"shopping_product","name":"invalid_ohttp_config"} - 
[task 2024-04-23T18:42:22.494Z] 18:42:22     INFO - Leaving test bound test_shopping_ohttp_invalid_telemetry
[task 2024-04-23T18:42:22.494Z] 18:42:22     INFO - Buffered messages finished
[task 2024-04-23T18:42:22.495Z] 18:42:22     INFO - TEST-UNEXPECTED-FAIL | toolkit/components/shopping/test/browser/browser_shopping_request_telemetry.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-23T18:42:22.496Z] 18:42:22     INFO - GECKO(7776) | MEMORY STAT | vsize 2104443MB | vsizeMaxContiguous 66556633MB | residentFast 340MB | heapAllocated 117MB
[task 2024-04-23T18:42:22.496Z] 18:42:22     INFO - TEST-OK | toolkit/components/shopping/test/browser/browser_shopping_request_telemetry.js | took 47145ms
```
Bug: A button with a cog icon is labeled as "Personalize new tab" while it's usually "Settings"
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2024-04-23 20:27:35+00:00
Resolved: 2024-11-18 12:45:08+00:00

The button with a cog icon is labeled as `Personalize new tab` that is not a common name for the control with such icon. It's expected to be `Settings` or at least to include this word.

[Consistency in the naming](https://www.w3.org/WAI/WCAG22/Understanding/consistent-identification.html) helps users with cognitive difficulties and serves all users with easing their mental load while trying to navigate the content. [Including the visual label in name of the control](https://www.w3.org/WAI/WCAG22/Understanding/label-in-name.html) is required for users of assistive technology to receive sighted help or to be able to guess the functionality of the control by its appearance, and [to provide an appropriate text alternative to the image](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html). Examples of functional images could be found on [the W3C WAI Tutorial page](https://www.w3.org/WAI/tutorials/images/functional/)
Bug: Select and checkbox controls on the about:newtab page's settings dialog have subtle focus indication
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-04-23 20:35:44+00:00
Resolved: 2024-12-05 07:48:52+00:00

The focus indication is very subtle for the checkboxes and combobox with the row numbers for `Shortcuts` on the Settings dialog of the `about:newtab` page. 

Being able to easily discern where the keyboard focus is located and follow it while navigating the page is crucial for the keyboard-only users, especially those with limited vision or with a glare on their screens. It is also important for users with cognitive difficulties and users with color deficiency to be able to tell apart a focused and not focused control to avoid activating wrong element.

It is recommended that the focus outline to follow the default browser behavior or to provide at [least 2px thick perimeter around the control](https://www.w3.org/WAI/WCAG22/Understanding/focus-appearance.html) and to ensure this outline provides [at least 3:1 in color contrast](https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html) between both the page background and the non-focused control appearance.