1397669 - NVDA is able to read the password while typing it

Status: RESOLVED WONTFIX

(Core :: Disability Access APIs, defect)

Description

[Mihai Boldan, Desktop QA [:mboldan]]

[Affected versions]:
- Firefox 56.0b9, Firefox 55.0.3

[Affected platforms]:
- Windows 7x64

[Steps to reproduce]:
Prerequisites: NVDA app is opened.
1. Launch Firefox with a clean profile.
2. Go to https://mail.google.com.
3. Enter a valid email address and click 'NEXT' button.
4. Enter the password and listen the narrator.

[Expected result]:
- NVDA app is not able to recognize the entered characters.

[Actual result]:
- NVDA is spelling each entered character.

[Regression range]:
- This seems to be a regression.
- Searched manually for the regression and seems that the firs affected build is 55.0b11(20170720101430).

[Additional notes]:
- This issue is reproducible only with clean profile. If restarting the browser or open it with a dirty profile, the issue is not reproducible.
- The issue is reproducible also on other sites where password is required (Eg. Facebook).
- Not reproducible on Firefox Nightly.

Comment 1

[Dana Keeler (she/her) (use needinfo) [:keeler]]

This should probably start off in untriaged, since I don't think security is quite the right component.

Comment 2

[Marco Zehe (:MarcoZ)]

(In reply to Mihai Boldan, QA [:mboldan] from comment #0)
> Prerequisites: NVDA app is opened.
> 1. Launch Firefox with a clean profile.
> 2. Go to https://mail.google.com.
> 3. Enter a valid email address and click 'NEXT' button.
> 4. Enter the password and listen the narrator.

So, are we talking NVDA, like downloaded from http://www.nvda-project.org, or Microsoft Narrator, which is built into Windows, but is a totally different thing?

I am not aware of any accessibility-specific things that landed in the 55 cycle, or were uplifted there, that could cause such behavior. Note, however, that Narrator uses different methods to access our APIs than NVDA does. Moreover, Narrator in Windows 7 was a very rudimentary screen reader.

Can you reproduce this on newer Windows platforms like Windows 10, too?

Comment 3

[Mihai Boldan, Desktop QA [:mboldan]]

(In reply to Marco Zehe (:MarcoZ) from comment #2)
> (In reply to Mihai Boldan, QA [:mboldan] from comment #0)
> > Prerequisites: NVDA app is opened.
> > 1. Launch Firefox with a clean profile.
> > 2. Go to https://mail.google.com.
> > 3. Enter a valid email address and click 'NEXT' button.
> > 4. Enter the password and listen the narrator.
> 
> So, are we talking NVDA, like downloaded from http://www.nvda-project.org,
> or Microsoft Narrator, which is built into Windows, but is a totally
> different thing?
> 
> I am not aware of any accessibility-specific things that landed in the 55
> cycle, or were uplifted there, that could cause such behavior. Note,
> however, that Narrator uses different methods to access our APIs than NVDA
> does. Moreover, Narrator in Windows 7 was a very rudimentary screen reader.
> 
> Can you reproduce this on newer Windows platforms like Windows 10, too?

For testing we used the NVDA from http://www.nvda-project.org. 
The issue is reproducible also on Windows 10x64. 
Please let me know if you need any other information about this issue.

Comment 4

[Marco Zehe (:MarcoZ)]

(In reply to Mihai Boldan, QA [:mboldan] from comment #3)
> > Can you reproduce this on newer Windows platforms like Windows 10, too?
> 
> The issue is reproducible also on Windows 10x64. 
> Please let me know if you need any other information about this issue.

Yes. When you started with that clean profile, were you notified that multi-process Firefox, AKA E10S, was deactivated due to accessibility, and did you then choose to not restart Firefox? If so, you were entering an invalid scenario, since E10S is not supported with any accessibility client in Firefox 56 and earlier.

Once you then restarted Firefox and had a "dirty" profile, E10S was deactivated, and you were in a valid scenario, where you could no longer reproduce the bug.

So: Did you choose to not restart Firefox when you were given the choice after E10S was deactivated? If so, this bug is not a valid one. :)

Comment 5

[Mihai Boldan, Desktop QA [:mboldan]]

(In reply to Marco Zehe (:MarcoZ) from comment #4)
> (In reply to Mihai Boldan, QA [:mboldan] from comment #3)
> > > Can you reproduce this on newer Windows platforms like Windows 10, too?
> > 
> > The issue is reproducible also on Windows 10x64. 
> > Please let me know if you need any other information about this issue.
> 
> Yes. When you started with that clean profile, were you notified that
> multi-process Firefox, AKA E10S, was deactivated due to accessibility, and
> did you then choose to not restart Firefox? If so, you were entering an
> invalid scenario, since E10S is not supported with any accessibility client
> in Firefox 56 and earlier.
> 
> Once you then restarted Firefox and had a "dirty" profile, E10S was
> deactivated, and you were in a valid scenario, where you could no longer
> reproduce the bug.
> 
> So: Did you choose to not restart Firefox when you were given the choice
> after E10S was deactivated? If so, this bug is not a valid one. :)


There was a pop-up displayed for 1 second. But I didn't had time to see what's about, or to select one of the available options. 
So, taking in consideration what you said above, I guess that this might be the cause of this problem.

Comment 6

[Marco Zehe (:MarcoZ)]

(In reply to Mihai Boldan, QA [:mboldan] from comment #5)
> There was a pop-up displayed for 1 second. But I didn't had time to see
> what's about, or to select one of the available options. 

Roxana filed this as bug 1398054.

> So, taking in consideration what you said above, I guess that this might be
> the cause of this problem.

Then I suggest closing this bug as INVALID. :)

Comment 7

[David Bolter [:davidb] (NeedInfo me for attention)]

Closing, please reopen if necessary.