Skip to content

V
V8
Switch branch/tag
  1. 27 Jul, 2022 1 commit
  3. 20 Nov, 2021 1 commit
  5. 27 May, 2021 1 commit
  7. 25 Jan, 2021 1 commit
  9. 09 Jul, 2020 1 commit
  11. 08 Jul, 2020 1 commit
  13. 12 Jun, 2020 1 commit
  15. 24 Apr, 2020 2 commits
  17. 31 Oct, 2019 1 commit
  19. 30 Oct, 2019 1 commit
  21. 11 Oct, 2019 1 commit
  23. 07 Oct, 2019 1 commit
  25. 01 Oct, 2019 1 commit
  27. 25 Sep, 2019 1 commit
  29. 12 Sep, 2019 1 commit
  31. 29 Apr, 2019 1 commit
  33. 19 Apr, 2019 1 commit
  35. 09 Apr, 2019 1 commit
  37. 24 Mar, 2019 1 commit
  39. 01 Feb, 2019 1 commit
  41. 25 Jan, 2019 1 commit
  43. 08 Jan, 2019 1 commit
  45. 03 Jan, 2019 1 commit
  47. 14 Dec, 2018 1 commit
  49. 12 Dec, 2018 1 commit
  51. 07 Dec, 2018 1 commit
  53. 01 Nov, 2018 1 commit
  55. 26 Sep, 2018 1 commit
  57. 14 Sep, 2018 1 commit
    • PhistucK's avatar
      [Intl] Rename dayperiod to dayPeriod · 53de7345
      PhistucK authored 
      Previously, DateTimeFormat.prototype.formatToParts returned an object
with the property key 'dayperiod' which is incorrect as per the spec.
This patch updates the property key to say 'dayPeriod', making this spec
compliant.

R=cira@chromium.org

Bug: chromium:865351
Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
Change-Id: I37f50797387bc69d5e29d7c2911bc5cc0fad37ac
Reviewed-on: https://chromium-review.googlesource.com/1145304Reviewed-by: 's avatarSathya Gunasekaran <gsathya@chromium.org>
Commit-Queue: PhistucK <phistuck@gmail.com>
Cr-Commit-Position: refs/heads/master@{#55922}
      53de7345
  59. 13 Sep, 2018 1 commit
  61. 04 Sep, 2018 1 commit
  63. 30 Aug, 2018 1 commit
  65. 02 Aug, 2018 1 commit
    • Jungshik Shin's avatar
      Accept Etc/GMT* as a valid time zone id. · 4343e1a9
      Jungshik Shin authored 
      Etc/GMT* time zones are  listed in the INAN time zone database and
they should be accepted as valid.

This CL will be followed by a CL for moving time zone name checks to C++
that will accept all the time zone names (e.g. EST5EDT, Hongkong, ROK, Zulu).

Bug: chromium:364374
Test: intl/date-format/timezone.js
Test: mjsunit/regress/regress-crbug-364374
Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng
Change-Id: If0e5327d7e980504a9cb3d2b641e907ebce61180
Reviewed-on: https://chromium-review.googlesource.com/1159546
Commit-Queue: Jungshik Shin <jshin@chromium.org>
Reviewed-by: 's avatarSathya Gunasekaran <gsathya@chromium.org>
Cr-Commit-Position: refs/heads/master@{#54879}
      4343e1a9
  67. 25 Apr, 2018 1 commit
  69. 21 Apr, 2018 1 commit
  71. 12 Apr, 2018 1 commit
  73. 27 Jan, 2018 1 commit
  75. 19 Oct, 2017 1 commit
    • Jungshik Shin's avatar
      Intl.DateTimeFormat: throw RangeError for non-finite input · 831bc233
      Jungshik Shin authored 
      intl.js throws an exception when datetime-value to format is
Infinity or NaN, but there was a way to thwart the check.

Moreover, intl.js and runtime-intl.cc have unnecessary conversions
of 'Number->Date->Number'. I removed the unnecessary conversion
and made 'Number' be passed to %InternalDateFormat.  With this
streamlining, the work-around mentioned above does not work
anymore.

Add a check in runtime_intl.cc for Infinity/NaN and throw a
RangeError.

Add invalid-time test for invalid datetime-values passed to
Intl.DateTimeFormat.format().

Bug: chromium:774833
Test: intl/date-format/invalid-time.js
Cq-Include-Trybots: master.tryserver.v8:v8_linux_noi18n_rel_ng
Change-Id: Idc575e532a86ee110dc4bb945ae023d6516650ee
Reviewed-on: https://chromium-review.googlesource.com/724860
Commit-Queue: Jungshik Shin <jshin@chromium.org>
Reviewed-by: 's avatarAdam Klein <adamk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#48765}
      831bc233
  77. 12 Jul, 2017 1 commit