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?
expect(node.hasAttribute('href')).toBe(false);
      });
      it('should not add an empty action attribute', () => {
        const container = document.createElement('div');
        expect(() => ReactDOM.render(<form action="" />, container)).toErrorDev(
          'An empty string ("") was passed to the action attribute. ' +
            'To fix this, either do not render the element at all ' +
            'or pass null to action instead of an empty string.',
        );
        const node = container.firstChild;
        expect(node.hasAttribute('action')).toBe(false);
        ReactDOM.render(<form action="abc" />, container);
        expect(node.hasAttribute('action')).toBe(true);
        expect(() => ReactDOM.render(<form action="" />, container)).toErrorDev(
          'An empty string ("") was passed to the action attribute. ' +
            'To fix this, either do not render the element at all ' +
            'or pass null to action instead of an empty string.',
        );
        expect(node.hasAttribute('action')).toBe(false);
      });
      it('should not add an empty formAction attribute', () => {
        const container = document.createElement('div');
        expect(() =>
          ReactDOM.render(<button formAction="" />, container),
        ).toErrorDev(
          'An empty string ("") was passed to the formAction attribute. ' +
            'To fix this, either do not render the element at all ' +
            'or pass null to formAction instead of an empty string.',
        );
        const node = container.firstChild;