[jitsi-dev] Testing desktop sharing on Firefox with Jidesha


#1

Hi all,

I have cloned the Jidesha repository. Performing Chromium testing on
Debian Jessi, it has run smoothly. But I'm having some difficulties
getting it to work on Firefox ESR.

I edited the make.sh file by completing the variables "DOMAINS" with the
domain where I have Jitsi Meet running, and the variable EXT_ID, which
has in this case "jitsi-meet". I understand that it would have to be
enough according to the README.md.

But I have not been able to make it work. In fact, Firefox does not even
show the desktop sharing icon.

After having uninstalled the extension I tried to install the XPI file
later but now I get a message saying "This add-on could not be installed
because it appears to be corrupt"

I would appreciate if anyone could tell me how to solve this.

Thanks in advance.

Kind regards,
Daniel


#2

I don't think this is a valid ID.
https://developer.mozilla.org/en-US/Add-ons/Install_Manifests

Boris

···

On 16/01/2017 18:35, Daniel Bareiro wrote:

Hi all,

I have cloned the Jidesha repository. Performing Chromium testing on
Debian Jessi, it has run smoothly. But I'm having some difficulties
getting it to work on Firefox ESR.

I edited the make.sh file by completing the variables "DOMAINS" with the
domain where I have Jitsi Meet running, and the variable EXT_ID, which
has in this case "jitsi-meet". I understand that it would have to be
enough according to the README.md.


#3

Hi, Boris.

···

On 17/01/17 01:42, Boris Grozev wrote:

I have cloned the Jidesha repository. Performing Chromium testing on
Debian Jessi, it has run smoothly. But I'm having some difficulties
getting it to work on Firefox ESR.

I edited the make.sh file by completing the variables "DOMAINS" with the
domain where I have Jitsi Meet running, and the variable EXT_ID, which
has in this case "jitsi-meet". I understand that it would have to be
enough according to the README.md.

I don't think this is a valid ID.
https://developer.mozilla.org/en-US/Add-ons/Install_Manifests

I was checking the install.rdf file. Here I just changed "maxVersion"
from 44 to 50, since I am using Firefox ESR 45.6.0. But I'm not sure
what else could be wrong. This is the content:

-------------------------------------------------------------------------
<?xml version="1.0"?>

<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:em="http://www.mozilla.org/2004/em-rdf#">

  <Description about="urn:mozilla:install-manifest">
    <em:id>JIDESHA_EXT_ID</em:id>
    <em:name>Jidesha</em:name>
    <em:description>Jitsi-Meet Desktop Sharing: enables screen sharing
for the Jitsi-Meet application.</em:description>
    <em:version>0.1.1</em:version>
    <em:creator>Jitsi</em:creator>
    <em:homepageURL>https://github.com/jitsi/jidesha/</em:homepageURL>
    <em:type>2</em:type>
    <em:bootstrap>true</em:bootstrap>

    <!-- Mozilla Firefox -->
    <em:targetApplication>
      <Description>
        <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
        <em:minVersion>40.0</em:minVersion>
        <em:maxVersion>50.0</em:maxVersion>
      </Description>
    </em:targetApplication>
  </Description>
</RDF>
-------------------------------------------------------------------------

Should I also replace JIDESHA_EXT_ID with a generic ID using something
like this [1]?

Thanks for your reply.

Kind regards,
Daniel

[1]
https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Generating_GUIDs


#4

Hi again,

···

On 17/01/17 09:01, Daniel Bareiro wrote:

I have cloned the Jidesha repository. Performing Chromium testing on
Debian Jessi, it has run smoothly. But I'm having some difficulties
getting it to work on Firefox ESR.

I edited the make.sh file by completing the variables "DOMAINS" with the
domain where I have Jitsi Meet running, and the variable EXT_ID, which
has in this case "jitsi-meet". I understand that it would have to be
enough according to the README.md.

I don't think this is a valid ID.
https://developer.mozilla.org/en-US/Add-ons/Install_Manifests

