1038530 - Loop client doesn't work properly in Chrome (video shows as grey square, no remote video)

Status: RESOLVED WORKSFORME

(Hello (Loop) :: Client, defect)

Description

[(no longer active)]

Right now the client shows a small grey rectangle instead of the video.  It would be nice if we fixed this before releasing Loop.

Comment 1

[Mark Banner (:standard8)]

I suspect this is a duplicate of bug 1020445 - see attachment 8434278 [details] (though currently I think the local video is the right size, but there's still a grey background for all the height seen in that screenshot).

Ehsan, can you take a look, and if it isn't the same attach a screenshot, and the console output? Your chrome version may also be useful to know.

Comment 2

[(no longer active)]

Attachment: Screenshot

Comment 3

[(no longer active)]

(In reply to Mark Banner (:standard8) (away until 28th July) from comment #1)
> I suspect this is a duplicate of bug 1020445 - see attachment 8434278 [details]
> [details] (though currently I think the local video is the right size, but
> there's still a grey background for all the height seen in that screenshot).
> 
> Ehsan, can you take a look, and if it isn't the same attach a screenshot,
> and the console output? Your chrome version may also be useful to know.

It's not, see the screenshot please.  I run Chrome 36.0.1985.125.

Comment 4

[Vlad Filippov (:vladikoff)]

I was testing Loop with a friend (he is on FF 33.0a2 (2014-08-04)) and he was not getting audio from me on Chrome Version 36.0.1985.125. Video was perfect.

When I switched to FF 33.0a2 myself and opened his link everything worked fine.

Comment 5

[Mark Banner (:standard8)]

(In reply to Vlad Filippov from comment #4)
> I was testing Loop with a friend (he is on FF 33.0a2 (2014-08-04)) and he
> was not getting audio from me on Chrome Version 36.0.1985.125. Video was
> perfect.
> 
> When I switched to FF 33.0a2 myself and opened his link everything worked
> fine.

Please can you file this as a separate bug - I suspect it could be an issue on the Chrome side, but its different to the issue here. Knowing your OS would be useful as well.

Comment 6

[Maire Reavy [:mreavy]]

This should now work.  If there are still problems, please file a new bug.  Thanks.