Jitsi picture-in-picture (PIP) snagging list

[lampholder]

• Read receipt avatars appear on top of the PIP
• Message hover actions (reply, react, etc.) appear on top of the PIP
• Clicking the PIP doesn't return you to the related room (like it does when you click on the P2P PIP)
• The PIP looks like a strange grey rectangle if you have lots of participants and on grid view - it would be better to switch to whatever the opposite of grid view is called when you move to PIP:
  

[turt2live]

The first two are #15221

Clicking the PIP doesn't return you to the related room (like it does when you click on the P2P PIP)

This is intentional so you can (un)mute yourself and generally interact with Jitsi.

[lampholder]

This is intentional so you can (un)mute yourself and generally interact with Jitsi.

Makes sense, but:

• the Jitsi PIP needs to provide a way to return to its room; currently it doesn't
• users shouldn't have to think about Jitsi and P2P being different - if the "click to go home" UX can't work for jitsi, then we need something else that works for both

[lampholder]

It looks the PIP for p2p calls has been designed with exactly this in mind:

Is it on anyone's immediate agenda to apply this to jitsi calls, too?

[toger5]

I want to change the CallPreview class to PiPContainer. It is already used to either display the p2p call or a persistent widget.
I also want to reuse the container things: header/borader/goToAssociatedRoom button.
(the PictureInPictureDragger>CallViewHeader should also wrap the sticky PiP widget (the jitsi call))

Can this get signed of by design? @vector-im/design