I was checking the install.rdf file. Here I just changed "maxVersion"
from 44 to 50, since I am using Firefox ESR 45.6.0. But I'm not sure
what else could be wrong. This is the content:

-------------------------------------------------------------------------
<?xml version="1.0"?>

<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:em="http://www.mozilla.org/2004/em-rdf#">

  <Description about="urn:mozilla:install-manifest">
    <em:id>JIDESHA_EXT_ID</em:id>
    <em:name>Jidesha</em:name>
    <em:description>Jitsi-Meet Desktop Sharing: enables screen sharing
for the Jitsi-Meet application.</em:description>
    <em:version>0.1.1</em:version>
    <em:creator>Jitsi</em:creator>
    <em:homepageURL>https://github.com/jitsi/jidesha/</em:homepageURL>
    <em:type>2</em:type>
    <em:bootstrap>true</em:bootstrap>

    <!-- Mozilla Firefox -->
    <em:targetApplication>
      <Description>
        <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
        <em:minVersion>40.0</em:minVersion>
        <em:maxVersion>50.0</em:maxVersion>
      </Description>
    </em:targetApplication>
  </Description>
</RDF>
-------------------------------------------------------------------------

Should I also replace JIDESHA_EXT_ID with a generic ID using something
like this [1]?

[1] https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Generating_GUIDs

From what I see, the content above is a template to generate
target/install.rdf. In this file JIDESHA_EXT_ID is replaced by the
EXT_ID variable used in make.sh which in my case had "jitsi-meet".

Kind regards,
Daniel


#5

Correct. I don't think "jitsi-meet" is valid ID. The doc I linked to has the requirements for an ID. We usually use something like "jidesha@one.of.the.deployment.domains.com"

Boris

···

On 17/01/2017 06:12, Daniel Bareiro wrote:

Hi again,

On 17/01/17 09:01, Daniel Bareiro wrote:

I have cloned the Jidesha repository. Performing Chromium testing on
Debian Jessi, it has run smoothly. But I'm having some difficulties
getting it to work on Firefox ESR.

I edited the make.sh file by completing the variables "DOMAINS" with the
domain where I have Jitsi Meet running, and the variable EXT_ID, which
has in this case "jitsi-meet". I understand that it would have to be
enough according to the README.md.

I don't think this is a valid ID.
https://developer.mozilla.org/en-US/Add-ons/Install_Manifests

I was checking the install.rdf file. Here I just changed "maxVersion"
from 44 to 50, since I am using Firefox ESR 45.6.0. But I'm not sure
what else could be wrong. This is the content:

-------------------------------------------------------------------------
<?xml version="1.0"?>

<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:em="http://www.mozilla.org/2004/em-rdf#">

  <Description about="urn:mozilla:install-manifest">
    <em:id>JIDESHA_EXT_ID</em:id>
    <em:name>Jidesha</em:name>
    <em:description>Jitsi-Meet Desktop Sharing: enables screen sharing
for the Jitsi-Meet application.</em:description>
    <em:version>0.1.1</em:version>
    <em:creator>Jitsi</em:creator>
    <em:homepageURL>https://github.com/jitsi/jidesha/</em:homepageURL>
    <em:type>2</em:type>
    <em:bootstrap>true</em:bootstrap>

    <!-- Mozilla Firefox -->
    <em:targetApplication>
      <Description>
        <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
        <em:minVersion>40.0</em:minVersion>
        <em:maxVersion>50.0</em:maxVersion>
      </Description>
    </em:targetApplication>
  </Description>
</RDF>
-------------------------------------------------------------------------

Should I also replace JIDESHA_EXT_ID with a generic ID using something
like this [1]?

[1] https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Generating_GUIDs

From what I see, the content above is a template to generate
target/install.rdf. In this file JIDESHA_EXT_ID is replaced by the
EXT_ID variable used in make.sh which in my case had "jitsi-meet".


#6

Hi, Boris.

I have cloned the Jidesha repository. Performing Chromium testing on
Debian Jessi, it has run smoothly. But I'm having some difficulties
getting it to work on Firefox ESR.

