Different size for caller video area and disabled video image, in conversation window

RESOLVED INCOMPLETE

Status

P3
normal
Rank:
36
RESOLVED INCOMPLETE
3 years ago
2 years ago

People

(Reporter: bogdan_maris, Unassigned)

Tracking

unspecified
Points:
---

Firefox Tracking Flags

(firefox42 affected, firefox43 affected, firefox44 affected)

Details

Attachments

(1 attachment)

Created attachment 8665861 [details]
Screencast showing the issue

Affected builds:
- latest Nightly 44.0a1
- latest Developer Edition 43.0a2
- Firefox 42beta1

Affected OS`s:
- Mac OS X 10.10.5
- Ubuntu 14.04 32-bit
- Windows 7 64-bit

STR:
1. Start Firefox
2. Click Hello icon
3. Make a conversation
4. Join the conversation from another pc, tab, browser.
5. From conversation window click Disable Video

Expected results: Disable Video image has the same size with caller video area.

Actual results: Disable Video image and caller video area have different sizes.

Notes:
1. Don`t know if this is an issue, but I would say to keep the same size for consistency.
2. This is not a regression, it reproduces on old builds as well.
3. Requesting needinfo from Sevaan for his opinion.
Flags: needinfo?(sfranks)
Nice catch Bogdan. Yes, the inset video size should remain static.
Flags: needinfo?(sfranks)
(In reply to Sevaan Franks [:sevaan] from comment #1)
> Nice catch Bogdan. Yes, the inset video size should remain static.

This is actually hard to do. We could probably assume a set aspect ratio, except for instance, in a conversation that starts as audio-only we wouldn't know the size of the video until it was enabled, so it would potentially still change size.

We can probably just assume an 4:3 aspect ratio for now if you're happy with that.
Flags: needinfo?(sfranks)
Yes please.
Flags: needinfo?(sfranks)

Updated

3 years ago
Rank: 36
Priority: -- → P3
Whiteboard: [visual refresh defect]
Whiteboard: [visual refresh defect]
Support for Hello/Loop has been discontinued.

https://support.mozilla.org/kb/hello-status

Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.