Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(241)

Side by Side Diff: LayoutTests/fast/js/script-tests/date-preserve-milliseconds.js

Issue 20867002: Remove old tests that have been migrated to the v8 repo. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: remove unused script-tests as well Created 7 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
(Empty)
1 description(
2 'The following test checks if an existing milliseconds value gets preserved if a call to setHours(), setMinutes() or setSeconds() does not specify the milliseco nds. See <a href="https://bugs.webkit.org/show_bug.cgi?id=3759">https://bugs.web kit.org/show_bug.cgi?id=3759</a>'
3 );
4
5 var d = new Date(0);
6 d.setMilliseconds(1);
7
8 var oldValue = d.getMilliseconds();
9
10 d.setHours(8);
11 shouldBe("d.getMilliseconds()", oldValue.toString());
12 d.setHours(8, 30);
13 shouldBe("d.getMilliseconds()", oldValue.toString());
14 d.setHours(8, 30, 40);
15 shouldBe("d.getMilliseconds()", oldValue.toString());
16 d.setMinutes(45);
17 shouldBe("d.getMilliseconds()", oldValue.toString());
18 d.setMinutes(45, 40);
19 shouldBe("d.getMilliseconds()", oldValue.toString());
20 d.setSeconds(50);
21 shouldBe("d.getMilliseconds()", oldValue.toString());
OLDNEW
« no previous file with comments | « LayoutTests/fast/js/script-tests/date-negative-setmonth.js ('k') | LayoutTests/fast/js/script-tests/date-toisostring.js » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698