Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
I have discussed this in the past with @domenic. He seems to think all requests/responses should default to `text/javascript` Unfortunately...ALL(?) browsers seem to request JS with `application/javascript` And in response servers respond with `application/javascript` In order to abide by his convention we need to update a myriad of libraries in Ruby AND Javascript for these tests to pass. Pros: Luckily most browsers and servers are "broken" therefore our "false positives" with `application/javascript` work. ¯\_(ツ)_/¯ Cons: If only one extension related per mime there will be blood! Although `text/javascript` may be more correct... the web (as we know it) still uses `application/javascript` convention. See References: - #164 Next steps: Determine if issue needs to be created in WHATWG HTML / DOM / Fetch ¯\_(ツ)_/¯ This will be the only way we can get user land mime libraries updated without an IETF (pending) blessing for `text/javascript`. /cc @tmornini @brandondees
- Loading branch information