Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Is there a program to get the GUID of a Mozzilla application or Mozilla fork such as K-Meleon or Waterfox or is there a respository that contains these GUIDs?

  • 2 antwurd
  • 1 hat dit probleem
  • 2 werjeftes
  • Lêste antwurd fan cor-el

Kevin
Kevin
more options

We have several plugins that in the past successfully ran in other Mozilla based browsers such as K-Meleon, Sea-Monkey, Netscape, etc.

In the past the plugin needed to be manually installed or required a special downloadable installer to get the plugin installed/ working with browsers like these.

Recent work on many of these projects now allow you to install plugins directly through the web or though about:addons and then restart the browser to complete the installation, just like in Firefox.

We have the list of the most popular GUIDs from the Mozilla documentation listed below, however we do not have the GUIDs for the more obscure Mozilla based forks or projects. - Firefox, Thunderbird, Nvu, Mozilla Suite or Mozilla Browser 1.x, SeaMonkey, Sunbird, Netscape, Flock, and Mobile.

Is there a way to find the GUIDs for these other browsers: K-Meleon, Waterfox, Firefox Nightly (we are guessing the Nightly builds use the same GUID as Firefox) so that we can add the appropriate information to our install.rdf and update.rdf files or does one need to get in contact with the respective projects to determine these?

For our use either an application that does this, or even a small script that could be run to determine the GUID of these other Mozilla based browsers would be great. If these don't exist, is there a public document or repository that can be accessed to get these GUIDs?

Additionally, is it possible that some of the obscure Mozilla based forks do not contain or utilize GUIDs that are used by the install.rdf and update.rdf manifests? If so, what can we do so that our plugins can be installed automatically for these browsers through the web or about:addons?

Is there a way to tell an install manifest that a particular browser is supported even though no GUID exists for that browser so that the installation can proceed as normal for that browser?

My apologies for the lengthy details and for so many questions. I have searched around and have not been able to find answers to these questions so I figure what better place than directly from Mozilla.

Thanks again for so many great products over the years and for the continued development of most of them. :-)

Kevin

We have several plugins that in the past successfully ran in other Mozilla based browsers such as K-Meleon, Sea-Monkey, Netscape, etc. In the past the plugin needed to be manually installed or required a special downloadable installer to get the plugin installed/ working with browsers like these. Recent work on many of these projects now allow you to install plugins directly through the web or though about:addons and then restart the browser to complete the installation, just like in Firefox. We have the list of the most popular GUIDs from the Mozilla documentation listed below, however we do not have the GUIDs for the more obscure Mozilla based forks or projects. - Firefox, Thunderbird, Nvu, Mozilla Suite or Mozilla Browser 1.x, SeaMonkey, Sunbird, Netscape, Flock, and Mobile. Is there a way to find the GUIDs for these other browsers: K-Meleon, Waterfox, Firefox Nightly (we are guessing the Nightly builds use the same GUID as Firefox) so that we can add the appropriate information to our install.rdf and update.rdf files or does one need to get in contact with the respective projects to determine these? For our use either an application that does this, or even a small script that could be run to determine the GUID of these other Mozilla based browsers would be great. If these don't exist, is there a public document or repository that can be accessed to get these GUIDs? Additionally, is it possible that some of the obscure Mozilla based forks do not contain or utilize GUIDs that are used by the install.rdf and update.rdf manifests? If so, what can we do so that our plugins can be installed automatically for these browsers through the web or about:addons? Is there a way to tell an install manifest that a particular browser is supported even though no GUID exists for that browser so that the installation can proceed as normal for that browser? My apologies for the lengthy details and for so many questions. I have searched around and have not been able to find answers to these questions so I figure what better place than directly from Mozilla. Thanks again for so many great products over the years and for the continued development of most of them. :-) Kevin

Bewurke troch Kevin op

Alle antwurden (2)

guigs
guigs
more options

Kevin, there are a few questions I can answer, but if you have irc you can also reach out to the #addons channel. I will also try to get in touch.

As far as I know:

Is there a way to find the GUIDs for these other browsers: K-Meleon, Waterfox, Firefox Nightly (we are guessing the Nightly builds use the same GUID as Firefox) so that we can add the appropriate information to our install.rdf and update.rdf files or does one need to get in contact with the respective projects to determine these? I do not know. There are generating GUIDS https://developer.mozilla.org/en-US/d.../Generating_GUIDs

Be right back. I will try asking for backup.

Bewurke troch guigs op

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Easiest would be to look for extensions that are compatible with those other browser and check the install.rdf file to get the GUIDs of supported browsers.

Some browser you mentioned are very old and outdated and shouldn't be used these days.

All Firefox versions, including developer builds Nightly and Aurora, have the same GUID.

  • Firefox: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
  • SeaMonkey: {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}

Extension for the Firefox mobile version have a different Fennec GUID.

  • Fennec: {a23983c0-fd0e-11dc-95ff-0800200c9a66}

See also:

I assume that Waterfox uses the same GUID as Firefox because otherwise extensions wouldn't be compatible like they claim. Waterfox might be using a second GUID for extensions (with 64-bit components) that are only compatible with Waterfox.

Bewurke troch cor-el op