google hangouts msg box can't show on safari

Dalmatian
Contributor

Did someone see the problem of google hangouts with safari(Version 9.1 (11601.5.17.1))?

I see many Mac pro (10.11.4) in my company that can't open the 1st google hangout message box on safari. I'm not sure its related to the new updates or something.

As attached, the 1st chat box you open, normally should show up on the right side of the browser, but it simply not showing up and become transparent.

i found this issue since last week and we did some OS X updates with SUS

btw, Chrome has no similar issue

29e654d0728a413889c55d0edb68280e

7 REPLIES 7

bainter
Contributor

I see the transparent, ghost chat message box too, but then when I try a few minutes, hours or day later, it works. Sometimes there is a Google error message that accompanies it, something like "an error has occurred." Other times, the chat works with one person consistently, then when I try messaging another, that one fails. Odd. This did not occur prior to the switch to Hangouts.

bpavlov
Honored Contributor

We're seeing this as well. This is happening in Safari and Firefox (latest versions) started happening maybe 2 days ago give or take? I suspect this may be an issue on Google's end since it's effecting two other browsers and only started recently (the latest versions of Firefox and Safari have been out more than 2 days that I'm aware of).

Dalmatian
Contributor

@bpavlov i just installed Firefox 45.0.2, i didn't see this issue reoccured. i think i might be happening only on Safari

Aziz
Valued Contributor

Looks like the issue is gone for me.

OS X 10.11.4 + Safari 9.1

edit: It's back!

Dalmatian
Contributor

@Aziz it's an intermittent issue. it happens from time to time.

bpavlov
Honored Contributor

@Dalmatian Not only is the issue intermittent but also hard to reproduce. I've seen it personally in Firefox this week multiple times (even yesterday) and I've had others report it using Safari and Google Chrome.

cdenesha
Valued Contributor III

I saw it once in Chrome so I restarted the browser and it was fixed. I thought it was a fluke. Chrome 50 just came out.