253423 2023-03-05 18:27:43 -0800 Regression(248952@main) setInterval and setTimeout order isn't respected when timeout is 0 2023-06-15 07:53:09 -0700 1 1 1 Unclassified WebKit WebCore Misc. WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=221124 https://bugs.webkit.org/show_bug.cgi?id=258135 InRadar P2 Normal --- 1 tristan.fraipont cdumez ahmad.saleem792 ap cdumez fujii heycam rniwa sam webkit-bug-importer oldest_to_newest 1939011 0 465310 tristan.fraipont 2023-03-05 18:27:43 -0800 Created attachment 465310 Test case Online test case: https://jsfiddle.net/7g5f0cLz/ 1. Queue a callback using setInterval(cb1, 0); 2. Queue a callback using setTimeout(cb2, 0); The callback queued through setTimeout() is executed before the one queued through setInterval(). You can see this StackOverflow answer of mine https://stackoverflow.com/a/75646343/3702797 for a walk-through of the specs showing how this behavior is wrong. Basically, with the same ms value, the order should be respected. Passing another ms value than 0 will make it behave normally. 1939012 1 ahmad.saleem792 2023-03-05 18:58:06 -0800 I am able to reproduce this on WebKit ToT (261247@main) and also Chrome Canary 113 also show incorrect results: setTimeout() setInterval() Only Firefox Nightly 112 is giving 'Expected' result. 1939312 2 tristan.fraipont 2023-03-06 18:49:21 -0800 > Chrome Canary 113 also show incorrect results Yes, this certainly comes from https://bugs.webkit.org/show_bug.cgi?id=221124 which removed the clamping of setTimeout( ,0) to 1ms, following what Chrome was going to do to. They've got the same issue and it's been reported at https://crbug.com/1421612 I guess @Wanming.Lin might chime in here too. I'll mention this issue in the CRBUG too since they seem very related. 1940528 3 webkit-bug-importer 2023-03-10 15:44:11 -0800 <rdar://problem/106576260> 1940529 4 heycam 2023-03-10 15:47:39 -0800 Maybe we can make it so that setInterval(..., 0) will fire the callback immediately (i.e. honoring the 0ms) the first time, and at the clamped 1ms interval afterwards? 1958844 5 cdumez 2023-05-30 12:05:19 -0700 Pull request: https://github.com/WebKit/WebKit/pull/14499 1958893 6 ews-feeder 2023-05-30 15:14:12 -0700 Committed 264701@main (09e6c5eb406c): <https://commits.webkit.org/264701@main> Reviewed commits have been landed. Closing PR #14499 and removing active labels. 1961213 7 fujii 2023-06-12 20:37:50 -0700 fast/dom/Window/setInterval-setTimeout-zero-ordering.html is flaky. https://results.webkit.org/?suite=layout-tests&test=fast%2Fdom%2FWindow%2FsetInterval-setTimeout-zero-ordering.html 465310 2023-03-05 18:27:43 -0800 2023-03-05 18:27:43 -0800 Test case test-case.html text/html 694 tristan.fraipont PCFET0NUWVBFIGh0bWw+CjxodG1sPgogIDxoZWFkPgogICAgPG1ldGEgY2hhcnNldD0idXRmOCI+ CiAgICA8c3R5bGU+LmV4cGVjdGVkIHByZSB7IGNvbG9yOiBncmVlbiB9Ozwvc3R5bGU+CiAgPC9o ZWFkPgogIDxib2R5PgogICAgPGRpdiBjbGFzcz0iZXhwZWN0ZWQiPgogICAgICA8aDQ+RXhwZWN0 ZWQ8L2g0PgogICAgICA8cHJlPnNldEludGVydmFsKCkKc2V0VGltZW91dCgpCjwvcHJlPgogICAg PC9kaXY+CiAgICA8ZGl2IGNsYXNzPSJhY3R1YWwiPgogICAgICA8aDQ+QWN0dWFsPC9oND4KICAg ICAgPHByZT48L3ByZT4KICAgIDwvZGl2PgogICAgPHNjcmlwdD4KICAgICAgY29uc3QgcHJlID0g ZG9jdW1lbnQucXVlcnlTZWxlY3RvcigiLmFjdHVhbCBwcmUiKTsKICAgICAgY29uc3QgaWQxID0g c2V0SW50ZXJ2YWwoKCkgPT4gewogICAgICAgIHByZS50ZXh0Q29udGVudCArPSAic2V0SW50ZXJ2 YWwoKVxuIjsKICAgICAgICBwcmUuc3R5bGUuY29sb3IgPSAicmVkIjsKICAgICAgICBjbGVhcklu dGVydmFsKGlkMSk7CiAgICAgIH0pOwogICAgICBjb25zdCBpZDIgPSBzZXRUaW1lb3V0KCgpID0+ IHsKICAgICAgICBwcmUudGV4dENvbnRlbnQgKz0gInNldFRpbWVvdXQoKVxuIjsKICAgICAgICBw cmUuc3R5bGUuY29sb3IgPSAiZ3JlZW4iOwogICAgICB9KTsKICAgIDwvc2NyaXB0PgogIDwvYm9k eT4KPC9odG1sPg==