- From: Michael[tm] Smith <notifications@github.com>
- Date: Wed, 06 Feb 2019 19:56:19 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 7 February 2019 03:56:40 UTC
As the bug reporter for https://bugs.chromium.org/p/chromium/issues/detail?id=775438, I think the explanation is great and aligns spot-on with the actual real-world problem cases I'm aware of where people have run into this in the wild (e.g., frustrated web developers posting to Stack Overflow who are baffled by the difference in browser behavior on this between Firefox and Chrome. So I agree we should update the spec such that we can have all implementations aligned on this ー to have agreement among implementors on the processing requirements, and spec text which leaves no doubts about what those requirements are. So, thanks much for taking time to raise this. -- 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/fetch/issues/869#issuecomment-461280147
Received on Thursday, 7 February 2019 03:56:40 UTC