**Affected versions** * latest Nightly 81.0a1 **Affected platforms** * Windows 10 x64 **Steps to reproduce** 1. Start a call between two people via https://meet.google.com/. 2. Turn off camera on device 1 using the dedicated website button. 3. Turn on camera on device 1 using the same dedicated website button (grant permissions on the door hanger if FF asks). **Expected result** * The video is correctly resumed, the video doesn't zoom in. **Actual result** * The video is not correctly displayed, the video appeared to be zoomed in. **Regression range** * The issue is not reproducible on Firefox Release 79.0, I will follow-up with a regression range asap. **Additional notes** * Please observe the attached screenshot. * Note that we were not able to reproduce this on all devices, so please let us know if any other information is needed. * The issue is not reproducible on other platforms, nor on Chrome. * I would suggest that this issue can be marked with a S3 severity.
Bug 1656252 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
**Affected versions** * latest Nightly 81.0a1 **Affected platforms** * Windows 10 x64 **Steps to reproduce** 1. Start a call between two people via https://meet.google.com/. 2. Turn off camera on device 1 using the dedicated website button. 3. Turn on camera on device 1 using the same dedicated website button (grant permissions on the door hanger if FF asks). **Expected result** * The video is correctly resumed, the video doesn't zoom in. **Actual result** * The video is not correctly displayed, the video appeared to be zoomed in on device 2. **Regression range** * The issue is not reproducible on Firefox Release 79.0, I will follow-up with a regression range asap. **Additional notes** * Please observe the attached screenshot. * Note that we were not able to reproduce this on all devices, so please let us know if any other information is needed. * The issue is not reproducible on other platforms, nor on Chrome. * I would suggest that this issue can be marked with a S3 severity.