If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Email input box cannot be deleted when Screen reader is used

NEW
Unassigned

Status

()

Toolkit
Password Manager
9 months ago
9 months ago

People

(Reporter: roxana.leitan@softvision.ro, Unassigned)

Tracking

53 Branch
x86_64
Windows 10
Points:
---

Firefox Tracking Flags

(firefox51 unaffected, firefox52 unaffected, firefox53 affected, firefox54 affected)

Details

(Reporter)

Description

9 months ago
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170120030214

[Affected versions]:
Nightly 53.0a1 

[Affected platforms]:
Windows 10

[Prerequisite]:
Download and install the screen reader :http://www.nvaccess.org/download

[Steps to reproduce]:
1.Open Nightly with new pofile
2.Go to https://gmail.com/
3.Enter an invalid email
4.Click "Next" button
5.Use mouse to select(highlight)the email entered at step 3
6.Press "backspace" key 

[Expected result]:
The email should be deleted

[Actual result]:
The email is not deleted
(Reporter)

Updated

9 months ago
status-firefox52: --- → unaffected

Comment 1

9 months ago
What bug caused this issue?  It is odd that 52 is unaffected but 53 is.  Can you doublecheck 52 and also check 51?  Thank you!
Flags: needinfo?(roxana.leitan)
(Reporter)

Comment 2

9 months ago
The issue is not reproducible on FF latest Release 51 and FF latest Beta 52(20170124094647) and is reproducible on FF latest Aurora 53 and FF Nightly 54.

Using the mozregression tool I got to this regression window:

Last good revision: 03e795912fdbb000ac95f040d84e26d3eaa8c20a
First bad revision: 8b2d92343bcb398075c909c587ec020286528059
Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=03e795912fdbb000ac95f040d84e26d3eaa8c20a&tochange=8b2d92343bcb398075c909c587ec020286528059

I will set the status flags accordingly.
status-firefox51: --- → unaffected
status-firefox54: --- → affected
Flags: needinfo?(roxana.leitan)
You need to log in before you can comment on or make changes to this bug.