It is also not working properly on Chrome Dev 68.0.3425.0 for Android 8.

gcast framework registers google-cast-button with the old API, document.registerElement().  So you can create it only with the old syntax, document.createElement('button', 'google-cast-button').

The standard syntax supports only elements registered by window.customElements.define().

So when will this upgrade and follow the updated API instead of the ancient one? As I said, it is causing problems when other libraries presume that the standard syntax works in all 'is' cases?

Route to cast team.

Context: I'm writing a PWA music player app (in react and material-ui) and would like to have the cast button on the screen rather than having the user route through the settings on Google Home. Currently I have to hack around react using the {is: } syntax by creating the button myself, and in doing so, I can't get material-ui to style it correctly so I have to hack that aspect as well.

Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 17.10 using chrome reported version #66.0.3359.139 and latest canary #68.0.3431.0.
This is a non-regression issue as it is observed from M60 old builds. 

Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!

We'll file an internal bug against the relevant team to follow up.  Thanks for the report.

For those hitting this as well, my workaround approach is to have a ChromecastButton component that just renders a normal button inside a div with what classNames I want, then

  componentDidMount() {
      const button = this.myRef.current.firstChild;
      // const castButton = document.createElement('button', {is: 'google-cast-button'});
      // SHOULD work, but doesn't.
      const castButton = document.createElement('button', 'google-cast-button');
      castButton.className = button.className;
      this.myRef.current.replaceChild(castButton, button);
  }

that takes the button and swaps it out with the newly created cast button that works. you generally shouldn't need your own event handlers on the button to swap out because the whole point is to have google-cast-button just magically do it all for you. if needed, you can swap out style attribute as well.

We've been able to reproduce the issue and will be releasing an update for the Cast Web Sender SDK soon along with updates in the documentation.

neosapien@: Please update this issue when the new sender SDK has been merged into M68.

We've just added a new launcher element consistent with the new webcomponent syntax. <google-cast-launcher></google-cast-launcher> or document.createElement('google-cast-launcher')

The old button will still work but if you're using react or the new custom element syntax you can use the new element. We will update the developer docs to reflect this change.

already working for me (including in react). thanks.