Open Bug 1502820 Opened 7 years ago Updated 3 years ago

Incorrect focus order in the confirm dialog

Categories

(Toolkit :: Content Prompts, defect, P5)

62 Branch
defect

Tracking

()

Tracking Status
firefox63 --- affected
firefox64 --- affected
firefox65 --- affected

People

(Reporter: hardhikm, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:62.0) Gecko/20100101 Firefox/62.0 Steps to reproduce: Run "confirm("true or false") in the developer console. Actual results: A confirmation dialog opens. The focus order is "ok"=>"cancel"=>the tab's title=>address bar.... => "ok" The focus order should only be inside the confirmational dialog that came up and only on the focusable elements. Reference for guidance: https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/alertdialog.html Expected results: The focus should've only been between the "ok" and "Cancel" buttons.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0 20181102100039 I was able to reproduce the mentioned behavior on Windows 10 x64 using the latest Nightly, Beta and Fx release builds. If the dev tools are open while pressing the tab button, the focus is moved across dev tools elements and the dialog. If the dev tools are not opened the focus order is as mentioned in the report.
Status: UNCONFIRMED → NEW
Component: Untriaged → Notifications and Alerts
Ever confirmed: true
Product: Firefox → Toolkit
And closing the dev tools (ctrl+shift+i) while the confirm dialog is up apparently doesnt do anything to change the tab order. This isn't something most people will run into but it is pretty bad and a patch would be great.
Priority: -- → P5

This is very annoying behaviour for keyboard only users such as screenreader users.
Hope it gets fixed soon.

As far as I can see there are already several similar bugs with different priorities:
https://bugzilla.mozilla.org/show_bug.cgi?id=1376749
https://bugzilla.mozilla.org/show_bug.cgi?id=636320

And they have been existing already for more than 10 years.

Is there any chance that it will be fixed some day?

Severity: normal → S3
Component: Notifications and Alerts → Content Prompts
You need to log in before you can comment on or make changes to this bug.