1949209 - User should be able to view what is typing, but while VoiceOver is on the signature can be visible only on the description field.

Status: NEW

(Firefox :: PDF Viewer, defect)

Description

[Monica Chiorean]

Attachment: IMG_7982.jpg

Found in

• version: 137.0a1

Affected versions

• version: 137.0a1

Tested platforms

• Affected platforms: Mac 12.6
• Unaffected platforms: Windows, Ubuntu

Preconditions

• precondition : have pref pdfjs.enableSignatureEditor set to true

Steps to reproduce

1. Open a pdf document.
2. Open the signature dialog and Type tab.
3. Open VoiceOver and move cursor on Type your signature then start typing a signature.

Expected result

• User should be able to view what is typing, but while VoiceOver is on the signature can be visible only on the description field.

Actual result

• Type your signature is displayed on top of your signature while VoiceOver is on this field.

Regression range

• Not a regression as it was recently implemented.

Comment 1

[Calixte Denizet (:calixte)]

I don't manage to reproduce the issue with Sequoia 15.2.
:Monica, could you check if it's specific to 12.6 ?
Maybe it could be a bug with VoiceOver itself.

Comment 2

[Morgan Reschenberg [:morgan]]

I was able to reproduce this only on my first interaction with signatures. On subsequent interactions, VO announces the signature as I'm typing it

Comment 3

[Monica Chiorean]

I do not have other Mac OSs only 12.6.

Comment 4

[Calixte Denizet (:calixte)]

:morgan do you think it's a bug in pdf.js ? or in Firefox ? or in VoiceOver ?
Since I've no way to reproduce it (I just spent the last 30 minutes to try to) it'd be nice if you'd have a clue or something which could help me to fix it.

Comment 5

[Morgan Reschenberg [:morgan]]

(In reply to Calixte Denizet (:calixte) from comment #4)

:morgan do you think it's a bug in pdf.js ? or in Firefox ? or in VoiceOver ?
Since I've no way to reproduce it (I just spent the last 30 minutes to try to) it'd be nice if you'd have a clue or something which could help me to fix it.

I haven't seen this happen in other firefox surfaces, so I'm inclined to say it is a problem with the specific markup presented here. That said, it could still be a voice over issue.

If it isn't easy to repro, I think it's safe to put this on the back burner for now and re-evaluate in a few weeks to see if it is still an issue.