| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The deprecation message for synchronous XHR references the XHR spec over
HTTP, even though there is an HTTPS version. This updates that
reference and all the relevant test expectations.
BUG=546043
R=ojan@chromium.org
Review URL: https://codereview.chromium.org/1411843003
Cr-Commit-Position: refs/heads/master@{#355373}
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This CL shows a message in developer tools console, warning that the sync xhr may
hamper responsiveness.
This was shown as per the spec suggestion: https://xhr.spec.whatwg.org/#sync-warning
BUG=392311
Review URL: https://codereview.chromium.org/585873002
git-svn-id: svn://svn.chromium.org/blink/trunk@184788 bbb929c8-8fbe-4397-9dbb-9b2b20218538
|
|
|
https://bugs.webkit.org/show_bug.cgi?id=40996
Progress event should not be fired during synchronous XMLHttpRequest
https://bugs.webkit.org/show_bug.cgi?id=17502
Assertion failure when trying to restart a sync XMLHttpRequest as an async one from onreadystatechange
Tests: http/tests/xmlhttprequest/xmlhttprequest-sync-no-progress-events.html
http/tests/xmlhttprequest/xmlhttprequest-sync-vs-async-assertion-failure.html
* xml/XMLHttpRequest.cpp:
(WebCore::XMLHttpRequest::callReadyStateChangeListener): We now only dispatch readystatechange
event for synchronous requests in states UNSENT, OPENED and DONE. I'm not sure what exactly
the spec draft says about readystatechange for sync requests, but this seems to be the most
logical and backwards compatible behavior.
(WebCore::XMLHttpRequest::didReceiveData): Don't dispatch progress events for sync requests.
Note that we already don't dispatch upload progress events for those.
git-svn-id: svn://svn.chromium.org/blink/trunk@63680 bbb929c8-8fbe-4397-9dbb-9b2b20218538
|
