- 25 Aug, 2016 1 commit
-
-
Sean McGivern authored
These can't be resolved in the UI because if they aren't in a UTF-8 compatible encoding, they can't be rendered as JSON. Even if they could, we would be implicitly changing the file encoding anyway, which seems like a bad idea.
-
- 17 Aug, 2016 1 commit
-
-
Sean McGivern authored
These JS errors are only thrown in PhantomJS, and enough of the page is rendered properly that this spec passes. We should remove this in future.
-
- 12 Aug, 2016 2 commits
-
-
Fatih Acet authored
-
Sean McGivern authored
-