In the example, isn't the requestAnimationFrame always called more than once if once queued were fired within a single frame?

[NewUserHa]

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame

What specific section or headline is this issue about?

examples

What information was incorrect, unhelpful, or incomplete?

at the beginning of the article, it says

The callback method is passed a single argument, a DOMHighResTimeStamp, which indicates the current time (based on the number of milliseconds since time origin). When multiple callbacks queued by requestAnimationFrame() begin to fire in a single frame, each receives the same timestamp even though time has passed during the computation of every previous callback's workload

but in the example, if once queued were fired within a single frame happened, weren't there always 2 or more requestAnimationFrame calls made (even those redundant async calls do nothing because previousTimeStamp !== timestamp, but it is still a useless call?)?
In the example, isn't the requestAnimationFrame always called more than once if

What did you expect to see?

maybe when found (previousTimeStamp !== timestamp), it should skip to call a new requestAnimationFrame?

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

MDN metadata

Page report details

• Folder: en-us/web/api/window/requestanimationframe
• MDN URL: https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame
• GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/web/api/window/requestanimationframe/index.md
• Last commit: c575deb
• Document last modified: 2022-09-13T06:51:25.000Z