av9ash/GitBugs huggingface dataset:
Bug: tab resizing when no sound in video distract me
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2025-01-22 11:24:37+00:00
Resolved: 2025-03-04 16:02:26+00:00

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

Steps to reproduce:

1. open youtube video for example https://www.youtube.com/live/bgoLP5FFSB4?si=ECIZIm0NiRJebCQx&t=2066
2. wait for the period when no sound in video (in example go to 34:30 and wait around 30s)


Actual results:

mute icon disappear. and make tab size smaller. then tab list move a little bit.
and when sound come again it make tab bigger

as you can see in https://youtu.be/v2aCnZrD_Sg 
around 00:22 it pull tab from left side
around 00:29 it push tab to right side


Expected results:

tab size should not move
Bug: Intermittent browser/components/tabbrowser/test/browser/tabs/browser_link_in_tab_title_and_url_prefilled_normal_page_no_target.js | single tracking bug
Status: NEW
Priority: P5
Created: 2025-01-22 11:38:19+00:00
Resolved: 2025-02-17 06:40:27+00:00

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

---
```
TEST-PASS | browser/components/tabbrowser/test/browser/tabs/browser_link_in_tab_title_and_url_prefilled_normal_page_no_target.js | "New Tab" == "example.com/browser/browser/components/tabbrowser/test/browser/tabs/link_in_tab_title_and_url_prefilled.html" - 
[task 2025-01-22T11:20:06.587Z] 11:20:06     INFO - Wait until loading the link target
[task 2025-01-22T11:20:06.588Z] 11:20:06     INFO - Buffered messages logged at 11:19:21
[task 2025-01-22T11:20:06.589Z] 11:20:06     INFO - Console message: [JavaScript Warning: "This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use �<!DOCTYPE html>�." {file: "https://example.com/browser/browser/components/tabbrowser/test/browser/tabs/wait-a-bit.sjs" line: 0}]
[task 2025-01-22T11:20:06.590Z] 11:20:06     INFO - Buffered messages finished
[task 2025-01-22T11:20:06.590Z] 11:20:06     INFO - TEST-UNEXPECTED-FAIL | browser/components/tabbrowser/test/browser/tabs/browser_link_in_tab_title_and_url_prefilled_normal_page_no_target.js | Test timed out - 
[task 2025-01-22T11:20:06.591Z] 11:20:06     INFO - GECKO(8128) | Completed ShutdownLeaks collections in process 6468
[task 2025-01-22T11:20:06.591Z] 11:20:06     INFO - TEST-START | Shutdown
[task 2025-01-22T11:20:06.592Z] 11:20:06     INFO - Browser Chrome Test Summary
[task 2025-01-22T11:20:06.592Z] 11:20:06     INFO - Passed:  650
[task 2025-01-22T11:20:06.593Z] 11:20:06     INFO - Failed:  1
[task 2025-01-22T11:20:06.593Z] 11:20:06     INFO - Todo:    0
[task 2025-01-22T11:20:06.594Z] 11:20:06     INFO - Mode:    e10s
[task 2025-01-22T11:20:06.594Z] 11:20:06     INFO - *** End BrowserChrome Test Results ***
[task 2025-01-22T11:20:06.595Z] 11:20:06     INFO - GECKO(8128) | Exiting due to channel error.
[task 2025-01-22T11:20:06.595Z] 11:20:06     INFO - GECKO(8128) | Exiting due to channel error.
[task 2025-01-22T11:20:06.595Z] 11:20:06     INFO - TEST-INFO | Main app process: exit 0
[task 2025-01-22T11:20:06.596Z] 11:20:06     INFO - TEST-UNEXPECTED-FAIL | browser/components/tabbrowser/test/browser/tabs/browser_link_in_tab_title_and_url_prefilled_normal_page_no_target.js | Application shut down (without crashing) in the middle of a test!
[task 2025-01-22T11:20:06.596Z] 11:20:06     INFO - TEST-INFO took 46589ms
[task 2025-01-22T11:20:06.596Z] 11:20:06     INFO - runtests.py | Application ran for: 0:02:14.044622
```
Bug: Some websites are showing a background that follows Firefox theme instead of the website theme
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2025-01-22 11:46:47+00:00
Resolved: 2025-01-22 13:17:35+00:00

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

Steps to reproduce:

Tried to open a website (in the screenshot example, fastmail.com webpage).

Other info:
Currently there is a custom theme setted: however, even by deleting the folder containing the theme, resetting the default theme, disabling all the extensions and even trying in Provisional Mode doesn't fix the issue.

