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

render: function() {
          return React.createElement('BR', null);
        },
      });
      var returnedValue = ReactDOMServer.renderToString(<Container/>);
      expect(returnedValue).not.toContain('</BR>');
    });
    it('should warn against children for void elements', function() {
      var container = document.createElement('div');
      expect(function() {
        ReactDOM.render(<input>children</input>, container);
      }).toThrow(
        'input is a void element tag and must not have `children` or ' +
        'use `props.dangerouslySetInnerHTML`.'
      );
    });
    it('should warn against dangerouslySetInnerHTML for void elements', function() {
      var container = document.createElement('div');
      expect(function() {
        ReactDOM.render(
          <input dangerouslySetInnerHTML={{__html: 'content'}} />,
          container
        );
      }).toThrow(
        'input is a void element tag and must not have `children` or use ' +
        '`props.dangerouslySetInnerHTML`.'
      );
    });
    it('should treat menuitem as a void element but still create the closing tag', function() {
      var container = document.createElement('div');