1. 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
  2. 12 Jul, 2017 1 commit
  3. 17 Apr, 2017 1 commit
  4. 19 Dec, 2016 1 commit
  5. 15 Sep, 2016 1 commit
  6. 06 Sep, 2016 1 commit
  7. 17 Aug, 2016 1 commit
  8. 27 May, 2016 1 commit
  9. 12 May, 2016 1 commit
  10. 12 Dec, 2015 1 commit
  11. 08 Dec, 2015 1 commit
  12. 23 Jul, 2014 2 commits
  13. 01 Apr, 2014 3 commits
  14. 11 Oct, 2013 1 commit
  15. 10 Oct, 2013 2 commits
  16. 01 Aug, 2013 1 commit
  17. 10 Jul, 2013 1 commit