Now that #1510 has landed we still have one final issue to fix (ironically, the initial reason for #1510). https://github.com/facebook/react/pull/1510#issuecomment-170229012 + https://github.com/facebook/react/pull/1510#issuecomment-170229162, the problem being that `value` is managed as a property for the purpose of `<input>`, but `<progress>` requires it to be an attribute so that the attribute is correctly removed when null.

As discussed in the second comment, it seems to me that the right approach here is to actually remove all the special property logic from DOMPropertyOperations and instead implement it in the appropriate wrappers instead (ReactDOMInput, etc).

Repro: http://jsfiddle.net/670u7ure/8/
Original issue: https://github.com/facebook/react/issues/1431

cc @jimfb, @spicyj

* All rights reserved.
 *
 * This source code is licensed under the BSD-style license found in the
 * LICENSE file in the root directory of this source tree. An additional grant
 * of patent rights can be found in the PATENTS file in the same directory.
 *
 * @emails react-core
 */
'use strict';
var emptyFunction = require('emptyFunction');
describe('ReactDOMTextarea', function() {
  var React;
  var ReactDOM;
  var ReactLink;
  var ReactTestUtils;
  var renderTextarea;
  beforeEach(function() {
    React = require('React');
    ReactDOM = require('ReactDOM');
    ReactLink = require('ReactLink');
    ReactTestUtils = require('ReactTestUtils');
    renderTextarea = function(component, container) {
      if (!container) {
        container = document.createElement('div');
      }
      var stub = ReactDOM.render(component, container);
      var node = ReactDOM.findDOMNode(stub);
      
      
      node.value = node.innerHTML.replace(/^\n/, '');