Testling should specify the encoding when serving the page/bundle. #34

Open
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants
@robotlolita

Since Testling didn't specify the charset, this led to a plethora of random encoding errors if the libraries used anything outside of the ASCII charset. The same code would work or not on browsers with the same capabilities depending on whether the browser decided to treat the page as UTF-8 or not.

Specifying the charset gets rid of all that and gives us predictable behaviours. Yay

Specify the charset as UTF-8.
Since Testling didn't specify the charset, this led to a plethora of random encoding errors if the libraries used anything outside of the ASCII charset. The same code would work or not on browsers with the same capabilities depending on whether the browser decided to treat the page as UTF-8 or not.

Specifying the charset gets rid of all that and gives us predictable behaviours. Yay
@ljharb

This comment has been minimized.

Show comment Hide comment
@ljharb

ljharb May 4, 2013

+1, this will help!

ljharb commented May 4, 2013

+1, this will help!

@pid pid referenced this pull request in pid/speakingurl May 29, 2013

Closed

add tests; browser #9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment