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 (expectedStyle !== serverValue) {
            warnForPropDifference(propKey, serverValue, expectedStyle);
          }
        }
      } else if (
        enableCustomElementPropertySupport &&
        isCustomComponentTag &&
        (propKey === 'offsetParent' ||
          propKey === 'offsetTop' ||
          propKey === 'offsetLeft' ||
          propKey === 'offsetWidth' ||
          propKey === 'offsetHeight' ||
          propKey === 'isContentEditable' ||
          propKey === 'outerText' ||
          propKey === 'outerHTML')
      ) {
        
        extraAttributeNames.delete(propKey.toLowerCase());
        if (__DEV__) {
          console.error(
            'Assignment to read-only property will result in a no-op: `%s`',
            propKey,
          );
        }
      } else if (isCustomComponentTag && !enableCustomElementPropertySupport) {
        
        extraAttributeNames.delete(propKey.toLowerCase());
        serverValue = getValueForAttribute(domElement, propKey, nextProp);
        if (nextProp !== serverValue) {
          warnForPropDifference(propKey, serverValue, nextProp);