#### 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('foo');
      expect(node.getAttribute('value')).toBe('');
      
    });
  });
  describe('checked inputs without a value property', function() {
    
    
    
    
    it('does not add "on" in absence of value on a checkbox', function() {
      const container = document.createElement('div');
      ReactDOM.render(
        <input type="checkbox" defaultChecked={true} />,
        container,
      );
      const node = container.firstChild;
      expect(node.value).toBe('on');
      expect(node.hasAttribute('value')).toBe(false);
    });
    it('does not add "on" in absence of value on a radio', function() {
      const container = document.createElement('div');
      ReactDOM.render(<input type="radio" defaultChecked={true} />, container);
      const node = container.firstChild;
      expect(node.value).toBe('on');
      expect(node.hasAttribute('value')).toBe(false);
    });
  });
});