Run the [`fixtures/ssr` test harness](https://github.com/facebook/react/tree/master/fixtures/ssr). In the terminal, the following warning is logged:

```
Warning: Unknown prop `onClick` on <a> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
  in a (at Page.js:12)
  in p (at Page.js:18)
  in div (at Page.js:17)
  in Page (at App.js:12)
  in div (at App.js:10)
  in body (at Chrome.js:17)
  in html (at Chrome.js:9)
  in Chrome (at App.js:9)
  in App (at render.js:18)
```

SSR behavior should match client-side behavior and not warn for a valid attribute.
expect(e.getAttribute('download')).toBe('false');
      });
      itRenders('download prop with string "true" value', async render => {
        const e = await render(<a download={'true'} />);
        expect(e.getAttribute('download')).toBe('true');
      });
      itRenders('download prop with number 0 value', async render => {
        const e = await render(<a download={0} />);
        expect(e.getAttribute('download')).toBe('0');
      });
      itRenders('no download prop with null value', async render => {
        const e = await render(<div download={null} />);
        expect(e.hasAttribute('download')).toBe(false);
      });
      itRenders('no download prop with undefined value', async render => {
        const e = await render(<div download={undefined} />);
        expect(e.hasAttribute('download')).toBe(false);
      });
    });
    describe('className property', function() {
      itRenders('className prop with string value', async render => {
        const e = await render(<div className="myClassName" />);
        expect(e.getAttribute('class')).toBe('myClassName');
      });
      itRenders('className prop with empty string value', async render => {
        const e = await render(<div className="" />);
        expect(e.getAttribute('class')).toBe('');
      });
      
      itRenders('className prop with true value', async render => {