I edited the make.sh file by completing the variables "DOMAINS"
with the
domain where I have Jitsi Meet running, and the variable EXT_ID, which
has in this case "jitsi-meet". I understand that it would have to be
enough according to the README.md.

I don't think this is a valid ID.
https://developer.mozilla.org/en-US/Add-ons/Install_Manifests

I was checking the install.rdf file. Here I just changed "maxVersion"
from 44 to 50, since I am using Firefox ESR 45.6.0. But I'm not sure
what else could be wrong. This is the content:

-------------------------------------------------------------------------

<?xml version="1.0"?>

<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:em="http://www.mozilla.org/2004/em-rdf#">

  <Description about="urn:mozilla:install-manifest">
    <em:id>JIDESHA_EXT_ID</em:id>
    <em:name>Jidesha</em:name>
    <em:description>Jitsi-Meet Desktop Sharing: enables screen sharing
for the Jitsi-Meet application.</em:description>
    <em:version>0.1.1</em:version>
    <em:creator>Jitsi</em:creator>
    <em:homepageURL>https://github.com/jitsi/jidesha/</em:homepageURL>
    <em:type>2</em:type>
    <em:bootstrap>true</em:bootstrap>

    <!-- Mozilla Firefox -->
    <em:targetApplication>
      <Description>
        <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
        <em:minVersion>40.0</em:minVersion>
        <em:maxVersion>50.0</em:maxVersion>
      </Description>
    </em:targetApplication>
  </Description>
</RDF>
-------------------------------------------------------------------------

Should I also replace JIDESHA_EXT_ID with a generic ID using something
like this [1]?

[1]
https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Generating_GUIDs

From what I see, the content above is a template to generate
target/install.rdf. In this file JIDESHA_EXT_ID is replaced by the
EXT_ID variable used in make.sh which in my case had "jitsi-meet".

Correct. I don't think "jitsi-meet" is valid ID. The doc I linked to has
the requirements for an ID. We usually use something like
"jidesha@one.of.the.deployment.domains.com"

Thank you! Now I understood what you meant before :slight_smile: That prevented the
error mentioned above. But now I get a different error because it seems
that it is not an add-on signed by Mozilla: "The add-on could not be
installed because it has not been verified". I have temporarily changed
the property "xpinstall.signatures.required" to "false" and that way I
can install it. But if I then set it back to "true", Firefox
automatically disables the add-on.

By testing with the property in "false", the desktop sharing icon is not
displayed. Do you know why it can be? I can confirm that the domain
configured in make.sh was included in
media.getusermedia.screensharing.allowed_domains.

Thanks for your reply.

Kind regards,
Daniel

···

On 17/01/17 12:50, Boris Grozev wrote:


#7

Is this the same domain as the one jitsi-meet loads from? Is the new extension ID configured in config.js?

The java script app detects the extension by trying to load
chrome://EXT_ID/content/DOMAIN.png

Look for "firefox" in the java script console logs to see if detection failed.

Boris

···

On 17/01/2017 11:46, Daniel Bareiro wrote:

Hi, Boris.

On 17/01/17 12:50, Boris Grozev wrote:

I have cloned the Jidesha repository. Performing Chromium testing on
Debian Jessi, it has run smoothly. But I'm having some difficulties
getting it to work on Firefox ESR.

I edited the make.sh file by completing the variables "DOMAINS"
with the
domain where I have Jitsi Meet running, and the variable EXT_ID, which
has in this case "jitsi-meet". I understand that it would have to be
enough according to the README.md.

I don't think this is a valid ID.
https://developer.mozilla.org/en-US/Add-ons/Install_Manifests

I was checking the install.rdf file. Here I just changed "maxVersion"
from 44 to 50, since I am using Firefox ESR 45.6.0. But I'm not sure
what else could be wrong. This is the content:

-------------------------------------------------------------------------

<?xml version="1.0"?>

<RDF xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:em="http://www.mozilla.org/2004/em-rdf#">

  <Description about="urn:mozilla:install-manifest">
    <em:id>JIDESHA_EXT_ID</em:id>
    <em:name>Jidesha</em:name>
    <em:description>Jitsi-Meet Desktop Sharing: enables screen sharing
