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?
return new Promise(resolve => {
      if (forceHydrate) {
        act(() => {
          ReactDOM.hydrate(reactElement, domElement);
        });
      } else {
        act(() => {
          ReactDOM.render(reactElement, domElement);
        });
      }
      
      
      resolve();
    });
  }
  
  
  async function expectErrors(fn, count) {
    if (console.error.calls && console.error.calls.reset) {
      console.error.calls.reset();
    } else {
      
      
      spyOnDev(console, 'error');
    }