1305942 - Add CliteHD to screenshare whitelist

Status: RESOLVED WONTFIX

(Firefox Graveyard :: Screen Sharing Whitelist, defect, P1)

Description

[tanvir]

>> Vendor name
NLTVC Sdn.Bhd.

>> Point of contact
[e-mail]

>> Site URLs
clite.nltvc.com
*.clitehd.com
*.crystalviewhd.com
*.nltvc.com

>> Does the application provide users with notice and control?
Privacy
You understand that through your use of the Services you consent to the following collection and use of this information.

Voice and video communicated in a room is not stored anywhere in our system. Chat messages is history is deleted at the end of the session.

The Content stored in the Service is stored securely, and may also be temporarily stored in other locations to facilitate the transmission of the Content to and from your devices.

Should you choose to de-register with our services we will delete all your Content.

>> Have you seen and agree with the Developer Screen Sharing Submission policy?
Yes

>> Does the usage comply with the Developer Screen Sharing Submission Policy guidelines?
Yes

Comment 1

[tanvir]

Site URLs

https://clite.nltvc.com
https://*.clitehd.com
https://*.crystalviewhd.com
https://*.nltvc.com

Comment 2

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

Hi Maire, wondering if you can help with this request.

Comment 3

[Maire Reavy [:mreavy]]

The screensharing whitelist "feature" has gone away in Firefox 52.  Starting in Fx 52, any site/domain works.  The only question is how soon the vendor NLTVC plans to launch service with screensharing support and whether we'd uplift that change to Fx51 (current Beta).  So I'll start by asking the reporter.

@tanvir -- How quickly are you launching your service with screensharing support?  Is it before March?  Thanks.

Comment 4

[Maire Reavy [:mreavy]]

Resetting needinfo flag to ping me when there is a reply from the reporter

Comment 5

[tanvir]

We already launched our video conferencing services since this year in June. The screen sharing also started at the same time. Our sites can share screen with Google Chrome without any problem. On the other hand, we can share screen using Firefox if we manually insert the domain name in the screen sharing whitelist using "about:config". 

@Maire -- Is that answers your question?

Me and my company would really appreciate it if you could add our domains as soon as possible.
Thanks

Comment 6

[tanvir]

(In reply to Maire Reavy [:mreavy] from comment #3)
> The screensharing whitelist "feature" has gone away in Firefox 52.  Starting
> in Fx 52, any site/domain works.  The only question is how soon the vendor
> NLTVC plans to launch service with screensharing support and whether we'd
> uplift that change to Fx51 (current Beta).  So I'll start by asking the
> reporter.
> 
> @tanvir -- How quickly are you launching your service with screensharing
> support?  Is it before March?  Thanks.

We already launched our video conferencing services since this year in June. The screen sharing also started at the same time. Our sites can share screen with Google Chrome without any problem. On the other hand, we can share screen using Firefox if we manually insert the domain name in the screen sharing whitelist using "about:config". 

@Maire -- Is that answers your question?

Me and my company would really appreciate it if you could add our domains as soon as possible.
Thanks

Comment 7

[Maire Reavy [:mreavy]]

How does screensharing work with Chrome? Via an extension?  

A simple extension will also work with Firefox in Fx50 (current release) and Fx51 (current Beta):

You can find documentation for restartless addons here (it's going away, but relevant for Fx51 and earlier):
    https://developer.mozilla.org/en-US/Add-ons/Bootstrapped_extensions

and to get you started, here is a very simple example of how to add a domain to the whitelist:
    https://hg.mozilla.org/users/blassey_mozilla.com/screenshare-whitelist/file/tip

All of this becomes unnecessary in Fx52 and later.

Comment 8

[Lakshmi]

>> Vendor name
NLTVC Sdn.Bhd.

>> Point of contact
[e-mail]

>> Site URLs
clite.nltvc.com
*.clitehd.com
*.crystalviewhd.com
*.nltvc.com

>>Add-On

An add-on under the name clite has been submitted for review. The status still remains "being reviewed" even 2 days after submission with the same queue number. The add-on was uploaded from the account with username lakshmi17. Kindly do the needy.

Comment 9

[Maire Reavy [:mreavy]]

I don't work regularly with the team that reviews add-on submissions, but I know some folks who do.

Shell -- Can you check the status of the "clite" add-on?  See Comment 7 and Comment 8 for context.  Thanks!

Comment 10

[Lakshmi]

Thank you very much for, our add-on is signed and is available for public. The add-on when installed onto the developer version of Firefox, works as expected, but fails to do the same in Firefox 50.1.0. Kindly look into it and suggest changes if any, from our side. Thanks in advance.

Comment 11

[Maire Reavy [:mreavy]]

(In reply to Lakshmi from comment #10)
> Thank you very much for, our add-on is signed and is available for public.
> The add-on when installed onto the developer version of Firefox, works as
> expected, but fails to do the same in Firefox 50.1.0. Kindly look into it
> and suggest changes if any, from our side. Thanks in advance.

Please open a separate bug ticket for the problem with your add-on. This ticket is only about updating the whitelist, which is no longer needed starting with Firefox 52 (current Beta).

Comment 12

[:shell escalante]

Hi, I am resolving this bug as "won't fix", since starting Firefox 52 on April 18th the Screensharing whitelist is no longer needed to share your screen or windows. Please let us know if you find any problems!

        Much of this work was front-end, UX/UI changes, including support to let the UI know what streams are "scary" to share (see bug 1284910). See the meta bug 1127522 for all the work that went into this.

        Please read Jan-Ivar's blog post explaining the risks that users need to know about when sharing their screen or windows: https://blog.mozilla.org/webrtc/share-browser-windows-entire-screen-sites-trust/.

        The new UI permission dialog for screensharing links to a SUMO article with similar content to Jan-Ivar's post, but our SUMO team tailored it to a less technical user.

Comment 13

[:shell escalante]

removing need infos from closed bug