for the Jitsi-Meet application.</em:description>
    <em:version>0.1.1</em:version>
    <em:creator>Jitsi</em:creator>
    <em:homepageURL>https://github.com/jitsi/jidesha/</em:homepageURL>
    <em:type>2</em:type>
    <em:bootstrap>true</em:bootstrap>

    <!-- Mozilla Firefox -->
    <em:targetApplication>
      <Description>
        <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id>
        <em:minVersion>40.0</em:minVersion>
        <em:maxVersion>50.0</em:maxVersion>
      </Description>
    </em:targetApplication>
  </Description>
</RDF>
-------------------------------------------------------------------------

Should I also replace JIDESHA_EXT_ID with a generic ID using something
like this [1]?

[1]
https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Generating_GUIDs

From what I see, the content above is a template to generate
target/install.rdf. In this file JIDESHA_EXT_ID is replaced by the
EXT_ID variable used in make.sh which in my case had "jitsi-meet".

Correct. I don't think "jitsi-meet" is valid ID. The doc I linked to has
the requirements for an ID. We usually use something like
"jidesha@one.of.the.deployment.domains.com"

Thank you! Now I understood what you meant before :slight_smile: That prevented the
error mentioned above. But now I get a different error because it seems
that it is not an add-on signed by Mozilla: "The add-on could not be
installed because it has not been verified". I have temporarily changed
the property "xpinstall.signatures.required" to "false" and that way I
can install it. But if I then set it back to "true", Firefox
automatically disables the add-on.

By testing with the property in "false", the desktop sharing icon is not
displayed. Do you know why it can be? I can confirm that the domain
configured in make.sh was included in
media.getusermedia.screensharing.allowed_domains.


#8

Hi, Boris.

From what I see, the content above is a template to generate
target/install.rdf. In this file JIDESHA_EXT_ID is replaced by the
EXT_ID variable used in make.sh which in my case had "jitsi-meet".

Correct. I don't think "jitsi-meet" is valid ID. The doc I linked to has
the requirements for an ID. We usually use something like
"jidesha@one.of.the.deployment.domains.com"

Thank you! Now I understood what you meant before :slight_smile: That prevented the
error mentioned above. But now I get a different error because it seems
that it is not an add-on signed by Mozilla: "The add-on could not be
installed because it has not been verified". I have temporarily changed
the property "xpinstall.signatures.required" to "false" and that way I
can install it. But if I then set it back to "true", Firefox
automatically disables the add-on.

By testing with the property in "false", the desktop sharing icon is not
displayed. Do you know why it can be? I can confirm that the domain
configured in make.sh was included in
media.getusermedia.screensharing.allowed_domains.

Is this the same domain as the one jitsi-meet loads from? Is the new
extension ID configured in config.js?

The java script app detects the extension by trying to load
chrome://EXT_ID/content/DOMAIN.png

Look for "firefox" in the java script console logs to see if detection
failed.

I have not seen any mention of config.js changes in the README.md [1]
when using Jidesha with Firefox. Now I was investigating the config.js
file and I found the following variables:

desktopSharingFirefoxExtId: null,
desktopSharingFirefoxDisabled: true,

The second one was perhaps responsible for the icon not being displayed
in Firefox. After configuring these variables, desktop sharing worked in
Firefox ESR (it might be nice to document this in Jidesha's README.md
for Firefox).

But I have not found a way to stop sharing the screen. When I click on
the window sharing icon on the address bar and then "stop sharing", I do
not see the image of my camera again.

Thanks for your reply.

Kind regards,
Daniel

[1] https://github.com/jitsi/jidesha/blob/master/firefox/README.md

···

On 17/01/17 15:12, Boris Grozev wrote:


#9

Hi again,

···

On 17/01/17 16:03, Daniel Bareiro wrote:

From what I see, the content above is a template to generate
target/install.rdf. In this file JIDESHA_EXT_ID is replaced by the
EXT_ID variable used in make.sh which in my case had "jitsi-meet".

