gitweb.js: No need for loop in blame_incremental's handleResponse()

JavaScript is single-threaded, so there is no need for protecting
against changes to XMLHttpRequest object behind event handler back.

Therefore there is no need for loop that was here in case `xhr' got
new changes while processing current changes.  This should make code a
bit more clear.

Signed-off-by: Jakub Narebski <redacted>
Signed-off-by: Junio C Hamano <redacted>

diff --git a/static/js/blame_incremental.js b/static/js/blame_incremental.js
index 22ed9bf908134ddabe12fee5c518370d48d1b6c3310ee0e521729bfd7d988b69..9040fbca71b5f1eebfaf416f4536ecf7fe1b12b74945a4975fef03b0e6be33e5 100644 (file)
--- a/static/js/blame_incremental.js
+++ b/static/js/blame_incremental.js
@@ -603,21 +603,16 @@ function handleResponse() {
                return;
        }
 
-       // extract new whole (complete) lines, and process them
-       while (xhr.prevDataLength !== xhr.responseText.length) {
-               if (xhr.readyState === 4 &&
-                   xhr.prevDataLength === xhr.responseText.length) {
-                       break;
-               }
 
+       // extract new whole (complete) lines, and process them
+       if (xhr.prevDataLength !== xhr.responseText.length) {
                xhr.prevDataLength = xhr.responseText.length;
                var unprocessed = xhr.responseText.substring(xhr.nextReadPos);
                xhr.nextReadPos = processData(unprocessed, xhr.nextReadPos);
-       } // end while
+       }
 
        // did we finish work?
-       if (xhr.readyState === 4 &&
-           xhr.prevDataLength === xhr.responseText.length) {
+       if (xhr.readyState === 4) {
                responseLoaded(xhr);
        }
 }