av9ash/GitBugs huggingface dataset:
Bug: Intermittent browser/tools/mozscreenshots/permissionPrompts/browser_permissionPrompts.js | Unexpected exception in [ compactDark, persistentStorage ]: Timed out -
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2021-07-30 15:52:24+00:00
Resolved: 2021-08-04 11:40:14+00:00

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

---
```
[task 2021-07-30T14:42:38.157Z] 14:42:38     INFO - Configured UI for [ compactDark, geo ] successfully
[task 2021-07-30T14:42:38.159Z] 14:42:38     INFO - TEST-PASS | browser/tools/mozscreenshots/permissionPrompts/browser_permissionPrompts.js | A valid bounding box was found - 
[task 2021-07-30T14:42:39.337Z] 14:42:39     INFO - _onConfigurationReady
[task 2021-07-30T14:42:39.337Z] 14:42:39     INFO - Combination 26/40: compactDark_persistentStorage
[task 2021-07-30T14:42:39.337Z] 14:42:39     INFO - promising persistentStorage
[task 2021-07-30T14:42:39.338Z] 14:42:39     INFO - calling persistentStorage
[task 2021-07-30T14:42:39.365Z] 14:42:39     INFO - called persistentStorage
[task 2021-07-30T14:43:09.781Z] 14:43:09     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 98
[task 2021-07-30T14:43:39.369Z] 14:43:39     INFO - TEST-INFO | started process screentopng
[task 2021-07-30T14:43:39.920Z] 14:43:39     INFO - TEST-INFO | screentopng: exit 0
[task 2021-07-30T14:43:39.921Z] 14:43:39     INFO - Buffered messages logged at 14:41:39
[task 2021-07-30T14:43:39.921Z] 14:43:39     INFO - Entering test bound setup
[task 2021-07-30T14:43:39.921Z] 14:43:39     INFO - Buffered messages finished
[task 2021-07-30T14:43:39.922Z] 14:43:39     INFO - TEST-UNEXPECTED-FAIL | browser/tools/mozscreenshots/permissionPrompts/browser_permissionPrompts.js | Unexpected exception in [ compactDark, persistentStorage ]: Timed out - 
[task 2021-07-30T14:43:39.922Z] 14:43:39     INFO - Stack trace:
[task 2021-07-30T14:43:39.923Z] 14:43:39     INFO - chrome://mochikit/content/browser-test.js:test_ok:1343
[task 2021-07-30T14:43:39.923Z] 14:43:39     INFO - resource://mozscreenshots/TestRunner.jsm:_performCombo:433
[task 2021-07-30T14:43:39.924Z] 14:43:39     INFO - 	Timed out
[task 2021-07-30T14:43:39.926Z] 14:43:39     INFO - Combination 27/40: compactDark_loginCapture
[task 2021-07-30T14:43:39.926Z] 14:43:39     INFO - promising loginCapture
[task 2021-07-30T14:43:39.927Z] 14:43:39     INFO - calling loginCapture
[task 2021-07-30T14:43:39.928Z] 14:43:39     INFO - called loginCapture
[task 2021-07-30T14:43:40.614Z] 14:43:40     INFO - fulfilled all applyConfig so setting lastCombo.
[task 2021-07-30T14:43:40.615Z] 14:43:40     INFO - Configured UI for [ compactDark, loginCapture ] successfully
[task 2021-07-30T14:43:40.617Z] 14:43:40     INFO - TEST-PASS | browser/tools/mozscreenshots/permissionPrompts/browser_permissionPrompts.js | A valid bounding box was found - 
```
Bug: Intermittent browser/tools/mozscreenshots/permissionPrompts/browser_permissionPrompts.js | Unexpected exception in [ <comboA>, <comboB> ]: Timed out -
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2021-07-30 15:53:57+00:00
Resolved: 2022-08-12 20:38:25+00:00

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

