Regarding BrowserStack's Firefox Extension

Andrew Swan aswan at mozilla.com
Wed Sep 27 15:34:16 UTC 2017


Hi, I don't know much about how your existing extension works but is using
websockets a possibility?

Since you mentioned chrome.socket.*, presumably you have a Chrome extension
that uses that API?  You're probably already aware, but that is an app API,
not an extension API, and the Chrome maintainers have announced their
intention to remove it at some point.

-Andrew


On Wed, Sep 27, 2017 at 6:01 AM, Dhimil Gosalia <dhimil at browserstack.com>
wrote:

> Adding Neil (VP product, BrowserStack)
>
> Hey Andrew,
> Thanks for the prompt response but as I have mentioned earlier this
> extension is really critical for seamless BrowserStack experience on
> Firefox. Due to the lack of support (or alternatives) for the above
> mentioned APIs we will be forced to drop complete support for Firefox.
>
> Thanks.
>
> On Tue, Sep 26, 2017 at 2:15 AM, Andrew McKay <amckay at mozilla.com> wrote:
>
>> Sadly, at this time I don't believe that there are alternatives to
>> those APIs. There are come bugs for some of those things you've
>> mentioned like:
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1247628 TCP and UDP
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1373640 DNS support
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1323414 streaming support
>>
>> But as you can see those have not been implemented in Firefox 57.
>>
>>
>> On 22 September 2017 at 05:40, Dhimil Gosalia <dhimil at browserstack.com>
>> wrote:
>> > Hello,
>> >
>> > We are the developers of the BrowserStack's Firefox extension. Our goal
>> at
>> > BrowserStack is to help developers to test websites/apps seamlessly on
>> all
>> > the major platforms. That is made possible by our extension which acts
>> as a
>> > reverse proxy and let user test local servers by tunneling the
>> connections.
>> > For your reference: https://www.browserstack.com/local-testing.
>> >
>> > With the changes to the Firefox API leading up to version 57.0, our
>> plugin
>> > was marked as legacy because it's based on XPCOM-javascript API. Now,
>> we are
>> > all excited about new WebExtensions API and the future it holds but
>> > currently, it's missing one of our most used API, chrome.socket.*
>> >
>> > Currently, we use the following services on Firefox in our extension:
>> >
>> > nsISocketTransportService
>> > dnsService
>> > nsIScriptableInputStream
>> > nsIInputStreamPump
>> > nsIBufferedInputStream
>> > nsIAsyncInputStream
>> >
>> >
>> > Checking online, we found that we might not be the only group using the
>> > above APIs. Mozilla and BrowserStack announced a partnership recently
>> and we
>> > don't want our customers on Firefox to miss out on seamless local
>> > integrations! We want to understand if there are any alternatives to the
>> > above APIs.
>> >
>> > I have cc'd my fellow team mates and Adam, who helped us with the right
>> > contact (Thanks Adam!).
>> >
>> > Thank you for helping us out!
>> >
>> > --
>> > Dhimil Gosalia,
>> > BrowserStack.
>> >
>> > _______________________________________________
>> > Webextensions-support mailing list
>> > Webextensions-support at mozilla.org
>> > https://mail.mozilla.org/listinfo/webextensions-support
>> >
>>
>
>
>
> --
> Dhimil Gosalia,
> BrowserStack.
>
> _______________________________________________
> Webextensions-support mailing list
> Webextensions-support at mozilla.org
> https://mail.mozilla.org/listinfo/webextensions-support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/webextensions-support/attachments/20170927/8434e817/attachment.html>


More information about the Webextensions-support mailing list