1271958 - "Disable video" and "Mute your audio" buttons move downwards when message field is dismissed

Status: RESOLVED WONTFIX

(Hello (Loop) :: Client, defect)

Description

[Iulia Cristescu, QA [:JuliaC] (away, please needinfo? [e-mail])]

Attachment: Screenshot showing the issue

[Affected versions]:
- 46.0.1 (20160502172042)
- 47.0b4 build1 (20160509171155)
- 48.0a2 (2016-05-11)
- 49.0a1 (2016-05-10)

[Affected platforms]:
- Windows 10 x86
- Mac OS X 10.11
- Ubuntu 14.04 x86

[Steps to reproduce]:
1. Launch Firefox with a new profile.
2. Go to about:support and check the version of Hello add-on. 
- if the Hello version is 1.3.2, move to step 5
- if the Hello version is older than 1.3.2, move on to step 3
3. Go to https://addons.mozilla.org/en-US/firefox/addon/firefox-hello-beta/versions/?page=1#version-1.3.2 and install Hello 1.3.2.
4. Go to about:support and check again if the Hello version is 1.3.2. 
5. Set the "loop.server" pref to "https://loop-dev.stage.mozaws.net/v0"
6. Click the Hello icon, start a conversation and send the conversation link to another PC 
7. Join the conversation from guest side
- inspect the "Disable video" and "Mute your audio" buttons position in host side
8. Leave the conversation from guest side
- inspect the "Disable video" and "Mute your audio" buttons position in host side

[Expected result]:
- "Disable video" and "Mute your audio" buttons are properly displayed and also aligned (steps 7 and 8)

[Actual result]:
- "Disable video" and "Mute your audio" buttons move downwards (step 8) and is not properly aligned.

[Regression range]:
- I will check as soon as possible.

[Additional notes]:
- I reproduced this issue using Hello 1.3.2
- On Ubuntu 14.04 x86 I reproduced this issue only on 46.0.1 (20160502172042)and 47.0b4 build1 (20160509171155); on latest Nightly and Aurora I still encounter Bug 1249365.

Comment 1

[Iulia Cristescu, QA [:JuliaC] (away, please needinfo? [e-mail])]

Verified on 45.0.1 build1 - the issue is still reproducing. Considering that the Hello version in this build is 1.1.14, this issue is not a regression.

Comment 2

[Ian Bicking (:ianbicking)]

The chat input field will be persistent in the next version, so this particular bug won't happen anymore.