---
```
[task 2021-07-30T15:36:12.717Z] 15:36:12     INFO - TEST-PASS | browser/tools/mozscreenshots/permissionPrompts/browser_permissionPrompts.js | A valid bounding box was found - 
[task 2021-07-30T15:36:13.902Z] 15:36:13     INFO - _onConfigurationReady
[task 2021-07-30T15:36:13.903Z] 15:36:13     INFO - Combination 37/40: alpenGlow_loginCapture
[task 2021-07-30T15:36:13.903Z] 15:36:13     INFO - promising loginCapture
[task 2021-07-30T15:36:13.903Z] 15:36:13     INFO - calling loginCapture
[task 2021-07-30T15:36:13.939Z] 15:36:13     INFO - called loginCapture
[task 2021-07-30T15:36:18.072Z] 15:36:18     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 98
[task 2021-07-30T15:37:03.073Z] 15:37:03     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 97
[task 2021-07-30T15:37:13.940Z] 15:37:13     INFO - TEST-INFO | started process screentopng
[task 2021-07-30T15:37:14.319Z] 15:37:14     INFO - TEST-INFO | screentopng: exit 0
[task 2021-07-30T15:37:14.319Z] 15:37:14     INFO - Buffered messages logged at 15:34:48
[task 2021-07-30T15:37:14.319Z] 15:37:14     INFO - Entering test bound setup
[task 2021-07-30T15:37:14.320Z] 15:37:14     INFO - Buffered messages finished
[task 2021-07-30T15:37:14.320Z] 15:37:14     INFO - TEST-UNEXPECTED-FAIL | browser/tools/mozscreenshots/permissionPrompts/browser_permissionPrompts.js | Unexpected exception in [ alpenGlow, loginCapture ]: Timed out - 
[task 2021-07-30T15:37:14.320Z] 15:37:14     INFO - Stack trace:
[task 2021-07-30T15:37:14.321Z] 15:37:14     INFO - chrome://mochikit/content/browser-test.js:test_ok:1343
[task 2021-07-30T15:37:14.322Z] 15:37:14     INFO - resource://mozscreenshots/TestRunner.jsm:_performCombo:433
[task 2021-07-30T15:37:14.323Z] 15:37:14     INFO - 	Timed out
[task 2021-07-30T15:37:14.324Z] 15:37:14     INFO - Combination 38/40: alpenGlow_notifications
[task 2021-07-30T15:37:14.325Z] 15:37:14     INFO - promising notifications
[task 2021-07-30T15:37:14.326Z] 15:37:14     INFO - calling notifications
[task 2021-07-30T15:37:14.327Z] 15:37:14     INFO - called notifications
[task 2021-07-30T15:37:15.122Z] 15:37:15     INFO - fulfilled all applyConfig so setting lastCombo.
[task 2021-07-30T15:37:15.123Z] 15:37:15     INFO - Configured UI for [ alpenGlow, notifications ] successfully
[task 2021-07-30T15:37:15.124Z] 15:37:15     INFO - TEST-PASS | browser/tools/mozscreenshots/permissionPrompts/browser_permissionPrompts.js | A valid bounding box was found - 
```
Bug: [XFA] Alignment issues in tables
Status: NEW
Priority: P3
Created: 2021-07-30 16:24:08+00:00
Resolved: 2022-02-24 18:20:50+00:00

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

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

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

**Note**
* When the user loads a specific PDF and compares its rendering with the one seen in Adobe, he will notice alignment issues.

**Affected versions**
* Nightly v92.0a1

**Affected platforms**
* all

**Steps to reproduce**
1. Launch browser.
2. Flip the pdfjs.enableXfa to true.
3. Load the attached PDF file.
4. Search for the areas in the demo pics.

**Expected result**
* The document is correctly displayed (as in Adobe Reader).

**Actual result**
* Alignment issues are being observed.

**Regression range**
* This is not a regression.

**Additional information:**
* -
Bug: about:preferences keeps the refresh driver ticking at 60Hz all the time
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-07-30 17:48:36+00:00
Resolved: 2022-07-27 07:33:55+00:00

