av9ash/GitBugs huggingface dataset:
Bug: The “Colorway Reminder” CFR message is triggered before the “Firefox View” CFR message on the Treatment E branch
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-12-06 16:38:48+00:00
Resolved: 2022-12-09 15:19:43+00:00

**[Affected versions]:**
- Firefox Release 108.0 - Build ID: 20221205155917

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

**[Prerequisites]:**
- Have a new Firefox profile with the "nimbus.debug" and “browser.ping-centre.log” prefs set to "true" in the "about:config" page.
- Have the browser console opened (Ctrl/Cmd + Shift +J).

**[Steps to reproduce]:**
1. Open the browser with the profile from the prerequisites.
2. Navigate to "about:studies?optin_slug=colorways-expiring-fx108&optin_branch=treatment-e&optin_collection=nimbus-preview" link.
4. Change the system date to 2 days in the future.
5. Open and close 3 tabs to trigger the “Firefox View” CFR message.
6. Focus the browser console (Ctrl/Cmd + Shift +J) and observe the displayed pings related to the “Firefox View” CFR message.

**[Expected result]:**
 - A telemetry ping related to “"CFR_FIREFOX_VIEW"” CFR message is displayed in the browser console.

**[Actual result]:**
- A telemetry ping for the “colorways-reminder-eco-2211-treatment-e ” is displayed in the browser console instead.

