1. 20 Oct, 2016 1 commit
  2. 22 Sep, 2016 1 commit
  3. 18 Jul, 2016 1 commit
  4. 07 Jun, 2016 1 commit
  5. 10 Sep, 2015 1 commit
  6. 01 Sep, 2015 1 commit
  7. 13 Jul, 2015 1 commit
  8. 18 May, 2015 2 commits
  9. 06 May, 2015 1 commit
  10. 02 Apr, 2015 1 commit
  11. 18 Mar, 2015 1 commit
  12. 15 Jan, 2015 2 commits
  13. 12 Jan, 2015 5 commits
  14. 06 Jan, 2015 1 commit
  15. 13 Dec, 2014 1 commit
  16. 11 Dec, 2014 1 commit
  17. 06 Nov, 2014 1 commit
  18. 16 Sep, 2014 1 commit
  19. 26 Aug, 2014 1 commit
  20. 22 Aug, 2014 1 commit
  21. 21 Aug, 2014 1 commit
    • Fix Studio to gracefully handle xblock JavaScript errors · d451c3e9
      TNL-46
      
      I've changed Studio to catch JavaScript errors when rendering xblocks, log the error, but to then continue as normal. This means that the user is still able to interact with the xblock to delete, duplicate etc. This seems reasonable as the xblock is only rendered as a WYSIWYG representation so if it isn't fully interactive that shouldn't be a big problem.
      Andy Armstrong committed
  22. 19 Aug, 2014 1 commit
  23. 16 Aug, 2014 1 commit
  24. 11 Aug, 2014 1 commit
  25. 07 Aug, 2014 10 commits