Problem with the order of processing arguments of function calls in the QML JavaScript engine

It looks like the JavaScript engine of QML apps contains a bug in the order in which it handles function arguments. The following code explains the issue:

    var i = 2;
    console.log(i, i += 2);
    // output in Chrome, Firefox: 2, 4
    // output in QML app:         4, 4 (WRONG?) 

It looks like the arguments for a function call are build up after processing each of the arguments, which goes wrong when an assignment operator changes a variable passed to the function itself earlier too.