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(console.log.calls.argsFor(0)[0]).toContain('onError called');
        expect(console.log.calls.argsFor(1)[0]).toContain('onLoad called');
      }
    });
    it('should receive a load event on <link> elements', () => {
      const container = document.createElement('div');
      const onLoad = jest.fn();
      ReactDOM.render(
        <link href="http://example.org/link" onLoad={onLoad} />,
        container,
      );
      const loadEvent = document.createEvent('Event');
      const link = container.getElementsByTagName('link')[0];
      loadEvent.initEvent('load', false, false);
      link.dispatchEvent(loadEvent);
      expect(onLoad).toHaveBeenCalledTimes(1);
    });
    it('should receive an error event on <link> elements', () => {
      const container = document.createElement('div');
      const onError = jest.fn();
      ReactDOM.render(
        <link href="http://example.org/link" onError={onError} />,
        container,
      );
      const errorEvent = document.createEvent('Event');
      const link = container.getElementsByTagName('link')[0];
      errorEvent.initEvent('error', false, false);
      link.dispatchEvent(errorEvent);
      expect(onError).toHaveBeenCalledTimes(1);
    });