<!--
  Note: if the issue is about documentation or the website, please file it at:
  https://github.com/reactjs/reactjs.org/issues/new
-->

**Do you want to request a *feature* or report a *bug*?**

Bug

**What is the current behavior?**

See fiddle https://jsfiddle.net/j2nzg31L/1/

The warning related to the select fires repeatedly.  @gaearon tells me it should dedupe, and that this is a bug.

**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template for React 16: https://jsfiddle.net/Luktwrdm/, template for React 15: https://jsfiddle.net/hmbg7e9w/).**

See above

**What is the expected behavior?**

See above

**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**

16.2
</select>,
    );
    if (__DEV__) {
      expect(console.error.calls.argsFor(0)[0]).toContain(
        '`value` prop on `select` should not be null. ' +
          'Consider using an empty string to clear the component or `undefined` ' +
          'for uncontrolled components.',
      );
    }
    ReactTestUtils.renderIntoDocument(
      <select value={null}>
        <option value="test" />
      </select>,
    );
    if (__DEV__) {
      expect(console.error.calls.count()).toBe(1);
    }
  });
  it('should warn if value is null and multiple is true', () => {
    spyOnDev(console, 'error');
    ReactTestUtils.renderIntoDocument(
      <select value={null} multiple={true}>
        <option value="test" />
      </select>,
    );
    if (__DEV__) {
      expect(console.error.calls.count()).toBe(1);
      expect(console.error.calls.argsFor(0)[0]).toContain(
        '`value` prop on `select` should not be null. ' +
          'Consider using an empty array when `multiple` is ' +