Update the version history for 1.3.1

Author: smfr

MotionMark/about.html

@@ -72,8 +72,15 @@ <h1>About MotionMark <span class="version"></span></h1>
             <p id="set-display-fps">The MotionMark benchmark relies on the requestAnimationFrame() JavaScript API, which provides callbacks at a consistent frequency related to screen refresh rate. However, browsers have made different choices about whether requestAnimationFrame() should strictly follow screen refresh rate. Safari currently fires requestAnimationFrame() callbacks at 60Hz on 120Hz screens, while other browsers fire it at 120Hz. This affects the benchmark score, so to compare browser scores across browsers, be sure to set the screen refresh rate to 60Hz (for example on macOS, this can be done in the Displays panel in System Settings).</p>
 
             <h3>Version history</h3>
-
             <ul id="log">
+                <li><strong>1.3.1</strong>: 
+                    <ul>
+                        <li><a href="https://github.com/WebKit/MotionMark/commit/c5f2326e9a982cd0d6c8bc15320020ac57147156">Increase the max complexity of the Multiply subtest</a></li>
+                        <li><a href="https://github.com/WebKit/MotionMark/commit/f3034d6f7754eefcebd5df76657082344fc629ee">When a subtest hits maximum complexity, make its reported score be the maximum score.</a></li>
+                        <li><a href="https://github.com/WebKit/MotionMark/commit/3f6115f9ea26fc74e723cb2eb55580dd93bac3d9">Ensure the stage is correctly sized when running from a URL with test parameters</a></li>
+                        <li><a href="https://github.com/WebKit/MotionMark/commit/f1c7edb54b8d5aaa47303a577487a0a6bbe0e144">Make frame rate detection more reliable</a></li>
+                    </ul>
+                </li>
                 <li><strong>1.3</strong>: 
                     <ul>
                         <li><a href="https://github.com/WebKit/MotionMark/commit/37c610115c8c3fae8a74a18305727064c1fd4edc">Ignore mutation frames when scoring</li>