Correct. I don't think "jitsi-meet" is valid ID. The doc I linked to has
the requirements for an ID. We usually use something like
"jidesha@one.of.the.deployment.domains.com"

Thank you! Now I understood what you meant before :slight_smile: That prevented the
error mentioned above. But now I get a different error because it seems
that it is not an add-on signed by Mozilla: "The add-on could not be
installed because it has not been verified". I have temporarily changed
the property "xpinstall.signatures.required" to "false" and that way I
can install it. But if I then set it back to "true", Firefox
automatically disables the add-on.

By testing with the property in "false", the desktop sharing icon is not
displayed. Do you know why it can be? I can confirm that the domain
configured in make.sh was included in
media.getusermedia.screensharing.allowed_domains.

Is this the same domain as the one jitsi-meet loads from? Is the new
extension ID configured in config.js?

The java script app detects the extension by trying to load
chrome://EXT_ID/content/DOMAIN.png

Look for "firefox" in the java script console logs to see if detection
failed.

I have not seen any mention of config.js changes in the README.md [1]
when using Jidesha with Firefox. Now I was investigating the config.js
file and I found the following variables:

desktopSharingFirefoxExtId: null,
desktopSharingFirefoxDisabled: true,

The second one was perhaps responsible for the icon not being displayed
in Firefox. After configuring these variables, desktop sharing worked in
Firefox ESR (it might be nice to document this in Jidesha's README.md
for Firefox).

But I have not found a way to stop sharing the screen. When I click on
the window sharing icon on the address bar and then "stop sharing", I do
not see the image of my camera again.

In Chromium by pressing the desktop sharing button on the main button
bar, it exits the desktop sharing and returns to the camera image. But
in Firefox ESR I do not have that same behavior when I press the button.
Can it be a bug?

Kind regards,
Daniel


#10

Yes, this sounds like a bug.

Boris

···

On 17/01/2017 20:00, Daniel Bareiro wrote:

Hi again,

On 17/01/17 16:03, Daniel Bareiro wrote:

From what I see, the content above is a template to generate
target/install.rdf. In this file JIDESHA_EXT_ID is replaced by the
EXT_ID variable used in make.sh which in my case had "jitsi-meet".

Correct. I don't think "jitsi-meet" is valid ID. The doc I linked to has
the requirements for an ID. We usually use something like
"jidesha@one.of.the.deployment.domains.com"

Thank you! Now I understood what you meant before :slight_smile: That prevented the
error mentioned above. But now I get a different error because it seems
that it is not an add-on signed by Mozilla: "The add-on could not be
installed because it has not been verified". I have temporarily changed
the property "xpinstall.signatures.required" to "false" and that way I
can install it. But if I then set it back to "true", Firefox
automatically disables the add-on.

By testing with the property in "false", the desktop sharing icon is not
displayed. Do you know why it can be? I can confirm that the domain
configured in make.sh was included in
media.getusermedia.screensharing.allowed_domains.

Is this the same domain as the one jitsi-meet loads from? Is the new
extension ID configured in config.js?

The java script app detects the extension by trying to load
chrome://EXT_ID/content/DOMAIN.png

Look for "firefox" in the java script console logs to see if detection
failed.

I have not seen any mention of config.js changes in the README.md [1]
when using Jidesha with Firefox. Now I was investigating the config.js
file and I found the following variables:

desktopSharingFirefoxExtId: null,
desktopSharingFirefoxDisabled: true,

The second one was perhaps responsible for the icon not being displayed
in Firefox. After configuring these variables, desktop sharing worked in
Firefox ESR (it might be nice to document this in Jidesha's README.md
for Firefox).

But I have not found a way to stop sharing the screen. When I click on
the window sharing icon on the address bar and then "stop sharing", I do
not see the image of my camera again.

In Chromium by pressing the desktop sharing button on the main button
bar, it exits the desktop sharing and returns to the camera image. But
in Firefox ESR I do not have that same behavior when I press the button.
Can it be a bug?