This was introduced when bug 1689727 changed `#updateDeck` from a xul deck to a stack with the non-selected decks hidden using `visiblity: hidden`. The correct fix would be to fix bug 560067, but I'll provide a patch to add an easy workaround.

Profile showing the problem: https://share.firefox.dev/3iXPV52 (There's 4 "Image Animation" markers, and the RefreshDriverTick markers slow down only after about:preferences is closed)
Profile with the patch applied: https://share.firefox.dev/3y9QPC1 (There's only one "Image Animation" marker, and the refresh driver slows down after 1.4s at the end of the update check)
Bug: Firefox 90.0.1 caused my computer to freeze up after 10 minutes of usage with 26 tabs open
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2021-07-30 19:49:07+00:00
Resolved: 2021-09-17 13:24:00+00:00

User Agent: Mozilla/5.0 (X11; Linux i686; rv:78.0) Gecko/20100101 Firefox/78.0

Steps to reproduce:

1.Upgrade Firefox on Linux Mint 19.3 32-bit(on 64-bit CPU,accidentally downloaded wrong iso)  to version 90.0.1
2.Open 26 tabs
3. wait 10 minutes


Actual results:

Firefox fills up all 8GB of RAM on my computer and most of the 2GB of swap, practically freezing up the computer. Luckily 90.0 was still available in the Linux Mint repos so I downgraded to that and it works fine now(Reporting this bug so it gets fixed in Firefox 91).


Expected results:

Firefox doesn't fill up RAM/swap, no downgrade needed.
Bug: Facebook & instagram don't load images intermittently, haven't been loading for the past two weeks.
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2021-07-30 21:43:42+00:00
Resolved: 2021-08-25 14:04:22+00:00

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

Steps to reproduce:

Cleared cache


Actual results:

it was fixed for a day, then the problem reappeared, fb and instagram works fine with chrome


Expected results:

the problem should have gone for good
Bug: Intermittent browser/base/content/test/protectionsUI/browser_protectionsUI_icon_state.js | Test timed out -
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2021-07-31 11:03:28+00:00
Resolved: 2022-10-04 17:03:24+00:00

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

---
```
[task 2021-07-31T08:41:24.291Z] 08:41:24     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/protectionsUI/browser_protectionsUI_icon_state.js | Test timed out - 
[task 2021-07-31T08:41:24.306Z] 08:41:24     INFO - GECKO(8720) | MEMORY STAT | vsize 2104398MB | vsizeMaxContiguous 65873277MB | residentFast 352MB | heapAllocated 97MB
[task 2021-07-31T08:41:24.307Z] 08:41:24     INFO - TEST-OK | browser/base/content/test/protectionsUI/browser_protectionsUI_icon_state.js | took 90170ms
[task 2021-07-31T08:41:24.318Z] 08:41:24     INFO - GECKO(8720) | [Child 6584: Main Thread]: I/DocShellAndDOMWindowLeak ++DOCSHELL 22839cafc00 == 1 [pid = 6584] [id = 6]
[task 2021-07-31T08:41:24.318Z] 08:41:24     INFO - GECKO(8720) | [Child 6584: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 1 (228403c0900) [pid = 6584] [serial = 14] [outer = 0]
[task 2021-07-31T08:41:24.319Z] 08:41:24     INFO - GECKO(8720) | [Child 6584: Main Thread]: I/DocShellAndDOMWindowLeak ++DOMWINDOW == 2 (228403b8000) [pid = 6584] [serial = 15] [outer = 228403c0900]
[task 2021-07-31T08:41:24.348Z] 08:41:24     INFO - checking window state
[task 2021-07-31T08:41:24.349Z] 08:41:24     INFO - Not taking screenshot here: see the one that was previously logged
[task 2021-07-31T08:41:24.350Z] 08:41:24     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/protectionsUI/browser_protectionsUI_icon_state.js | Found a browser window after previous test timed out - 
[task 2021-07-31T08:41:24.350Z] 08:41:24     INFO - GECKO(8720) | must wait for focus
[task 2021-07-31T08:41:24.446Z] 08:41:24     INFO - Not taking screenshot here: see the one that was previously logged
[task 2021-07-31T08:41:24.447Z] 08:41:24     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/protectionsUI/browser_protectionsUI_icon_state.js | Uncaught exception received from previously timed out test - at resource://testing-common/BrowserTestUtils.jsm:500 - Error: The window unloaded while we were waiting for the browser to load - this should never happen.
[task 2021-07-31T08:41:24.447Z] 08:41:24     INFO - Stack trace:
[task 2021-07-31T08:41:24.447Z] 08:41:24     INFO - listener@resource://testing-common/BrowserTestUtils.jsm:500:15
[task 2021-07-31T08:41:24.462Z] 08:41:24     INFO - GECKO(8720) | [GPU 7052, Compositor] WARNING: Possibly dropping task posted to updater thread: file /builds/worker/checkouts/gecko/gfx/layers/apz/src/APZUpdater.cpp:370
```
Bug: Search engines don't synchronize
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-07-31 13:56:01+00:00
Resolved: 2021-07-31 17:58:10+00:00

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

