Blur event is not triggered after an alert
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
People
(Reporter: calixte, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
402 bytes,
text/html
|
Details |
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.
Comment 1•2 years ago
|
||
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/).
Updated•2 years ago
|
Comment 2•2 years ago
|
||
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).
Comment 3•2 years ago
|
||
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.
Updated•2 years ago
|
Reporter | ||
Comment 4•2 years ago
|
||
Reporter | ||
Comment 5•2 years ago
|
||
Could it be a regression from https://bugzilla.mozilla.org/show_bug.cgi?id=1700871 ?
Comment 7•2 years ago
|
||
:hsivonen, since you are the author of the regressor, bug 1696908, could you take a look?
For more information, please visit auto_nag documentation.
Comment 8•2 years ago
|
||
Set release status flags based on info from the regressing bug 1696908
Updated•2 years ago
|
Updated•2 years ago
|
Comment 9•2 years ago
|
||
I don't think we will fix for esr91.
Updated•2 years ago
|
Updated•4 months ago
|
Description
•