#11

Hi, Boris.

···

On 18/01/17 00:12, Boris Grozev wrote:

From what I see, the content above is a template to generate
target/install.rdf. In this file JIDESHA_EXT_ID is replaced by the
EXT_ID variable used in make.sh which in my case had "jitsi-meet".

Correct. I don't think "jitsi-meet" is valid ID. The doc I linked
to has
the requirements for an ID. We usually use something like
"jidesha@one.of.the.deployment.domains.com"

Thank you! Now I understood what you meant before :slight_smile: That
prevented the
error mentioned above. But now I get a different error because it
seems
that it is not an add-on signed by Mozilla: "The add-on could not be
installed because it has not been verified". I have temporarily
changed
the property "xpinstall.signatures.required" to "false" and that way I
can install it. But if I then set it back to "true", Firefox
automatically disables the add-on.

By testing with the property in "false", the desktop sharing icon
is not
displayed. Do you know why it can be? I can confirm that the domain
configured in make.sh was included in
media.getusermedia.screensharing.allowed_domains.

Is this the same domain as the one jitsi-meet loads from? Is the new
extension ID configured in config.js?

The java script app detects the extension by trying to load
chrome://EXT_ID/content/DOMAIN.png

Look for "firefox" in the java script console logs to see if detection
failed.

I have not seen any mention of config.js changes in the README.md [1]
when using Jidesha with Firefox. Now I was investigating the config.js
file and I found the following variables:

desktopSharingFirefoxExtId: null,
desktopSharingFirefoxDisabled: true,

The second one was perhaps responsible for the icon not being displayed
in Firefox. After configuring these variables, desktop sharing worked in
Firefox ESR (it might be nice to document this in Jidesha's README.md
for Firefox).

But I have not found a way to stop sharing the screen. When I click on
the window sharing icon on the address bar and then "stop sharing", I do
not see the image of my camera again.

In Chromium by pressing the desktop sharing button on the main button
bar, it exits the desktop sharing and returns to the camera image. But
in Firefox ESR I do not have that same behavior when I press the button.
Can it be a bug?

Yes, this sounds like a bug.

Thanks for confirm. Then I can open an issue in Github to check it. Let
me know, please.

Kind regards,
Daniel


#12

Sure, but note that this may be specific to your environment or firefox version. I cannot reproduce it with firefox 50 on a jitsi-meet instance from a few weeks ago.

Boris

···

On 18/01/2017 04:53, Daniel Bareiro wrote:

Hi, Boris.

Yes, this sounds like a bug.

Thanks for confirm. Then I can open an issue in Github to check it. Let
me know, please.


#13

Hi, Boris.

Yes, this sounds like a bug.

Thanks for confirm. Then I can open an issue in Github to check it. Let
me know, please.

Sure, but note that this may be specific to your environment or firefox
version. I cannot reproduce it with firefox 50 on a jitsi-meet instance
from a few weeks ago.

It's possible. I'll see if I can reproduce it with Firefox 50 and I will
comment on the results.

On the other hand, when you have a few minutes, if you can check the
mentioned in the thread "Possible bug with authentication from Firefox
ESR", I would appreciate it :slight_smile:

Thanks for your time.

Kind regards,
Daniel

···

On 18/01/17 13:25, Boris Grozev wrote:


#14

Hi Daniel,

···

On 18/01/2017 11:56, Daniel Bareiro wrote:

Hi, Boris.

On 18/01/17 13:25, Boris Grozev wrote:

Yes, this sounds like a bug.

Thanks for confirm. Then I can open an issue in Github to check it. Let
me know, please.

Sure, but note that this may be specific to your environment or firefox
version. I cannot reproduce it with firefox 50 on a jitsi-meet instance
from a few weeks ago.

It's possible. I'll see if I can reproduce it with Firefox 50 and I will
comment on the results.

On the other hand, when you have a few minutes, if you can check the
mentioned in the thread "Possible bug with authentication from Firefox
ESR", I would appreciate it :slight_smile:

Sorry, I don't have any insight there.

Boris