A new profile seems to not have this issue: I can't, however, find anything related to my about:config or direct settings that could cause this issue.


Actual results:

The background on the page uses the same color as Firefox personal background theme (see picture). This is NOT happening on every website, but only a few ones. For example: fastmail.com (showed in the screenshot), one.google.com (right panel) or mirror.sitsa.com.ar/ubuntu-releases (bottom panel). Many websites are not affected. The black and purple background in the screenshot are related to the dark theme and incognito mode of Firefox.


Expected results:

The website should appear with a white background instead of the color from the current Firefox session.
Bug: Intermittent browser/components/search/test/browser/telemetry/browser_search_telemetry_domain_categorization_ping_submission.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2025-01-22 11:58:02+00:00
Resolved: 2025-02-17 12:05:29+00:00

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

---
```
TEST-PASS | browser/components/search/test/browser/telemetry/browser_search_telemetry_domain_categorization_ping_submission.js | Counter should be incremented when there is an issue creating the store for the domain-to-categories map. - 1 == 1 - 
[task 2025-01-22T11:03:12.496Z] 11:03:12     INFO - Buffered messages logged at 11:03:12
[task 2025-01-22T11:03:12.496Z] 11:03:12     INFO - Leaving test bound test_count_incremented_if_store_is_not_created
[task 2025-01-22T11:03:12.497Z] 11:03:12     INFO - Buffered messages finished
[task 2025-01-22T11:03:12.506Z] 11:03:12     INFO - TEST-UNEXPECTED-FAIL | browser/components/search/test/browser/telemetry/browser_search_telemetry_domain_categorization_ping_submission.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 2025-01-22T11:03:12.511Z] 11:03:12     INFO - GECKO(5928) | MEMORY STAT | vsize 2104271MB | vsizeMaxContiguous 65063633MB | residentFast 311MB | heapAllocated 127MB
[task 2025-01-22T11:03:12.511Z] 11:03:12     INFO - TEST-OK | browser/components/search/test/browser/telemetry/browser_search_telemetry_domain_categorization_ping_submission.js | took 53000ms
[task 2025-01-22T11:03:12.511Z] 11:03:12     INFO - checking window state
[task 2025-01-22T11:03:12.511Z] 11:03:12     INFO - TEST-START | browser/components/search/test/browser/telemetry/browser_search_telemetry_domain_categorization_region.js
```
Bug: Properly localize tab groups' aria-label and aria-description
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2025-01-22 12:57:14+00:00
Resolved: 2025-02-25 21:38:19+00:00

These are currently hardcoded English and should be localized instead: https://searchfox.org/mozilla-central/rev/ef34dd879ef8d4a0f3d68d371d23caebcd8fef65/browser/components/tabbrowser/content/tabgroup.js#185-186
Bug: 4.88 - 4.47% damp browser-toolbox.inspector-ready.DAMP / damp browser-toolbox.inspector-ready.DAMP (OSX, Windows) regression on Thu January 16 2025
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2025-01-22 15:16:00+00:00
Resolved: 2025-01-29 16:29:24+00:00

