1679241 - Firefox Crashes when the URL is Deleted while VoiceOver is ON

Status: RESOLVED DUPLICATE of bug 1679075

(Core :: Disability Access APIs, defect)

Description

[Rares Doghi, Desktop QA]

Attachment: VoiceCrash.mp4

[Affected versions]
Firefox 85.0a1 (2020-11-24)

[Affected platforms]
MacOsX

[Preconditions]
Have VoiceOver enabled on MacOS (Command + F5)

[Steps to reproduce]

1. Open the Firefox browser and reach the URL bar using the VoiceOver Commands
2. Reach the end of the URL text and use Delete to erase everything one by one

[Expected result]
The User should be able to delete any Text from the URL bar without issues

[Actual result]
The Moment the last letter of the URL is deleted, Firefox will instantly crash

Notes:
It seems to be a recent Regression, here is the pushlog from the first bad Build, it seems that Bug 1672700 might be the cause of it
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=98e8b23c627e0839acf9f5b87f1e881d3e6a40b0&tochange=bb7606e92697cbf94bd0b7fe0710acd53041cfa5

Comment 1

[Rares Doghi, Desktop QA]

I Think the Severity for this issue should be an S2.

Hi Eitan can you please take a look at this issue it seems that Bug 1672700 might be the cause of it.

Comment 2

[Rares Doghi, Desktop QA]

I Was convinced the issue is caused by the lack of text in the URL bar but I think this issue also happens when the user opens a new empty tab and maybe thats the cause of it and not the actual action of deleteing the existing text ?? @Eitan if these are two different issues please let me know so I can log a different issue for it.

To sum Up - Firefox will crash when I delete the text from the URL bar, but also if I click the new tab button which would open a tab with an empty url bar.

Comment 3

[Rares Doghi, Desktop QA]

ok so it seems the New Tab crash only occur with the latest Nightly build 85.0a1 (2020-11-25).

Comment 4

[Rares Doghi, Desktop QA]

I did another Regression range just for this new tab crash and it pointed me to the same Issue. Bug 1672700

Comment 5

[Eitan Isaacson [:eeejay]]

I think this is a dup of bug 1679075. Once that lands can you please verify? Thanks!

Comment 6

[Rares Doghi, Desktop QA]

Yes this issue was a duplicate of Bug 1679075, this and other related issues were fixed when Bug 1679075 landed. Thank you Eitan!