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?
if (
          !dontWarnCustomElement &&
          nextProp !== serverValue &&
          !isMismatchDueToBadCasing
        ) {
          warnForPropDifference(propKey, serverValue, nextProp);
        }
      }
    }
  }
  if (__DEV__) {
    if (shouldWarnDev) {
      if (
        
        extraAttributeNames.size > 0 &&
        rawProps[SUPPRESS_HYDRATION_WARNING] !== true
      ) {
        
        warnForExtraAttributes(extraAttributeNames);
      }
    }
  }
  switch (tag) {
    case 'input':
      
      
      track((domElement: any));
      ReactDOMInputPostMountWrapper(domElement, rawProps, true);
      break;
    case 'textarea':