1340152 - Window to share list is not corresponding with the window names opened

Status: NEW

(Firefox :: Site Identity, defect, P3)

Description

[Hani Yacoub, Desktop QA]

Attachment: window sharing.png

[Affected versions]: 
Nightly 54.0a1

[Affected platforms]:
All platforms: Ubuntu 16.04 x64, Windows 10 x 64, Mac OS X 10.12

[Steps to reproduce]:
1. Go to https://people-mozilla.org/~fqueze2/webrtc/ and click on "Window".
2. Open another browser with a few tabs open in it.
3. Observe the list of the opened windows.
4. Change the tab from the second browser opened.
5. Observe the window to share from the drop down list.

[Expected result]:
Window to share list should be corresponding with the window names opened.

[Actual result]:
Window to share list is not corresponding with the window names opened.

[Note]
After restarting the browser the window share list is updated.

Comment 1

[Panos Astithas (he/him) [:past] (please ni?)]

Florian, what's your take here?

Comment 2

[Florian Quèze [:florian]]

We are not updating the list of possible windows to share after the permission prompt has been displayed. If we wanted to update the list whenever a new window opens (or changes title), we would need the platform code to send a notification when it happens.

Also, this bug seems familiar, so I wouldn't be surprised if it was a duplicate.

Comment 3

[(inactive) Nihanth Subramanya [:nhnt11]]

(In reply to Florian Quèze [:florian] [:flo] from comment #2)
> We are not updating the list of possible windows to share after the
> permission prompt has been displayed. If we wanted to update the list
> whenever a new window opens (or changes title), we would need the platform
> code to send a notification when it happens.

Couldn't we just execute the code that populates the list on-demand when the drop down is opened?

Comment 4

[Florian Quèze [:florian]]

(In reply to Nihanth Subramanya [:nhnt11] from comment #3)

> Couldn't we just execute the code that populates the list on-demand when the
> drop down is opened?

It would be nice, but I'm afraid that would cause UI flicker, due to needing to send a message to the content process and wait for the reply to update the list.