Could you provide some details about what website used to work, but doesn't now?

Could you also provide the steps you performed, what happened, and then what you expected to happen?

I thought that answer will be "We disabled it becouse of ... (some
reason)", thats why i didn't add more information and test steps.

So here is test steps:
1. Open http://infinitybit.net/cast_example/index.html in Chrome (desktop).
2. If you have chromecast, in textarea you will see:
"init success"
"receiver found"
2. Click "launch app", and chrome extension will appears.
3. After that you will be able to cast video to chromecast.

Lets try it on Chrome for iOS:
1. Open http://infinitybit.net/cast_example/index.html in Chrome iOS (my
device is: iPhone 6s, iOS 9.3.2)
2. Nothig will appears in textarea
3. Click "launch app", and you will see "launching app..."... and nothing
will be nothing happens
4. You cannot cast anything via Chrome for iOS

It is broken for over an year. For exaple here is a questin on stackoweflow:
http://stackoverflow.com/questions/38579912/chromecast-sender-app-on-chrome-mobile-receiverlistener-doesnt-get-called

and here is a screenshot:
https://dl.dropboxusercontent.com/u/934782/chromecastios.png

Hi

Cast is still supported on Chrome for iOS (you can test it on Youtube and cast your video).


The initialization of the cast device must be done with using __onGCastApiAvailable API as presented on the cast web site: https://developers.google.com/cast/docs/chrome_sender

Initialization

To determine if the API is available and initialize it, you can provide the callback function window['__onGCastApiAvailable'] before the Cast API loads. It is invoked with loaded == true if the API loads, or with errorInfo when load fails.


The legacy way (test chrome.cast.isAvailable) cannot work on Chrome for iOS at the moment (compatibility issue with the WKWebView renderer).
Unfortunately, infinitybit example uses the legacy init.

Sorry for the inconvenience.