Steps to reproduce:

Log in with my account on a computer, add a search engine (google maps), add an alias to the existing and new search engine, and delete some default search engines.
Then I logged in in another computer with the same account


Actual results:

The new search engine that I had added was not available. I had to add google maps again. Also, I was given all the default search engines. Addicionally, I had to set the alias again


Expected results:

The modifications to the search engines should've been synchronized.
Bug: Manage Exceptions for Cookies Does Nothing
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2021-08-01 05:20:57+00:00
Resolved: 2021-08-19 16:22:39+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1.2 Safari/605.1.15

Steps to reproduce:

Go to Preferences > Privacy & Security

Under Cookies & Site Data, Click Manage Exceptions.


Actual results:

Nothing happens. Window to edit cookie exceptions does not appear.


Expected results:

Window to edit cookie exceptions should appear, allowing for editing of allowed and blocked cookies.
Bug: Intermittent browser/tools/mozscreenshots/permissionPrompts/browser_permissionPrompts.js | Unexpected exception in [ compactLight, loginCapture ]: Timed out -
Status: RESOLVED
Priority: P5
Resolution: DUPLICATE
Created: 2021-08-01 07:43:39+00:00
Resolved: 2021-08-04 11:40:14+00:00

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

---
```
[task 2021-08-01T06:19:57.387Z] 06:19:57     INFO - TEST-INFO | screentopng: exit 0
[task 2021-08-01T06:19:57.388Z] 06:19:57     INFO - Buffered messages logged at 06:18:17
[task 2021-08-01T06:19:57.388Z] 06:19:57     INFO - Entering test bound setup
[task 2021-08-01T06:19:57.390Z] 06:19:57     INFO - Buffered messages finished
[task 2021-08-01T06:19:57.390Z] 06:19:57     INFO - TEST-UNEXPECTED-FAIL | browser/tools/mozscreenshots/permissionPrompts/browser_permissionPrompts.js | Unexpected exception in [ compactLight, loginCapture ]: Timed out - 
[task 2021-08-01T06:19:57.390Z] 06:19:57     INFO - Stack trace:
[task 2021-08-01T06:19:57.391Z] 06:19:57     INFO - chrome://mochikit/content/browser-test.js:test_ok:1343
[task 2021-08-01T06:19:57.392Z] 06:19:57     INFO - resource://mozscreenshots/TestRunner.jsm:_performCombo:433
[task 2021-08-01T06:19:57.392Z] 06:19:57     INFO - 	Timed out
[task 2021-08-01T06:19:57.392Z] 06:19:57     INFO - Combination 18/40: compactLight_notifications
[task 2021-08-01T06:19:57.392Z] 06:19:57     INFO - promising notifications
[task 2021-08-01T06:19:57.392Z] 06:19:57     INFO - calling notifications
[task 2021-08-01T06:19:57.392Z] 06:19:57     INFO - called notifications
[task 2021-08-01T06:19:58.029Z] 06:19:58     INFO - fulfilled all applyConfig so setting lastCombo.
[task 2021-08-01T06:19:58.030Z] 06:19:58     INFO - Configured UI for [ compactLight, notifications ] successfully
[task 2021-08-01T06:19:58.031Z] 06:19:58     INFO - TEST-PASS | browser/tools/mozscreenshots/permissionPrompts/browser_permissionPrompts.js | A valid bounding box was found - 
```
Bug: "Empfohlen von Pocket" ist heute wieder einmal verschwunden.
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2021-08-01 10:45:05+00:00
Resolved: 2021-08-04 14:25:28+00:00

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

