[Webkit-unassigned] [Bug 125840] Have XHR.getResponseHeader() return null in initial ready states
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Jan 9 10:58:10 PST 2014
https://bugs.webkit.org/show_bug.cgi?id=125840
--- Comment #15 from Alexey Proskuryakov <ap at webkit.org> 2014-01-09 10:55:53 PST ---
(From update of attachment 219634)
View in context: https://bugs.webkit.org/attachment.cgi?id=219634&action=review
> Source/WebCore/ChangeLog:3
> + Have XHR.getResponseHeader() return null in initial ready states
Here and in the bug title, please mention getAllResponseHeaders as well.
> Source/WebCore/ChangeLog:8
> + Merging https://chromium.googlesource.com/chromium/blink/+/d201caf874a0bd6f101f517462b3cf1d8c5fce3d
What do other browsers do? The spec changed many times over the last few years, and it can't be taken very seriously.
> Source/WebCore/xml/XMLHttpRequest.cpp:1013
> + if (m_state < HEADERS_RECEIVED || m_error)
Why was "|| m_error" added here? This is not mentioned in ChangeLog.
If this is a behavior change, it should be landed in a separate patch to facilitate regression testing when a site breaks. If there is no behavior change, why is the code changed? I'm not sure if there is any test coverage for this.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list