1. 31 Oct, 2017 1 commit
    • Mathias Bynens's avatar
      [parser] Improve error message for `import()` · dbcea115
      Mathias Bynens authored
      Currently, dynamic `import()` throws the following SyntaxError when
      used without a specifier:
      
          > import();
          < Uncaught SyntaxError: Unexpected token )
      
      From the error message, it seems this the result of the code snippet
      being seen as static `import` followed by parens, as opposed to
      `import()` with no specifier.
      
      This patch makes this error message more clear:
      
          > import();
          < SyntaxError: import() requires a specifier
      
      BUG=v8:7020,v8:6513
      
      Change-Id: I3519dfd0029f38d23da858a5499f1d226e794935
      Reviewed-on: https://chromium-review.googlesource.com/747141Reviewed-by: 's avatarSathya Gunasekaran <gsathya@chromium.org>
      Commit-Queue: Mathias Bynens <mathias@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49058}
      dbcea115
  2. 26 Oct, 2017 1 commit
  3. 26 Oct, 2016 1 commit
  4. 21 Mar, 2016 1 commit
  5. 16 Mar, 2016 1 commit
  6. 02 Feb, 2016 1 commit
  7. 29 Jan, 2016 1 commit
    • littledan's avatar
      Fix Unicode string normalization with null bytes · f3e41d96
      littledan authored
      Previously, String.prototype.normalize constructed its ICU input
      string as a null-terminated string. This creates a bug for strings
      which contain a null byte, which is allowed in ECMAScript. This
      patch constructs the ICU string based on its length so that the
      entire string is normalized.
      
      R=jshin@chromium.org
      BUG=v8:4654
      LOG=Y
      
      Review URL: https://codereview.chromium.org/1645223003
      
      Cr-Commit-Position: refs/heads/master@{#33614}
      f3e41d96
  8. 04 Jan, 2016 1 commit