Add explanation of loose type checks in value assignment.

Author: nhunzaker

src/renderers/dom/client/wrappers/ReactDOMInput.js

@@ -199,8 +199,9 @@ var ReactDOMInput = {
     var node = ReactDOMComponentTree.getNodeFromInstance(inst);
     var value = LinkedValueUtils.getValue(props);
     if (value != null) {
-      // To avoid side effects (such as losing text selection), only set value if changed
-      if (value != node.value) {
+      // Use loose coercion to prevent replacement on comparisons like
+      // '3e1' == 30 in Chrome (~52).
+      if (value != node.value) { // eslint-disable-line
         // Cast `value` to a string to ensure the value is set correctly. While
         // browsers typically do this as necessary, jsdom doesn't.
         node.value = '' + value;

src/renderers/dom/shared/DOMPropertyOperations.js

@@ -159,7 +159,9 @@ var DOMPropertyOperations = {
                    (propertyInfo.hasOverloadedBooleanValue && value === true)) {
           node.setAttribute(attributeName, '');
         } else if (attributeName === 'value' && node.hasAttribute('value')) {
-          if (node.value != value) {
+          // Use loose coercion to prevent replacement on comparisons like
+          // '3e1' == 30 in Chrome (~52).
+          if (node.value != value) { // eslint-disable-line
             node.setAttribute(attributeName, '' + value);
           }
         } else {