Closed Bug 1294123 Opened 4 years ago Closed 3 years ago
>> Vendor name BlueJeans >> Point of contact Lee Ho >> Site URLs bluejeans.com,*.bluejeans.com,*.a.bluejeans.com >> Does the application provide users with notice and control? https://bluejeans.com/privacy-policy >> 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
Please consider this whitelist addition for inclusion in the next Firefox release.
Hi Shell -- I sent you an email about this bug and am following up with a needinfo. I'm looking to get this addition to our whitelist approved for landing this week. Thanks!
Status: UNCONFIRMED → NEW
Ever confirmed: true
sorry Maire - was slow on replying (just back from Grand Canyon- no internet). at a glance this looks good, so i approve adding
Attachment #8796682 - Flags: review?(rjesup) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/f81946d26642 Add BlueJeans to screensharing whitelist r=jesup
Comment on attachment 8796682 [details] [diff] [review] bluejeans.patch Approval Request Comment [Feature/regressing bug #]: screensharing whitelist [User impact if declined]: BlueJeans needs their domain added to the whitelist to allow screensharing and to avoid having users modify settings in about: config. They are deploying their service next month, and they want/need it to work with Firefox Release. [Describe test coverage new/current, TreeHerder]: manually verified (it's a text only change) [Risks and why]: Extremely low risk, very easily verified, pref only change. It would help BlueJeans tremendously to have this in Firefox 50 to align with their release plans. [String/UUID change made/needed]: None
Hello Lee, could you please verify this issue is fixed as expected on a latest Nightly build? Thanks!
Comment on attachment 8796682 [details] [diff] [review] bluejeans.patch Addition to screenshare whitelist, Aurora51+, Beta50+
Thanks for following up on this request. I can confirm that this is fixed as expected in 52.0a1 (2016-10-04). The requested Site URLs have been added to media.getusermedia.screensharing.allowed_domains .
You need to log in before you can comment on or make changes to this bug.