Export to GitHub

v8cgi - issue #79

Date problem


Posted on Jan 4, 2011 by Helpful Wombat

What steps will reproduce the problem? 1. new Date 2. (new Date()).toLocaleTimeString() 3. etc...

What is the expected output? What do you see instead? a right date but i see a date = system date - 1h ex: system date report 8.45 but system.stdout(new Date) reports 7.45

What version of the product are you using? On what operating system? v8cgi 0.9 precompiled for windows on my system windows xp it

Please provide any additional information below.

Comment #1

Posted on Jan 4, 2011 by Happy Giraffe

This is not relevant to v8cgi, as all functionality related to Date is implemented by V8.

Comment #2

Posted on Jan 4, 2011 by Helpful Wombat

Ok but some things are not going well in this binary. The Date has a wrong behavior in the v8cgi shell. Chrome + v8 report a right behavior. Perhaps there is a problem. A Date object cannot be used beacause it return a bad date...

Comment #3

Posted on Jan 4, 2011 by Happy Giraffe

Please try the sample shell app which is distributed with V8... it is completely out of v8cgi's scope to do anything with the Date primordial object, which is completely managed by V8.

Status: Invalid

Labels:
Type-Defect Priority-Medium