When setting boolean attributes on Web Components
`<x-search somebool name={this.props.name} />`
they get rendered as attribute/value pairs instead
`<x-search somebool="true" name={this.props.name}>`

This causes problems with some AMP components, for eg. `<amp-iframe />` which has a `resizable` attribute that gets rendered as `resizable="true"`. This results in non valid AMP content and developers crying with blood tears on their keyboards :)
> The attribute 'resizable' in tag 'amp-iframe' is set to the invalid value 'true'. (see https://www.ampproject.org/docs/reference/components/amp-iframe)

Is there any reason for the current behaviour? Will changing this break something else?
customElement.foo = null;
      
      ReactDOM.render(<my-custom-element foo={true} />, container);
      expect(customElement.foo).toBe(true);
      ReactDOM.render(<my-custom-element foo="bar" />, container);
      expect(customElement.foo).toBe('bar');
      
      ReactDOM.render(<my-custom-element foo={false} />, container);
      expect(customElement.foo).toBe(false);
      ReactDOM.render(<my-custom-element foo="bar" />, container);
      expect(customElement.foo).toBe('bar');
      
      ReactDOM.render(<my-custom-element foo={true} />, container);
      expect(customElement.foo).toBe(true);
      ReactDOM.render(<my-custom-element foo={null} />, container);
      expect(customElement.foo).toBe(null);
      
      ReactDOM.render(<my-custom-element foo={false} />, container);
      expect(customElement.foo).toBe(false);
      ReactDOM.render(<my-custom-element foo={null} />, container);
      expect(customElement.foo).toBe(null);
    });
    
    it('custom element custom event handlers assign multiple types', () => {
      const container = document.createElement('div');
      document.body.appendChild(container);
      const oncustomevent = jest.fn();
      
      ReactDOM.render(<my-custom-element oncustomevent={'foo'} />, container);
      const customelement = container.querySelector('my-custom-element');