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?
ReactDOM.render(<div style={styles} />, container);
      styles = {display: 'block'};
      const stubStyle = container.firstChild.style;
      ReactDOM.render(<div style={styles} />, container);
      expect(stubStyle.display).toEqual('block');
      ReactDOM.render(<div style={null} />, container);
      expect(stubStyle.display).toEqual('');
      ReactDOM.render(<div style={styles} />, container);
      expect(stubStyle.display).toEqual('block');
      ReactDOM.render(<div style={null} />, container);
      expect(stubStyle.display).toEqual('');
    });
    it('should allow named slot projection on both web components and regular DOM elements', () => {
      const container = document.createElement('div');
      ReactDOM.render(
        <my-component>
          <my-second-component slot="first" />
          <button slot="second">Hello</button>
        </my-component>,
        container,
      );
      const lightDOM = container.firstChild.childNodes;
      expect(lightDOM[0].getAttribute('slot')).toBe('first');
      expect(lightDOM[1].getAttribute('slot')).toBe('second');
    });
    it('should skip reserved props on web components', () => {
      const container = document.createElement('div');
      ReactDOM.render(
        <my-component
          children={['foo']}