Browser and platform compatibility

[cofiem]

Catch-all issue for browser and platform compatibility. General idea is to test on different browser/platform combinations, report any bugs as issues, and reference them here.

• [x] #99 - browser version check on load (status: complete)
• [x] #140 - grid lines
• [ ] #138 - audio does not play in firefox (status: issues identified, fixes pending)
• [x] #123 - chrome for android v35 (status: closed, can't reproduce, possibly solved in later version of chrome)
• [ ] #159 - iOS audio playing bug (status: fixes pending. problem: byte-range requests not sending cookie)

The spreadsheet tracking some of these issues: https://docs.google.com/spreadsheets/d/10kaio839fLPJLLw7SVZ2do1zKih5nxA1c9XZlTgbPKw/edit#gid=0

[cofiem]

Audio currently does not play in mobile browsers. It is downloaded, the response does have content, but Android (Chrome and Firefox) and iPad (Safari) won't play the audio in the listen page or if the audio file is loaded directly. they will all play the file if it is requested directly through Apache, with HTTP headers very closely matching the problematic requests & responses.

The mobile browsers do not make Range requests.

[atruskie]

Range requests less important.

Have we got any reasons why the audio is not playing?

[cofiem]

No clear reasons why audio isn't playing. We tried serving a file directly through Apache from staging. That worked fine.

Possibilities:

• mobile browsers require interaction to play audio (although they don't play even when loading the audio file directly, and pressing play)
• HTTP headers (candidates for being part of the problem: Content-Disposition, Set-Cookie, Content-Transfer-Encoding, Connection, CORS (not likely), caching headers)