Chromium Code Reviews| OLD | NEW |
|---|---|
| 1 // Copyright 2013 the V8 project authors. All rights reserved. | 1 // Copyright 2013 the V8 project authors. All rights reserved. |
| 2 // Redistribution and use in source and binary forms, with or without | 2 // Redistribution and use in source and binary forms, with or without |
| 3 // modification, are permitted provided that the following conditions are | 3 // modification, are permitted provided that the following conditions are |
| 4 // met: | 4 // met: |
| 5 // | 5 // |
| 6 // * Redistributions of source code must retain the above copyright | 6 // * Redistributions of source code must retain the above copyright |
| 7 // notice, this list of conditions and the following disclaimer. | 7 // notice, this list of conditions and the following disclaimer. |
| 8 // * Redistributions in binary form must reproduce the above | 8 // * Redistributions in binary form must reproduce the above |
| 9 // copyright notice, this list of conditions and the following | 9 // copyright notice, this list of conditions and the following |
| 10 // disclaimer in the documentation and/or other materials provided | 10 // disclaimer in the documentation and/or other materials provided |
| (...skipping 12 matching lines...) Expand all Loading... | |
| 23 // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY | 23 // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY |
| 24 // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT | 24 // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT |
| 25 // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE | 25 // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE |
| 26 // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. | 26 // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
| 27 | 27 |
| 28 // Testing v8Parse method for date and time pattern. | 28 // Testing v8Parse method for date and time pattern. |
| 29 // Month is represented as a short name. | 29 // Month is represented as a short name. |
| 30 | 30 |
| 31 var dtf = new Intl.DateTimeFormat(['en'], | 31 var dtf = new Intl.DateTimeFormat(['en'], |
| 32 {year: 'numeric', month: 'short', | 32 {year: 'numeric', month: 'short', |
| 33 day: 'numeric'}); | 33 day: 'numeric', |
| 34 timeZone: 'America/Los_Angeles'}); | |
| 34 | 35 |
| 35 // Make sure we have pattern we expect (may change in the future). | 36 // Make sure we have pattern we expect (may change in the future). |
| 36 assertEquals('MMM d, y', dtf.resolved.pattern); | 37 assertEquals('MMM d, y', dtf.resolved.pattern); |
| 37 | 38 |
| 38 assertEquals('Sat May 04 1974 00:00:00 GMT-0007 (PDT)', | 39 var date = dtf.v8Parse('Feb 4, 1974'); |
| 39 usePDT(String(dtf.v8Parse('May 4, 1974')))); | 40 assertEquals(1974, date.getFullYear()); |
|
mnita
2013/10/08 20:04:41
Should we go with UTC fields, for consistency?
| |
| 41 assertEquals(1, date.getMonth()); | |
| 42 assertEquals(4, date.getDate()); | |
| 40 | 43 |
| 41 // Missing , in the pattern. | 44 // Missing , in the pattern. |
| 42 assertEquals(undefined, dtf.v8Parse('May 4 1974')); | 45 assertEquals(undefined, dtf.v8Parse('Feb 4 1974')); |
| 43 | 46 |
| 44 // Extra "th" after 4 in the pattern. | 47 // Extra "th" after 4 in the pattern. |
| 45 assertEquals(undefined, dtf.v8Parse('May 4th, 1974')); | 48 assertEquals(undefined, dtf.v8Parse('Feb 4th, 1974')); |
| 46 | 49 |
| 47 // Wrong pattern. | 50 // Wrong pattern. |
| 48 assertEquals(undefined, dtf.v8Parse('5/4/1974')); | 51 assertEquals(undefined, dtf.v8Parse('2/4/1974')); |
| OLD | NEW |