Not working for Me Uncaught TypeError

Hey mayne123,

We’ll look into this. Can you give me a URL to the site you are using this on and let me know the version of the browser you are using?

– Dan

Hey,

i forgot to write it happens on latest chrome beta
seems like safari works fine. But if i understand it correct you already integrated the chrome future into the plugin. I also tried to use just the javascript provided on roost, also doesnt working.

best

Ah! There we go. Makes complete sense now.

Integration with Chrome is not yet into the plugin or our public JS. Watch for an update in the next few days for both.

The reason this error is thrown is your browser and the plugin are in a mixed state.

If the browser can not receive push, we do not load the Roost script completely.

But since Chrome beta DOES support push, Roost JS loads, but the prompt function throws an error as the beta support is not there in the code.

Thus, what you are experiencing.

Thanks for the details. It clears the picture up.

Again, just watch over the next few days. This is going to get fun.

– Dan

We did push an update on our servers to resolve this issue. You should be good now. The updates to the plugin will also take this into context so that it will work as expected.

Im using the javascript version from your site but thanks for letting me know. Do you already know when the chrome integration is ready?

Hey Mayne123,

We released support for Chrome late last week!!! Boom!

The latest version of our plugin v2.3.2 supports Chrome (and has already been through a few bugfixes.)

Glad to answer questions if you have any. Let us know your thoughts!

hey thanks for the message i already noticed it.
But its just working with https and https is useless when you dont have any user data to protect + the speed loss of https is too high (caching etc.). ALso when your anayltics is correct then the click rate is really low even twitter or facebook have a higher click rate (and they suck both) ??

The HTTPS thing is a slight catch but one that we have no control over.

We had a question in another thread on this earlier. I’ll quote what I said there for ease so you don’t have to dig:

We wrote a post about this on our blog called Chrome Security – SSL Keeps You Safe. In the post we reference a post by Matt Gaunt, Google Developer Advocate, where he expands a bit more as to the why of the requirement. For brevity, here is his post: Push Notifications on the Open Web.

Re the CTR: This is something we are very focused on optimizing. We are limited with the Safari implementation as to the control we have for some things, but with Chrome have a whole new world of possibility. We are watching this closely and have some ideas to test.

My CTR comment was about safari i didnt tested chrome yet.

And if the there is no solution besides https i will never test it. But i believe there will be a service in a few weeks which offers it without the need of https.

Sure, I know CTR has been in the context of Safari.

Again, I understand the https concerns. I assure you, if there is a way to use Chrome notifications non-https, we will support it as well. Anything we can do to provide a great service and make it easy to use.