FireFox Hello does not open conversation window after partner joined
When I initiate a conversation and my partner joins, I can hear a sound and get a notification, but the conversation window does not change. That means it does not open the larger chat window.
If I then press the Hello button and select the conversation, pressing the link does nothing.
If I then copy&paste the conversation link in a new FireFox tab, I get the chat window, BUT it asks me to "join the conversation". If I do so, it simply says there are already 2 people in the conversation.
It seems to work fine, when somebody else initiates the conversation.
I've disabled all add-ons, except no-script, which I set to accept all scripts. I have no other FireFox versions installed.
Tutte le risposte (6)
I've called the big guys to help you. Good luck.
FredMcD said
I've called the big guys to help you. Good luck.
Thanks!
I've run some tests with friends on 4 different PCs. PC A: Win8.1, FF (36.0) PC B: Ubuntu, FF (very low-end pc) PC C: Mac, FF PC D: Win7, FF(36.0)
A -> B,C or D: As described in the first post, the conversation window does not change after the partner joins - although I can hear a sound and get the notification.
B -> A: When A joins the conversation (which seems to work fine on A) the window on B changes to "There was a problem". [EDIT: this seems to be a problem of B being very low-end, as it sometimes works fine]
C -> A: This works! No problems there.
D -> A: Same problem as described in the first post.
Additionally I tried to create accounts on A and on D. On A I can add several other people as "contact", on D there is no "contacts" tab. However I think, this is another problem for another thread. The connection issues are causing more trouble.
Modificato da veryBadKarMa il
Hi, a few suggestions:
Have you tried restarting Firefox when you're in this state where the conversation window won't open? If so, have you previously tried renaming a room?
Are you in private browsing mode as well?
Standard8 said
Hi, a few suggestions: Have you tried restarting Firefox when you're in this state where the conversation window won't open? If so, have you previously tried renaming a room? Are you in private browsing mode as well?
thanks for these suggestions.
I've tried restarting FF before and after the invited person joined. Same effect, although I don't hear a sound or see a notification. But the Hello icon turns blue. I've also tried renaming the conversation. Same problem.
Another thing I tried without success is running FF in safe mode.
Sorry for not getting back to you earlier. Which version of Firefox are you using?
Can you try making sure you're on the latest 36.0.4 and trying it there?
My only other thoughts is that there's some configuration option that is blocking what is going on.
You could also try going to Tools -> Web Developer -> Browser Console and see if there's any errors raise soon after startup or when you go try to open the conversation window.
Thanks for getting back at all!
It doesn't work with 36.0.4, too.
When I use the Browser Console and press the HELLO button for the first time, I get the following two errors:
Content Security Policy: The page's settings blocked the loading of a resource at self ("default-src jar:// about: file: chrome:"). about:loopconversation uncaught exception: document is not associated to any tab <unknown>
When I initiate a conversation and try to respond on the other computer, I also get a very long error:
"[Dispatcher] Dispatching action caused an exception: " Exception { message: "", result: 2153644038, name: "", filename: "chrome://browser/content/loop/libs/sdk.js", lineNumber: 2931, columnNumber: 0, inner: null, data: null, stack: "OTHelpers.request@chrome://browser/content/loop/libs/sdk.js:2931:4 OTHelpers.post@chrome://browser/content/loop/libs/sdk.js:2957:6 OT.Analytics/send@chrome://browser/content/loop/libs/sdk.js:6856:0 OT.Analytics/throttledPost@chrome://browser/content/loop/libs/sdk.js:6879:14 OT.Analytics/post@chrome://browser/content/loop/libs/sdk.js:6899:10 OT.Analytics/this.logEvent/<@chrome://browser/content/loop/libs/sdk.js:7053:8 OT._.getClientGuid/<@chrome://browser/content/loop/libs/sdk.js:6817:6 init/<.get@chrome://browser/content/loop/js/conversation.js:631:8 getClientGuid@chrome://browser/content/loop/libs/sdk.js:6764:4 OT._.getClientGuid@chrome://browser/content/loop/libs/sdk.js:6794:4 OT.Analytics/this.logEvent@chrome://browser/content/loop/libs/sdk.js:7019:6 OT.Session/this.logEvent@chrome://browser/content/loop/libs/sdk.js:20485:6 OT.Session/this.connect@chrome://browser/content/loop/libs/sdk.js:20645:0 loop.OTSdkDriver</OTSdkDriver.prototype.connectSession@chrome://browser/content/loop/shared/js/otSdkDriver.js:96:0 loop.store.ConversationStore</ConversationStore<.connectionProgress@chrome://browser/content/loop/shared/js/conversationStore.js:168:0 loop.Dispatcher</Dispatcher.prototype._dispatchNextAction/<@chrome://browser/content/loop/shared/js/dispatcher.js:76:10 loop.Dispatcher</Dispatcher.prototype._dispatchNextAction@chrome://browser/content/loop/shared/js/dispatcher.js:74:6 loop.Dispatcher</Dispatcher.prototype.dispatch@chrome://browser/content/loop/shared/js/dispatcher.js:48:6 loop.store.ConversationStore</ConversationStore<._handleWebSocketProgress@chrome://browser/content/loop/shared/js/conversationStore.js:453:6 triggerEvents@chrome://browser/content/loop/shared/libs/backbone-1.1.2.js:208:31 Backbone.Events.trigger@chrome://browser/content/loop/shared/libs/backbone-1.1.2.js:148:18 loop.CallConnectionWebSocket</CallConnectionWebSocket.prototype._onmessage@chrome://browser/content/loop/shared/js/websocket.js:248:10 " } dispatcher.js:78:10 </p>
It looks a bit like "sdk.js" is causing problems.