requestAnimationFrame callback with "double" not "int" value

[DartBot]

This issue was originally filed by @bp74

---

What steps will reproduce the problem?

1. Call window.requestAnimationFrame(onAnimationFrame);
2. Method: bool onAnimationFrame(int time)

What is the expected output? What do you see instead?

The time argument should be an integer, but starting with the latest Dartium Build it is a double value.
The value is somthing like "9059.999999939464".

What version of the product are you using? On what operating system?

Dart Editor 7313 32 bit, Windows 7 64 bit

[DartBot]

This comment was originally written by @bp74

---

Sorry i was wrong, i checked the source of the SDK:
typedef bool RequestAnimationFrameCallback(num highResTime);

It is a num, not an int!

But the documentation is still wrong, it says "int time".
http://api.dartlang.org/html/RequestAnimationFrameCallback.html

[DartBot]

This comment was originally written by [email protected]

---

Added Area-DOM, Triaged labels.

[DartBot]

This comment was originally written by @bp74

---

The documentation says "num highResTime" now.

Maybe someone should check the specification if it says that a double value is valid or it should be an int. I havn't found it ...

[DartBot]

This comment was originally written by @bp74

---

I just saw a new post on html5rocks:
RequestAnimationFrame with sub-millisecond precision.

http://updates.html5rocks.com/2012/05/requestAnimationFrame-API-now-with-sub-millisecond-precision

So it is clear that the time is a double. Please close the issue.

[DartBot]

This comment was originally written by @bp74

---

Okay we are back to "int time" ...
I will stay with "num time" and i should be save.

[DartBot]

This comment was originally written by [email protected]

---

Bernhard, we just follow WebKit here: it first switched to doubles in IDL and then reverted the change back, see http://trac.webkit.org/log/trunk/Source/WebCore/dom/RequestAnimationFrameCallback.idl

Sorry, I cannot fix it just for Dartium. If you prefer, you can probably file a bug against WebKit, but I assume this topic is actively discussed these days.

---

Added WontFix label.