hugoloza / gwt-mobile-webkit

Automatically exported from code.google.com/p/gwt-mobile-webkit
2 stars 0 forks source link

position.getTimestamp() should return long instead of int #29

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.in the positionCallback call position.getTimestamp();
2.
3.

What is the expected output? What do you see instead?
For Java, DOMTimeStamp is bound to the long type. For ECMAScript, DOMTimeStamp 
is bound to the Date type because the range of the integer type is too small. 
(this comes from 
http://www.w3.org/TR/DOM-Level-3-Core/core.html#Core-DOMTimeStamp)

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

I am using 0.9.5 
Please provide any additional information below.
Great work guys ! i love it ! 

Original issue reported on code.google.com by kristoff...@gmail.com on 16 Dec 2010 at 10:20

GoogleCodeExporter commented 9 years ago
Hi Kristoff,

Thanks for reporting! You are absolutely right: an int doesn't fit the bill. 
However, a long is unacceptable due to lack of support in JSNI, so we should 
use a Date instead.

Will work on it!

Original comment by bguijt on 16 Dec 2010 at 11:09

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r343.

Original comment by bguijt on 16 Dec 2010 at 11:58