1550416 - Picture-in-Picture mirrorred in calls - personal_screens

Status: RESOLVED DUPLICATE of bug 1672401

(Toolkit :: Video/Audio Controls, defect, P3)

Description

[Cristian Fogel [:cfogel]]

Attachment: pipTalky.png

Affected versions

• 68.0a1 (2019-05-08)

Affected platforms

• Windows 10

Steps to reproduce

1. Launch Firefox;
2. Access talky.io and start a new chat / join a call;
3. In the left-most section hover on the image from your camera;
4. 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;

Comment 1

[Cristian Fogel [:cfogel]]

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.

Comment 2

[Adam Stevenson [:adamopenweb]]

Noticed this issue on Google Meet this week.

Comment 3

[Adam Stevenson [:adamopenweb]]

Is it possible to detect this scenario Mike? Maybe we could hide PiP for WebRTC by default?

Comment 4

[Mike Conley (:mconley) (:⚙️)]

(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

[Adam Stevenson [:adamopenweb]]

Just tested this again on Meet and wasn't able to reproduce the issue.

Comment 6

[Mike Conley (:mconley) (:⚙️)]

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.

Comment 8

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Comment 9

[Mike Conley (:mconley) (:⚙️)]

This will get fixed by bug 1672401.