1. 15 Dec, 2016 1 commit
  2. 14 Dec, 2016 1 commit
  3. 13 Dec, 2016 1 commit
  4. 12 Dec, 2016 2 commits
  5. 16 Nov, 2016 2 commits
  6. 15 Nov, 2016 1 commit
  7. 07 Nov, 2016 1 commit
  8. 21 Oct, 2016 1 commit
  9. 17 Oct, 2016 1 commit
  10. 22 Sep, 2016 1 commit
    • jochen's avatar
      Make sure to use the correct context for eval checks · d008b9ef
      jochen authored
      We can't assume that there's no entered context during microtask
      execution. We also can't assume that we'll never enter an context during
      microtask execution either.
      
      We can however assume that we don't execute microtasks recursively, so
      remembering the length of the entered context stack is enough to decide
      which context to use.
      
      BUG=chromium:635769
      R=verwaest@chromium.org
      
      Review-Url: https://codereview.chromium.org/2350933007
      Cr-Commit-Position: refs/heads/master@{#39627}
      d008b9ef
  11. 19 Aug, 2016 1 commit
  12. 03 Aug, 2016 1 commit
    • jochen's avatar
      Do an access check before compiling code via eval() · 2f8d4f44
      jochen authored
      Similarly to how we check whether the entered context has access to the target
      context when invoking the function constructor, we should check the involved
      contexts before invoking eval().
      
      I forgot to add this in the initial CL that adds the check for the function
      constructor. Move the code to a common location, and use it for the GlobalEval
      builtin as well.
      
      BUG=chromium:541703
      R=verwaest@chromium.org
      
      Review-Url: https://codereview.chromium.org/2199343002
      Cr-Commit-Position: refs/heads/master@{#38277}
      2f8d4f44
  13. 27 Jul, 2016 1 commit
  14. 25 Jul, 2016 2 commits
  15. 20 Jul, 2016 3 commits
  16. 19 Jul, 2016 3 commits
  17. 18 Jul, 2016 5 commits
  18. 15 Jul, 2016 1 commit
  19. 14 Jul, 2016 7 commits
  20. 13 Jul, 2016 2 commits
  21. 12 Jul, 2016 1 commit
  22. 11 Jul, 2016 1 commit