Picture-in-Picture mirrorred in calls - personal_screens
Categories
(Toolkit :: Video/Audio Controls, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | unaffected |
| firefox68 | --- | affected |
People
(Reporter: cfogel, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(1 file)
|
106.99 KB,
image/png
|
Details |
Affected versions
- 68.0a1 (2019-05-08)
Affected platforms
- Windows 10
Steps to reproduce
- Launch Firefox;
- Access talky.io and start a new chat / join a call;
- In the left-most section hover on the image from your camera;
- Hover over the PIP controls;
Expected result
- PIP Text is properly displayed.
Actual result
- Text is mirrored.
Regression range
- not a regression;
Additional notes
- attached screenshot with the issue;
| Reporter | ||
Comment 1•2 years ago
|
||
Adding https://jitsi.org/ and https://www.facebook.com/ as other webrtc platform which exhibit this issue.
Another note would be that the container image/video is indeed flipped.
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Noticed this issue on Google Meet this week.
Comment 3•2 years ago
|
||
Is it possible to detect this scenario Mike? Maybe we could hide PiP for WebRTC by default?
(In reply to Adam Stevenson [:adamopenweb] from comment #3)
Is it possible to detect this scenario Mike? Maybe we could hide PiP for WebRTC by default?
Hm. I would have expected the patch in bug 1547795 to have fixed this. I can't, for example, reproduce this on jitsi.org. Talky.io seems to be broken right now, so I can't test it.
How reliably can you reproduce it on Meet? Can you show me a screenshot?
Comment 5•2 years ago
|
||
Just tested this again on Meet and wasn't able to reproduce the issue.
Okay, can't reproduce on talky.io either, so going to close this as INCOMPLETE for now then. Please re-open if this is still an issue.
Updated•2 years ago
|
Updated•2 years ago
|
Bugbug thinks this bug is a regression, but please revert this change in case of error.
Comment 9•7 months ago
|
||
This will get fixed by bug 1672401.
Description
•