Steps to reproduce:

I opened a new tab.
Later I opened the settings.


Actual results:

A new tab appeared, but without "Empfohlen von Pocket".
When opening the settings for the start screen, there was no point for "Empfohlen von Pocket".


Expected results:

A new tab should appear, and one of the areas should be "Empfohlen von Pocket".
In the start screen settings should be the possibility to enable "Empfohlen von Pocket".
Bug: Firefox Relay recommended even though website scripts do not reference Facebook APIs
Status: RESOLVED
Priority: --
Resolution: MOVED
Created: 2021-08-01 15:22:47+00:00
Resolved: 2021-08-04 08:41:22+00:00

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

Steps to reproduce:

Navigate to a login page that uses Email Address as the username (even your own website exhibits this behavior).


Actual results:

The "fence" icon appears on the username input, and clicking on it displays the following dialog:

Facebook Container
Allow Facebook to track you here?
This site can share your email address with Facebook, which allows Facebook to track you. Use a service like Firefox Relay to hide your real email address.
Don’t show me this again
Dismiss    Try Firefox Relay


Expected results:

Nothing - no icon.

Suggesting this new Mozilla product on every website regardless of whether FB code or HTML is detected or not is disingenuous marketing (fear based). My website and apps (in development) are extremely privacy-centric and assure users that their private data will not be shared. Suggesting to them otherwise could do harm to my bottom line.
Bug: When using firefox sync, applying new theme does not sync to account, causing theme to default to a previous theme
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2021-08-01 19:30:27+00:00
Resolved: 2021-08-03 14:26:58+00:00

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

Steps to reproduce:

Using firefox sync. Apply any new theme. Close firefox. Open firefox and new theme shows briefly, then switches to a previously synced theme. Does not happen when sync is signed out. Running Windows 10 21H1, Dark system theme. Issue can easily be reproduced, including when firefox is refreshed and re-installed. I also tried a new Windows 10 user profile, and issue was reproduced after logging into Firefox sync. I have not tried deleting my Firefox sync account and creating a new one.


Actual results:

see "What did you do?" Also, I googled and tried many different settings in about:config based on the searches, but nothing worked.


Expected results:

I would have expected that when a new theme is added, the theme is replicated to the rest of the devices. However, in this case, it seems the default theme is being applied to all devices, instead of the a theme extension, even though extensions all settings are being synced.
Bug: Some JSWindowActors use unknown param `group`
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2021-08-01 20:51:51+00:00
Resolved: 2021-08-03 01:10:09+00:00

It seems `group` was the name of a related param for Legacy actors, so the intent from bug 1505916, and bug 1712941 is clear.
Bug: [XFA] Image alt text not exposed
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2021-08-02 02:05:39+00:00
Resolved: 2023-06-02 15:21:48+00:00

STR (with the NVDA screen reader):

1. Open this PDF in Firefox: https://bug1671648.bmoattachments.org/attachment.cgi?id=9182033
2. Wait a few seconds for the first page to load.
3. Press control+home to ensure you are at the top of the document.
4. Press g to move to the next image.
    - Expected: NVDA should report "Canadian Flag image. Citizenship and Immigration Canada.  graphic"
    - Actual: NVDA reports "page 2 region  Loading...  graphic", which is the pdf.js placeholder for a page that is loading. It completely skips over the image on the first page.