**[Notes]:**
- Changing the system date by one day in the future, opening and closing a tab will trigger the “"CFR_FIREFOX_VIEW"” CFR message also.
- Attaching a screen recording of the issue [here](https://drive.google.com/file/d/1zzdHuqxzlwJALO-03Th4A81J-Vf882wC/view?usp=sharing).
Bug: Some collections display errors after changing the environment to Stage
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-12-06 16:41:27+00:00
Resolved: 2023-01-27 14:39:04+00:00

**[Affected Versions]:**
- Firefox Nightly 109.0a1 (Build ID: 20221206034609)
- Firefox Beta 108.0 (Build ID: 20221205155917)
- Firefox Release 107.0 (Build ID: 20221110173214)

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

**[Prerequisites]:**
- Have this [user.js](https://drive.google.com/file/d/1VLdfJOnWwtbRVBDdskLM68_WE6_3YwQd/view?usp=share_link) (or [this](https://drive.google.com/file/d/17LonpPBHfw4df3SRltYg2X2huU0THvnY/view?usp=share_link)) saved to your machine.
- Have Firefox open on the “about:support” page.
- Have the Browser Console open.

**[Steps to reproduce]:**
1. Open the profile folder from “about:support”.
2. Copy the user.js file from prerequisites to the profile folder.
3. Restart Firefox.
4. Observe the Browser Console.

**[Expected result]:**
- The “Enabling Shield” message is displayed, after which the experiments active on Stage are displayed.

**[Actual result]:**
- The “Enabling Shield” message is displayed, after which the following errors are displayed:
`services.settings: main/normandy-recipes-capabilities Signature failed  InvalidSignatureError: Invalid content signature (main/normandy-recipes-capabilities) using 'remote-settings.content-signature.mozilla.org-2023-01-11-02-14-45.chain'
`
`services.settings: main/normandy-recipes-capabilities local data was corrupted`
`services.settings: main/normandy-recipes-capabilities Signature verified failed. Retry from scratch`

**[Notes]:**
- After a while, the experiments are displayed in the Browser Console.
- The “about:studies” page remains blank until the experiments are displayed in the Browser Console.
- After the experiments are loaded, other collections display similar errors (e.g. "main/doh-providers").
- Attached is a recording of the issue.
Bug: auto update causes user to lose work
Status: RESOLVED
Priority: P3
Resolution: WORKSFORME
Created: 2022-12-06 18:20:09+00:00
Resolved: 2022-12-09 14:57:14+00:00

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

Steps to reproduce:

I'm running Ubuntu 22.04.1 and have turned off snap since it caused issues with regard to file access.  I installed Firefox locally using your binary.  When I'm working, let's say filling out a long form medical record, I can get 20-30 minutes into the work, I expect to be able to complete my session.


Actual results:

Just as I'm completing my daily tracking form, Firefox sometimes decides that it's time to restart.  For some reason this prevents me from saving my work on the remote server, and opening a new tab shows the "Sorry. We just need to do one small thing to keep going."  At this point, I'm stuck.  I cannot save my work, and, once I restart Firefox, all of my work is lost.  To add insult to injury, the site that I'm on has a Javascript modal pop-up that prevents me from using system clipboard to save large text blocks.  This is a data-loss problem, even if you're being nice about telling me.  I have to re-enter large chunks of work when this happens.


Expected results:

I should be able to continue working, saving my work, and then, once I'm done, choose to restart Firefox.  I find the various posts to turn off auto-updates altogether via policies.json "ManualAppUpdateOnly" to be far less than ideal, since I do want auto-updates.  I just don't want to lose my work when an update happens.
Bug: Non-native context menus don't appear bigger when activated via touchmode
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-12-06 21:23:14+00:00
Resolved: 2022-12-21 19:36:08+00:00

This broke because in bug 1798324 the selector that was meant to target menuitems specifically was removed, and the var was instead moved to the menupopup.
This is not an issue for panel items because they have their use of the var elsewhere.
Bug: Clicking the block or result menu button with a valid page proxy state makes the page proxy state invalid
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2022-12-07 00:08:27+00:00
Resolved: 2023-02-22 08:25:15+00:00

STR

1. Enable `browser.urlbar.resultMenu`, or add block buttons to top sites results, or add a provider for empty search strings whose results include block buttons
2. Open http://example.com/ in a new tab (any URL will do)
3. Click in the urlbar to show the top sites view
4. Click a result menu button or block button

On mouseup, the page proxy state becomes invalid and whatever is in the input becomes the search string, so if you click in the urlbar again, you get a search for that search string instead of the top sites.

This happens because on mouseup the view [calls `#selectElement(null)`](https://searchfox.org/mozilla-central/rev/ef0aa879e94534ffd067a3748d034540a9fc10b0/browser/components/urlbar/UrlbarView.sys.mjs#2708), which updates the input.

Adding `{ updateInput: false }` to the call fixes the problem for the result menu button, but for the block button, it reveals another problem where the input value is set to the URL of the next row but no row is visually selected. That happens because of two things: (1) the input value is set due to `onQueryResultRemoved()` setting the selected row index to the index of the row after the removed row -- so far so good -- but then (2) the `#selectElement(null)` inside `on_mouseup()` is reached and the selecton is cleared.

This is a problem for the weather suggestion since it will have a block button and it's shown in the top sites view. All this logic is surprisingly complex and kind of brittle and I think it would be simplest to just not select buttons when they're clicked.
Bug: Tab pickup shows no tabs if only desktop devices are connected to the account until restarting
Status: RESOLVED
Priority: P2
Resolution: FIXED
Created: 2022-12-07 02:27:24+00:00
Resolved: 2023-01-10 01:20:07+00:00

STR:
* Sign in to an account that has other desktop devices connected but no mobile devices.

Expected:
* While a CTA to connect a mobile device is expected, it should also be possible to see the tabs from the connected desktop devices.

Actual:
* No tabs are shown, even though the hamburger menu shows them. See screenshot showing both Firefox View (no tabs listed) and the hamburger menu (tabs from the connected desktop device listed)
Bug: firefox 版本107 在 win7 系統,無法正常看8891.com的資料
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-12-07 03:44:17+00:00
Resolved: 2023-01-02 04:45:25+00:00

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

Steps to reproduce:

firefox 版本107 在 win7 64bit 系統,無法正常看8891.com的資料 https://auto.8891.com.tw/usedauto-infos-3299042.html


Actual results:

網頁顯示不正常,但在win10系統應該是沒問題的


Expected results:

請用google chrome對照
Bug: about:sync wants each payload to have the ID field
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2022-12-07 06:27:01+00:00
Resolved: 2024-02-02 22:17:41+00:00

In bug 1804174 I think I was too aggressive - it broke about:sync and I fear other subtle things might be broken. So this patch ensures that if the payload from the server doesn't have the ID in the payload, it is added to the record seen by our JS code.
Bug: Intermittent browser/components/urlbar/tests/browser/browser_glean_telemetry_impression_groups.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INVALID
Created: 2022-12-07 08:41:40+00:00
Resolved: 2023-01-30 06:13:44+00:00

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

---
```
[task 2022-12-07T08:25:53.861Z] 08:25:53     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_glean_telemetry_impression_groups.js | n_results is correct - "2" == 2 - 
[task 2022-12-07T08:25:53.864Z] 08:25:53     INFO - Leaving test bound group_suggested_index
[task 2022-12-07T08:25:53.864Z] 08:25:53     INFO - Buffered messages finished
[task 2022-12-07T08:25:53.865Z] 08:25:53     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_glean_telemetry_impression_groups.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 2022-12-07T08:25:53.865Z] 08:25:53     INFO - GECKO(5220) | MEMORY STAT | vsize 919MB | vsizeMaxContiguous 1806MB | residentFast 228MB | heapAllocated 100MB
[task 2022-12-07T08:25:53.866Z] 08:25:53     INFO - TEST-OK | browser/components/urlbar/tests/browser/browser_glean_telemetry_impression_groups.js | took 49601ms
[task 2022-12-07T08:25:53.866Z] 08:25:53     INFO - checking window state
[task 2022-12-07T08:25:53.867Z] 08:25:53     INFO - GECKO(5220) | Completed ShutdownLeaks collections in process 2948
[task 2022-12-07T08:25:53.867Z] 08:25:53     INFO - TEST-START | Shutdown
[task 2022-12-07T08:25:53.868Z] 08:25:53     INFO - Browser Chrome Test Summary
[task 2022-12-07T08:25:53.868Z] 08:25:53     INFO - Passed:  801
[task 2022-12-07T08:25:53.869Z] 08:25:53     INFO - Failed:  1
[task 2022-12-07T08:25:53.869Z] 08:25:53     INFO - Todo:    0
[task 2022-12-07T08:25:53.870Z] 08:25:53     INFO - Mode:    e10s
[task 2022-12-07T08:25:53.870Z] 08:25:53     INFO - *** End BrowserChrome Test Results ***
```
Bug: Cannot print/save an edited pdf with a "large" number of pages
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-12-07 09:53:28+00:00
Resolved: 2023-01-11 13:47:34+00:00

Attach (recommended) or Link to PDF file here:
https://raw.githubusercontent.com/mozilla/pdf.js/master/test/pdfs/tracemonkey.pdf#page=1&zoom=page-fit,-510,792

Steps to reproduce the problem:
1. Add a text on the first page
2. Scroll the pdf to go to the last page
3. Click on the print button

The print preview shows an empty document.

This bug mirrors https://github.com/mozilla/pdf.js/issues/15780
Bug: Downloads panel animations should honour prefers-reduced-motion settings
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2022-12-07 10:32:09+00:00
Resolved: 2023-06-02 15:24:00+00:00

+++ This bug was initially created as a clone of Bug #1714402 +++

Steps to reproduce:

In Windows 10 Settings, in Display, set "Show animations in Windows" to Off.
Or on macOS, in the Accessibility system preferences, under "Display" tick the "Reduce motion" checkbox.

Alternatively, in Firefox about:config, set "ui.prefersReducedMotion" to integer 1. Restart Firefox.

Download a file (a larger file makes it easier to see the issues). 

Actual results:

The download indicator/menu button will animate (grow/shrink, progressively "sketch" the circle and checkmark, etc)

Expected results:

Download indicator should simply change to a static "complete" shape/colour when a download is complete, with no animations.
Bug: Tabstrip switch-to-tab / scroll-into-view on an overflown tabstrip should not animate if the user has indicated they prefer reduced motion
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2022-12-07 10:39:49+00:00
Resolved: 2024-03-05 08:20:59+00:00

Steps to reproduce:

In Windows 10 Settings, in Display, set "Show animations in Windows" to Off.
Or on macOS, in the Accessibility system preferences, under "Display" tick the "Reduce motion" checkbox.

Alternatively, in Firefox about:config, set "ui.prefersReducedMotion" to integer 1. Restart Firefox.

Open a new tab when the tab bar is already full of open tabs and some tab early (leftward) in the list is selected. 

Actual results:
The whole tab bar will glide rapidly to the new tab on the far right side.

Expected results:

The tab bar should jump instantaneously to the new tab instead of gliding.


---

It looks like the code responsible might be [this bit of the arrowscrollbox code](https://searchfox.org/mozilla-central/rev/70bc66e002ad1cdb1fe5d77428803432f261038a/toolkit/content/widgets/arrowscrollbox.js#311-314). Although we can work around this by checking for the prefers-reduced-motion media query from JS using `matchMedia` and altering the arguments we pass to `scrollIntoView`, I wonder if the DOM/layout code should be automatically not applying animated scrolling if that setting is enabled. That'd be something to take up with the DOM team - we may want to just apply a workaround in the meantime but we should still chase it as that'd improve website a11y.
Bug: When switching to a previous site in a singular tab it doesn't switch
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2022-12-07 13:01:54+00:00
Resolved: 2024-11-04 12:30:15+00:00

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

Steps to reproduce:

1. Open some sites in 1 tab
2. Try to switch to a previous one


Actual results:

I opened Youtube and watched some video then I wanted to go back to the homepage of Youtube so I clicked the left arrow button but it didn't go back and I had to click on a bookmark.


Expected results:

When switching to a previous site in a singular tab, it should switch to that site.
Bug: Intermittent browser/components/screenshots/tests/browser/browser_screenshots_drag_scroll_test.js | single tracking bug
Status: REOPENED
Priority: P5
Created: 2022-12-07 13:32:20+00:00
Resolved: 2025-02-24 07:22:39+00:00

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

---
```
[task 2022-12-07T12:53:43.707Z] 12:53:43     INFO - TEST-PASS | browser/components/screenshots/tests/browser/browser_screenshots_drag_scroll_test.js | The overlay spans the entire height of the page - 
[task 2022-12-07T12:53:43.708Z] 12:53:43     INFO - Leaving test bound test_scrollingScreenshotsOpen
[task 2022-12-07T12:53:43.709Z] 12:53:43     INFO - Buffered messages finished
[task 2022-12-07T12:53:43.709Z] 12:53:43     INFO - TEST-UNEXPECTED-FAIL | browser/components/screenshots/tests/browser/browser_screenshots_drag_scroll_test.js | waiting for vsync to be disabled - timed out after 50 tries. - false == true - JS frame :: chrome://mochikit/content/browser-test.js :: ensureVsyncDisabled :: line 587
[task 2022-12-07T12:53:43.709Z] 12:53:43     INFO - Stack trace:
[task 2022-12-07T12:53:43.711Z] 12:53:43     INFO - chrome://mochikit/content/browser-test.js:ensureVsyncDisabled:587
[task 2022-12-07T12:53:43.711Z] 12:53:43     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-12-07T12:53:43.712Z] 12:53:43     INFO - TEST-UNEXPECTED-FAIL | browser/components/screenshots/tests/browser/browser_screenshots_drag_scroll_test.js | vsync remained enabled at the end of the test. Is there an animation still running? Consider talking to the performance team for tips to solve this. - false == true - JS frame :: chrome://mochikit/content/browser-test.js :: ensureVsyncDisabled :: line 588
[task 2022-12-07T12:53:43.712Z] 12:53:43     INFO - Stack trace:
[task 2022-12-07T12:53:43.712Z] 12:53:43     INFO - chrome://mochikit/content/browser-test.js:ensureVsyncDisabled:588
[task 2022-12-07T12:53:43.712Z] 12:53:43     INFO - GECKO(1740) | MEMORY STAT | vsize 2112358MB | vsizeMaxContiguous 68274376MB | residentFast 262MB | heapAllocated 125MB
[task 2022-12-07T12:53:43.712Z] 12:53:43     INFO - TEST-OK | browser/components/screenshots/tests/browser/browser_screenshots_drag_scroll_test.js | took 7287ms
[task 2022-12-07T12:53:43.713Z] 12:53:43     INFO - checking window state
[task 2022-12-07T12:53:43.713Z] 12:53:43     INFO - TEST-START | browser/components/screenshots/tests/browser/browser_screenshots_drag_test.js
```
Bug: Intermittent browser/components/urlbar/tests/browser/browser_queryContextCache.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2022-12-07 15:24:19+00:00
Resolved: 2023-10-16 12:00:55+00:00

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

---
```
[task 2022-12-07T14:19:26.257Z] 14:19:26     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_queryContextCache.js | View should contain the expected URLs - ["https://4.example.com/example","https://3.example.com/example","https://2.example.com/example","https://1.example.com/example","https://0.example.com/example"] deepEqual ["https://4.example.com/example","https://3.example.com/example","https://2.example.com/example","https://1.example.com/example","https://0.example.com/example"] - 
[task 2022-12-07T14:19:26.261Z] 14:19:26     INFO - Leaving test bound evict
[task 2022-12-07T14:19:26.266Z] 14:19:26     INFO - Buffered messages finished
[task 2022-12-07T14:19:26.269Z] 14:19:26     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_queryContextCache.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 2022-12-07T14:19:26.273Z] 14:19:26     INFO - GECKO(8997) | MEMORY STAT | vsize 12245MB | residentFast 670MB | heapAllocated 367MB
[task 2022-12-07T14:19:26.276Z] 14:19:26     INFO - TEST-OK | browser/components/urlbar/tests/browser/browser_queryContextCache.js | took 48120ms
[task 2022-12-07T14:19:26.279Z] 14:19:26     INFO - checking window state
[task 2022-12-07T14:19:26.283Z] 14:19:26     INFO - TEST-START | browser/components/urlbar/tests/browser/browser_quickactions.js
```
Bug: sporadically I cannot type anything into any of my search bars or into any web page I have open, and need to close then reopen Firefox to fix every time
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2022-12-07 15:52:14+00:00
Resolved: 2023-01-03 11:18:15+00:00

+++ This bug was initially created as a clone of Bug #546663 +++

User-Agent:       Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:107.0) Gecko/20100101 Firefox/107.0
Build Identifier: browser.startup.homepage_override.buildID 20221128185858

I have had this problem several times and I can't tell what causes it because it seems to happen at random.  I have always been able to fix it by restarting firefox.  However today I updated and restarted firefox and I still had the problem when firefox restarted.  

Reproducible: Seemingly at random times
Bug: PDF.js annotation message appears in Firefox View
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2022-12-07 17:16:38+00:00
Resolved: 2022-12-20 12:44:13+00:00

When the `browser.pdfjs.feature-tour` has a `screen` value equal to one of the screen ids in a [PDF.js message](https://searchfox.org/mozilla-central/source/browser/components/newtab/lib/FeatureCalloutMessages.jsm#395), the callout unexpectedly shows in Firefox View instead of that feature's tour.

To resolve this issue, we can add additional targeting to the PDF.js messages that restrict them to showing only when the source ends in `.pdf`.
Bug: Convert toolkit SessionStoreFunctions.jsm to sys.mjs ESM module
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-12-07 18:33:19+00:00
Resolved: 2022-12-08 15:36:31+00:00

+++ This bug was initially created as a clone of Bug #1803158 +++

In that bug I left the toolkit one alone. Oddly, it only has C++ consumers.
Bug: Save to Pocket and Pocket newtab pass rollout metadata to Pocket links
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-12-07 20:45:58+00:00
Resolved: 2022-12-09 03:35:59+00:00

If we want to ensure a rollout is doing no harm as we increase the percentage, we need to be able to look at a few metrics, and one of them being signups.

In order to do that, it might be helpful in some cases to know what signups were in the rollout and what were not.

We already do this for experiments, so we just need to add rollouts to that too, prioritising experiments over rollouts if a user is in both.
Bug: Re-vendor application-services to pickup fix to IDs in sync payload
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2022-12-07 21:58:16+00:00
Resolved: 2022-12-08 09:44:28+00:00

https://github.com/mozilla/application-services/pull/5278 fixes a regression I introduced in application services - we'd like to take that in m-c.
Bug: Interaction type `refined` should not across sessions
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2022-12-07 23:27:37+00:00
Resolved: 2023-07-10 06:22:41+00:00

Now, even if one session finished, if the current keywords are refined comparing with the previous keywords, we record the interaction type as `refined`.
But, as the `refined` should be handled as a subset of `retuned`, not cross the sessions.
Bug: (Firefox MacOS) Cannot focus on <a /> anchor element using tab key
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2022-12-07 23:55:36+00:00
Resolved: 2023-11-28 21:29:02+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:

Create a simple web page including the following:

```
<a href="https://google.com" role="button" tabindex="0">This should be focusable</a>
```

This element should be focusable using the tab key, however it isn't.



Actual results:

The <a /> element is not focused, even with `role="button"` and `tabindex="0"`


Expected results:

The element should be focused with the tab key