Perfherder has detected a devtools performance regression from push [34f28da9e8d593cc53458fda8caefc688ea58d56](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=34f28da9e8d593cc53458fda8caefc688ea58d56). 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)** |  
|--|--|--|--|--| 
| [5%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,85768,1,12)  | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) browser-toolbox.inspector-ready.DAMP | windows11-64-shippable-qr | e10s fission stylo webrender | 235.00 -> 246.47 | 
| [4%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,300685,1,12)  | [damp](https://firefox-source-docs.mozilla.org/devtools/tests/performance-tests-overview.html#damp) browser-toolbox.inspector-ready.DAMP | macosx1470-64-shippable | e10s fission stylo webrender | 345.42 -> 360.88 | 


Details of the alert can be found in the [alert summary](https://treeherder.mozilla.org/perfherder/alerts?id=43382), 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 all of these tests on try with `./mach try perf --alert 43382`

The following [documentation link](https://firefox-source-docs.mozilla.org/testing/perfdocs/mach-try-perf.html#running-alert-tests) provides more information about this command.

For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).

If you have any questions, please do not hesitate to reach out to bacasandrei@mozilla.com.
Bug: [Rollout] If Firefox is already pinned to the Windows Start Menu, the “Pin Firefox to Start menu” checkbox is still displayed in the “FOX_DOODLE_MULTI_ACTION” message
Status: RESOLVED
Priority: P1
Resolution: WONTFIX
Created: 2025-01-22 16:07:05+00:00
Resolved: 2025-01-23 20:06:20+00:00

[Affected versions]:
- Firefox Release 134.0.2 MSIX BUILD ID: 20250120135430.

[Affected Platforms]:
- Windows 10.
- Windows 11.

[Prerequisites]:
- User is or was enrolled in the Delivery branch of the “[Long term holdback 2025H1 Growth Desktop](https://experimenter.services.mozilla.com/nimbus/long-term-holdback-2025h1-growth-desktop/summary)” required experiment.
- User was not previously enrolled in the Treatment A branch of the “Fox Doodle Multi-Action CTA - [Early Day](https://experimenter.services.mozilla.com/nimbus/fox-doodle-multi-action-cta-early-day/summary) / [Existing Users](https://experimenter.services.mozilla.com/nimbus/fox-doodle-multi-action-cta-existing-users/summary)” experiments.
- Have a Firefox profile that is older than 7 days and younger than 28 days (for Early Day users) OR have a firefox profile that is older than 28 days (for Existing users).
- Firefox is not set as the default browser.
- Firefox is already pinned to the Windows Start Menu.
- Click the “Don’t show this message again” checkbox from the “Make Firefox your primary browser” prompt.

[Steps to reproduce]:
1. Open the browser with the profile from the prerequisites.
2. Enroll in the “[Fox Doodle Multi-Action CTA 2025 - Rollout](https://experimenter.services.mozilla.com/nimbus/fox-doodle-multi-action-cta-2025-rollout/summary)” by adding this [user.js](https://drive.google.com/file/d/1HuEKS45QPLTqmXR356azT3SWrZtHn86O/view?usp=sharing) file to the profile folder.
3. Restart the browser and observe the behavior after the “FOX_DOODLE_MULTI_ACTION” message is triggered.

[Expected result]:
- The “Pin Firefox to Start menu” checkbox is not displayed since Firefox is already pinned to the Start Menu. Only the “Pin Firefox to taskbar” and “Set Firefox as default browser” checkboxes should be displayed.

[Actual result]:
- The “Pin Firefox to Start menu” checkbox is also displayed, along with “Pin Firefox to taskbar” and “Set Firefox as default browser”.

[Additional Notes]:
- Another scenario when the pin is not recognized is the following: If Firefox is pinned to the Taskbar but not to the Start Menu, the “FOX_DOODLE_SET_DEFAULT” message is triggered instead of the "FOX_DOODLE_MULTI_ACTION” since it doesn’t seem to recognize “Pin Firefox to Start menu” as a possible option to display.
Bug: Curated name for Serbian is incorrect
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2025-01-22 18:35:40+00:00
Resolved: 2025-02-05 15:04:00+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36

Steps to reproduce:

Opened Settings, wanted to add Serbian language to GUI. Language list initially contains only English. Clicked "Set Alternatives", and in the new window clicked "Select a language to add". 


Actual results:

Drop-down list opens, but Serbian language is in the wrong place in the sorted list of languages. I found it as "Cрпски", between Cymraeg and Dansk. First letter seems to be Latin, and the rest are Cyrillic.


Expected results:

The language should be found as "Српски", between Русский and Тоҷикӣ. First letter should be U+0421 Cyrillic Capital Letter Es, that just looks the same, but is different from U+0043 Latin Capital Letter C.
Bug: No close button on sidebar of addon when sidebar.revamp = true
Status: NEW
Priority: P2
Created: 2025-01-22 20:15:24+00:00
Resolved: 2025-01-23 17:49:40+00:00

Steps to reproduce:
1. enable sidebar.revamp
2. install addon such as tree style tab/update scanner
3. open addon's sidebar

Actual results:
No close button on sidebar

Expected resukts:
Close button should be provided just like Bookmarks/History sidebar.
Bug: PrefFlipsFeature initialized in child processes.
Status: NEW
Priority: P3
Created: 2025-01-22 21:18:01+00:00
Resolved: 2025-02-07 14:40:47+00:00

The ExperimentManager is [unconditionally initializing the Pref Flips Feature](https://searchfox.org/mozilla-central/rev/4f5426084651871759f5346eb0ded2e9ac5326fd/toolkit/components/nimbus/lib/ExperimentManager.sys.mjs#106), which should only run in the parent process. This means the feature is also running in the child process, where it cant really do anything and wastes resources.
Bug: Address Bar Spoofing via Suppression of Fullscreen Exit Notifications on Firefox Linux Version 134.0.2
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2025-01-23 09:42:36+00:00
Resolved: 2025-01-29 19:27:56+00:00

## Hi Team,

- During my research on Firefox Linux (Version 134.0.2), I discovered an address bar spoofing vulnerability in Fullscreen mode.
- By triggering multiple file downloads in Fullscreen mode, the "Press esc to exit full screen and see download" notification can be suppressed.
- Instead, only the "Download started, to see it press esc" notification appears.
- This issue can lead to address bar spoofing and user deception, as critical Fullscreen exit prompts are removed, and multiple files (e.g., APKs) are downloaded without visible notifications.

## Browser Version:

- Firefox Version: 134.0.2
- Operating System: Linux

## Proof of concept:

I have uploaded the proof-of-concept videos and exploit file in this report for your review and reproductions.

## Impact:

- Address Bar Spoofing: Users may unknowingly interact with a spoofed website, compromising their trust and security.
- Silent Downloads: Files (potentially malicious) can be downloaded without user awareness.
- Deceptive Experience: Suppressed notifications mislead users and undermine security mechanisms.

## Reproduction steps:

- Open this PoC URL in Firefox Linux:
https://stirring-figolla-0c9c71.netlify.app/index.html
- Enter Fullscreen mode by clicking the "Click Here" button.
- Observe the notification "Press back button or exit Fullscreen mode" appearing initially.
- Trigger multiple interactions (e.g., multiple button clicks to start downloads).
- The exit Fullscreen notification may no longer appear, while files continue downloading.
- Verify that the address bar is spoofed, and the exit prompt is no longer visible.
- Exit Fullscreen mode and check how many files were downloaded without proper notifications.

## Suggested Fix:

- Enforce persistent Fullscreen exit prompts: Ensure that the "Press esc to exit full screen" notification is always visible when Fullscreen mode is active.
- Rate-limit download notifications: Prevent excessive download-triggered notifications in Fullscreen mode.
- Enhance user awareness: Clearly indicate ongoing downloads and provide a consistent mechanism to verify file downloads while in Fullscreen.

## References
- Similar issues: Chromium Bug Report #2952743
Bug: The "Checking Review Quality (0%)" update message is displayed in the Firefox Sidebar Review Checker panel on a non PDP
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2025-01-23 13:05:52+00:00
Resolved: 2025-02-13 13:55:52+00:00

**Found in**
* 136.0a1 (2025-01-23)

**Affected versions**
* 136.0a1 (2025-01-23)

**Preconditions**
Enable the Review Checker:
browser.shopping.experience2023.enabled - true
browser.shopping.experience2023.optedIn - 1
browser.shopping.experience2023.autoOpen.enabled - true
browser.shopping.experience2023.integratedSidebar - true
browser.shopping.experience2023.shoppingSidebar - false

**Affected platforms**
* all

**Steps to reproduce**
1. Reach an outdated product on amazon.com that has the Check Now button.
2. Click the Check now button and switch tabs to a non Product details page.

**Expected result**
* The "Checking Review Quality (0%)" update message should not be displayed in the Sidebar.

**Actual result**
* The "Checking Review Quality (0%)" update message is displayed on a non product details page.

**Regression range**
Not a regression
Bug: Secondary Actions: Restart glean event telemetry ping not found/sent
Status: NEW
Priority: P2
Created: 2025-01-23 13:30:58+00:00
Resolved: 2025-01-27 16:51:16+00:00

**Found in**
* 136.0a1 (2024-01-22)

**Affected versions**
* 136.0a1 (2024-01-22)

**Tested platforms**
* Affected platforms: Windows 11, Mac 13, Ubuntu 24

**Preconditions:**
* Open about:glean and select events type pings.

**Steps to reproduce**
1. Type in address bar **restart**
2. Click on the **restart** secondary action.
3. Check the glean telemetry on [firebase](https://debug-ping-preview.firebaseapp.com).

**Expected result**
There are restart glean telemetry pings on [firebase](https://debug-ping-preview.firebaseapp.com).

**Actual result**
There are no restart glean telemetry pings on [firebase](https://debug-ping-preview.firebaseapp.com).

**Regression range**
* N/A - telemetry implemented recently

**Note**
- The **update** keyword also restarts firefox with the same above actual results: no telemetry pings - see bug 1928635
- Its possible that due to the fact that we are using about:glean manual testing options, the event pings for restart are not sent in due time, but better safe than sorry.
- Same situation for **Update** action with the note that Update action should not be available if no update is available to restart for.
Bug: Pop-up window ´Manage sharing your microphone with the site´ by MS Teams Links
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2025-01-23 14:05:34+00:00
Resolved: 2025-02-17 10:17:18+00:00

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

Steps to reproduce:

We have noticed that opening a Microsoft Teams meetings link in Firefox does not open pop-up window asking the user to allow microphone access.
Reopening the link in new tab without closing the Firefox causes the pop-up window to appear (sometimes it takes more then two tries). If one closes the Firefox and then reopens the link, the permission pop-up window will not be shown.

Is this a known issue?
Can we expect this issue to be resolved in the near future?

We are currently using Firefox version 128.6.0esr (64-bit) and Windows 10 (22H2) on our computers.

https://support.mozilla.org/en-US/questions/1478579


Actual results:

The pop-up window asking the users if they wanted to allow microphone access was not displayed.


Expected results:

The pop-up window asking the users if they want to allow microphone access opens (See attached file)
Bug: login-command-button stories are broken
Status: NEW
Priority: --
Created: 2025-01-23 15:59:32+00:00
Resolved: 2025-01-23 15:59:32+00:00

It looks like the `login-command-button` stories don't render any content ex: https://firefoxux.github.io/firefox-desktop-components/?path=/story/domain-specific-ui-widgets-credential-management-command-button--working-button

Doing a quick search I can see places where the code is imported, but it seems to only get used in the stories. Maybe this component + all related code can be removed?

(Also I swear I remembering filing something like this a couple months ago, but I couldn't find it. Apologies if this is a dupe)
Bug: Can't use arrow keys to move through awesomebar suggestions
Status: NEW
Priority: P3
Created: 2025-01-23 16:07:00+00:00
Resolved: 2025-02-24 20:57:31+00:00

I've noticed this a couple of times and it's pretty annoying. I'm pretty sure it's a regression.

I've attached a screenrecording of me hitting the down arrow key a bunch and it skipping over a bunch of items.
Bug: [Rollout][Desktop] The Fx 102-128 RootCA Infobar has the “Learn more” string incorrectly displayed for Firefox versions 115 or newer with en-* or en fallback locales
Status: RESOLVED
Priority: P1
Resolution: WONTFIX
Created: 2025-01-23 20:36:05+00:00
Resolved: 2025-01-27 21:55:39+00:00

**[Affected versions]:**
- Firefox Release 115.0 - Build ID: 20230629134642
- Firefox ESR 115.0 - Build ID: 20230629151558
- Firefox Release 127.0.2 - Build ID: 20240624183754
- Firefox ESR 115.12.0 - Build ID: 20240603145132

**[Affected Platforms]:**
- Windows 7
- Windows 8
- Windows 10
- Windows 11
- macOS 15.0.1
- Ubuntu 22.04

**[Prerequisites]:**
- Have a Firefox Release 115.0 installed.
- Have any Firefox [locale without translation](https://docs.google.com/document/d/1ayrMfagy2hJ3CIz7tvIcLjiByiB9MwmWJs-QKdM1KGI/edit?usp=sharing) installed (e.g.: kn, et, ro, az, ca-valencia).

**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to the "about:config" page and add the “root-ca” pref, set to the “true” value.
3. Change the system time to any date between the 12th of February and the 17th of March, included.
4. Open a new tab and observe the address bar.

**[Expected result]:**
 - The Infobar is displayed, having the “Why do I need to update?” link on the left side of the “Update now” button.

**[Actual result]:**
 - The Infobar is displayed, having the “Learn more” link on the left side of the “Update now” button.


**[Notes]:**
- This issue is reproducible on all Firefox (Release and ESR) 115 and newer versions.
- This issue is NOT reproducible on Firefox (Release and ESR) versions older than 115.
- This issue is reproducible on all en-* locales and all locales without translations, with en fallback.
- According to the [received documentation](https://docs.google.com/document/d/19gWu8wwcRSOjYhjVEuJ3xh7EbgdTa5qK2FMLyIL84aM/edit?tab=t.0), the “Why do I need to update?” string should be displayed for the [SUMO page](https://support.mozilla.org/en-US/kb/root-certificate-expiration?as=u&utm_source=inproduct) link, not “Learn more”, on all en-* locales and all [locales without translations](https://docs.google.com/document/d/1ayrMfagy2hJ3CIz7tvIcLjiByiB9MwmWJs-QKdM1KGI/edit?usp=sharing), with en fallback.
- Attached a screenshot of the issue.