I'm not sure how XFA encodes alt text for images, but Acrobat reports "Canadian Flag image. Citizenship and Immigration Canada." as the label for that image.

While the image isn't particularly important in this case, an image could well provide vital information to the user in another document.
Bug: [XFA] Headings not exposed for accessibility
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2021-08-02 02:15:13+00:00
Resolved: 2023-06-02 15:21:48+00:00

STR (with the NVDA screen reader):

1. Open this PDF in Firefox: https://bug1671648.bmoattachments.org/attachment.cgi?id=9182033
2. Wait a few seconds for the first page to load.
3. Press control+home to ensure you are at the top of the document.
4. Press h to move to the next heading.
    - Expected: NVDA should say "APPLICATION FOR VISITOR VISA (TEMPORARY RESIDENT VISA)  heading level 1"
    - Actual: NVDA says "no next heading"

Semantic headings make it much easier for screen reader users to know that a piece of text is a heading (rather than having to guess based on context), as well as making it much more efficient to navigate between sections.

I'm not sure how XFA encodes this information, but it is exposed correctly in Acrobat Reader. Pdf.js could expose this by using the attributes role="heading" aria-level="n", where n is the heading level.
Bug: [XFA] A11y form field labels not exposed
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2021-08-02 02:27:32+00:00
Resolved: 2023-06-02 15:21:49+00:00

STR (with the NVDA screen reader):

1. Open this PDF in Firefox: https://bug1671648.bmoattachments.org/attachment.cgi?id=9182033
2. Wait a few seconds for the first page to load.
3. Press control+home to ensure you are at the top of the document.
4. Press NVDA+control+f to open the NVDA Find dialog. (The NVDA key is usually the insert key by default.)
5. Type "Current country" (no quotes) and press enter.
6. Press e to move to the next text box.
    - Expected: NVDA should say "Question 7 C If your immigration status is other, please give details.  edit multi line"
    - Actual: NVDA says only "edit multi line"

There are plenty of other form fields in this document that do have associated labels. They don't seem to be the labels the author intended for accessibility purposes, though. For the most part, this isn't a huge concern. I chose the example above because in this case, the author did specify a label, but there is no associated label at all with pdf.js. This makes it impossible for a screen reader user to be certain what they should fill in here.

I'm not sure how XFA encodes this information, but it is picked up by Acrobat Reader. Pdf.js could output these labels in the HTML using the aria-label attribute.
Bug: [XFA] Intended document order not exposed to accessibility
Status: NEW
Priority: P2
Created: 2021-08-02 02:52:19+00:00
Resolved: 2023-06-02 15:21:49+00:00

STR (with the NVDA screen reader):

1. Open this PDF in Firefox: https://bug1671648.bmoattachments.org/attachment.cgi?id=9182033
2. Wait a few seconds for the first page to load.
3. Press control+home to ensure you are at the top of the document.
4. Press d to move to the top of the actual content.
5. Press down arrow several times, reading the first few lines of the document.
    - Expected: NVDA should read "PROTECTED WHEN COMPLETED - B", the "Canadian Flag image. Citizenship and Immigration Canada." image (though this is impacted by bug 1723418), "Page  of", then the "APPLICATION FOR VISITOR VISA (TEMPORARY RESIDENT VISA)" heading.
    - Actual: After "PROTECTED WHEN COMPLETED - B", NVDA reads "IMM 5257 (06-2019) E", then "This form is made available by Immigration, Refugees and Citizenship Canada and is not to be sold ", etc.

What gets read here might be the order of the text in the document, but it isn't the visual order, nor is it the document order specified by the author for accessibility purposes. This is very confusing for screen reader users. In this example, it requires them to read content that isn't of interest (which is why it is placed at the bottom of the page visually). In other cases, it could be a lot more problematic.

I'm not sure how XFA exposes this information, but it is picked up by Acrobat Reader. It could be exposed by pdf.js either by reordering the DOM or by using aria-owns to reorder the accessibility tree.