1254940 - If the link generator exits a room whilst sharing is paused, and then re-enters, the link-clicker display is messed up

Status: RESOLVED FIXED

(Hello (Loop) :: Client, defect, P1)

Description

[Mark Banner (:standard8)]

STR:

1) Set up a call between a link generator & clicker
2) On the link generator, select Stop Sharing

=> link clicker shows that the peer has paused sharing.

3) Exit the room on the link generator's side.

=> link clicker shows that your friend has left.

4) Re-enter the room from the link generator.

=> Initially both the sharing screen is shown and the peer has paused. Then, just the peer has paused is shown, with no remote share visible.

The remote share should have been shown.

Comment 1

[GitHub Autolander Bot]

Attachment: [loop] mancas:bug1254940 > mozilla:master

Comment 2

[Manuel Casas Barrado [:mancas]]

Comment on attachment 8728423 [details] [review]
[loop] mancas:bug1254940 > mozilla:master

Just need to reset the state on peer disconnected.

Comment 3

[Romain Testard [:RT]]

Lowering the priority since it's low occurence, low criticaly with a work-around

Comment 4

[Manuel Casas Barrado [:mancas]]

Landed in master: https://github.com/mozilla/loop/commit/0181101f30dc1c479da39d864aeb93f9e2499e74

Comment 5

[Camelia Badau [:cbadau], Desktop Test Engineering]

The issue is still reproducible on Firefox 46 Beta 7 Build 2 (buildID: 20160401021843) - on  Windows 7 64bit, Windows XP 32bit, Mac OS X 10.8.5 and Ubuntu 12.04 32bit.

Comment 6

[Mark Banner (:standard8)]

(In reply to Camelia Badau, QA [:cbadau] from comment #5)
> The issue is still reproducible on Firefox 46 Beta 7 Build 2 (buildID:
> 20160401021843) - on  Windows 7 64bit, Windows XP 32bit, Mac OS X 10.8.5 and
> Ubuntu 12.04 32bit.

Did you test with the dev server?

This bug applies to the standalone web pages which is not part of the Firefox release.

Comment 7

[Camelia Badau [:cbadau], Desktop Test Engineering]

I've tested with the dev server (i've set "loop.server" = https://loop-dev.stage.mozaws.net/v0 in about:config) and the issue is no longer reproducible.