Closed Bug 1718245 Opened 3 years ago Closed 3 years ago

[XFA] Some text input fields are inaccessible

Categories

(Firefox :: PDF Viewer, defect, P1)

Desktop
All
defect

Tracking

()

VERIFIED FIXED
Tracking Status
firefox89 --- disabled
firefox90 --- wontfix
firefox91 --- verified
firefox92 --- verified

People

(Reporter: danibodea, Assigned: calixte)

References

Details

Attachments

(4 files, 1 obsolete file)

Note

  • When the user loads a specific PDF file in Adobe Reader and Firefox, he scrolls to page 11, section 13, subsection 13.1, and clicks inside the input boxes of fields named "Name of Issuer" or "Law governing the bonds", he will notice that the input fields are inaccessible.

Affected versions

  • Nightly v91.0a1

Affected platforms

  • all

Preconditions

  • Flip the "pdfjs.enableXfa" pref to true.

Steps to reproduce

  1. Launch browser.
  2. Load the attached PDF file.
  3. Scroll to pages 11, section 13, subsection 13.1.
  4. Click inside the input boxes of fields named "Name of Issuer" or "Law governing the bonds".

Expected result

  • The cursor appears and the user is able to input text.

Actual result

  • The cursor does not appear and the user is NOT able to input text.

Regression range

  • Not a regression, but an implementation fault.
Assignee: nobody → cdenizet
Status: NEW → ASSIGNED
Priority: -- → P1

Correct demo.

Attachment #9228958 - Attachment is obsolete: true
QA Whiteboard: [pdf_xfa_generic]

Could you check if this is due to JS or not?

Flags: needinfo?(cdenizet)

It's an implementation issue.
The field here has no ui so according to the spec:

If the UI element contains no children or is not present, the application chooses a default user interface for the 
container, based on the type of the container's content. 

So we should probably add a textfield by default.

Flags: needinfo?(cdenizet)
Commit merged into master by GitHub Authored by calixteman (calixteman)
Depends on: 1722352
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED

I have verified the fix in Beva v91.0b9 and Nightly v92.0a1 from 2021-07-30.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: