Open Bug 1767201 Opened 2 years ago Updated 4 months ago

Blur event is not triggered after an alert

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3)

x86_64
All
defect

Tracking

()

Tracking Status
firefox-esr91 --- wontfix
firefox99 --- affected
firefox100 --- affected
firefox101 --- affected
firefox102 --- wontfix

People

(Reporter: calixte, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Attached file plop.html

STR:

  • enter something in the first input;
  • then click on the second
  • an alert is launched "Leave a", then click on "OK";
  • the focus should be on the second input, click on the first one

When leaving the 2nd input a blur event should be triggered, hence an alert with "Leave b" should be displayed.

The bug is related to the alert() calls. With console.log() instead, it meets the reporter's expectation (can be reproduced with https://jsfiddle.net/7Lhj2ru4/).

OS: Windows 11 → All

Reproducible on Ubuntu 20.04.

The reporter's expectation meets the spec (https://html.spec.whatwg.org/multipage/timers-and-user-prompts.html#dom-alert-noargs).

Chrome behaves differently. It repeatedly creates "blur" events after clicking in the right input field. Since https://html.spec.whatwg.org/multipage/timers-and-user-prompts.html#dom-alert-noargs step 6 is optional, this seems to meet the spec.

:hsivonen, since you are the author of the regressor, bug 1696908, could you take a look?
For more information, please visit auto_nag documentation.

Flags: needinfo?(hsivonen)

Set release status flags based on info from the regressing bug 1696908

Severity: -- → S3
Priority: -- → P3

I don't think we will fix for esr91.

Flags: needinfo?(hsivonen)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: