Open
Bug 1225211
Opened 9 years ago
Updated 2 years ago
Timeout fire before the “click” event loop is complete
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: hdd2008, Unassigned)
References
(Depends on 1 open bug)
Details
(Whiteboard: DUPEME)
User Agent: Opera/9.80 (Windows NT 6.1; WOW64) Presto/2.12.388 Version/12.17 Steps to reproduce: http://stackoverflow.com/questions/33741170/why-does-the-timeout-fire-before-the-click-event-loop-is-complete-on-firefox http://jsfiddle.net/pLezf4ar/ Actual results: alert shows 10 Expected results: alert shows 0
Comment 1•9 years ago
|
||
From the stackoverflow thread: "Because unlike many browsers, Firefox may allow the JavaScript thread to run other code while the alert, prompt, and confirm modals are showing, suspending the current code. [...] I would expect [...] that Mozilla will change this to be in line with other browsers, as one could argue it violates JavaScript's run-to-completion semantics for tasks, and those semantics just got beefed up and clarified by the latest specification."
Component: Untriaged → JavaScript Engine
Comment 2•9 years ago
|
||
This has nothing to do with the JS engine, which doesn't even have an event loop in Firefox so far. alert() and confirm() are pure DOM code.
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•