- From: claskfosmic <notifications@github.com>
- Date: Mon, 31 Jul 2017 23:43:43 +0000 (UTC)
- To: whatwg/xhr <xhr@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 31 July 2017 23:44:08 UTC
As reporter in the Google Group (thanks for bringing it up here @foolip), I would like to ask a little attention here too. In our application, we use a literal comparison based on the header field names in the response. After this change in Chrome 60, we're now converting all header field name to lowercase, because other browsers still leave it untouched, in order to make it work. So, after a long fight against Internet Explorer, we're back in a situation where various browsers respond differently to the same functions... I do not think we want to go there! I agree it's nice to do lowercasing, but as @cpuy notes, as a developer, you would expect the XHR-function to be stable, to prevent applications from breaking down all of a sudden... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/xhr/issues/146#issuecomment-319227271
Received on Monday, 31 July 2017 23:44:08 UTC