#### Type
`inconsistency` for common use cases.
`bug` for projects relying on correct DOM emissions.

#### Description
It's unclear to me if the following is a known issue or not.
Take in consideration the snippet below:
```jsx
<input type="checkbox" defaultChecked={true} />
```
#### Current Behavior
Setting the `defaultValue` prop on inputs of other types sets both the `value` and `defaultValue` attribute on the DOM element.

When setting the `defaultChecked` prop on inputs of type `checkbox` only the `checked` attribute is correctly set, leaving the `defaultChecked` attribute unchanged.

#### Expected Behaviour
Like mentioned above, the expected behavior would be for the `defaultChecked` prop to set both the `checked` and `defaultChecked` attributes on the corresponding DOM node (like it's the case with the `defaultValue` prop).

);
    expect(node.value).toBe('0');
    ReactDOM.render(<input type="text" defaultValue="1" />, container);
    expect(node.value).toBe('0');
    expect(node.defaultValue).toBe('1');
  });
  it('should update `defaultValue` for uncontrolled date/time input', () => {
    const container = document.createElement('div');
    const node = ReactDOM.render(
      <input type="date" defaultValue="1980-01-01" />,
      container,
    );
    expect(node.value).toBe('1980-01-01');
    ReactDOM.render(<input type="date" defaultValue="2000-01-01" />, container);
    expect(node.value).toBe('1980-01-01');
    expect(node.defaultValue).toBe('2000-01-01');
    ReactDOM.render(<input type="date" />, container);
  });
  it('should take `defaultValue` when changing to uncontrolled input', () => {
    const container = document.createElement('div');
    const node = ReactDOM.render(
      <input type="text" value="0" readOnly="true" />,
      container,
    );
    expect(node.value).toBe('0');
    expect(() =>
      ReactDOM.render(<input type="text" defaultValue="1" />, container),
    ).toWarnDev(
      'A component is changing a controlled input of type ' +
        'text to be uncontrolled.',