Opened 4 years ago

Closed 4 years ago

#13380 closed project (wontfix)

Add Pale Moon 25 support

Reported by: cypherpunks Owned by: zyan
Priority: Medium Milestone: HTTPS-E 4 stable
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Please add Pale Moon 25 support and please make sure the toolbar button/menu works.

Child Tickets

Change History (8)

comment:1 Changed 4 years ago by martywd

At this time in Pale Moon 25, HTTPS Everywhere (installed) shows no toolbar icon. HTTP Everywhere 'Options' button in Add-ons Manager _does_ launch the 'HTTP Everywhere Preferences' window.

A few links that might help explain why this is an issue (new GUID, etc.):

Release notes at PM's forum posted by the Pale Moon dev: ==>

Further comment regarding 'Extensions and Pale Moon 25' by the PM developer (Aug '14) at the PM forum: ==>

comment:2 Changed 4 years ago by jsha

Priority: criticalnormal

martywd, can you try HTTPS Everywhere 4.0.2 with Pale Moon and let me know what the results are?


comment:3 in reply to:  description Changed 4 years ago by cypherpunks

Options box is broken in HTTPS-E 4.0.2 on Pale Moon 25.1.0

comment:4 in reply to:  2 Changed 4 years ago by martywd

Replying to jsha:

martywd, can you try HTTPS Everywhere 4.0.2 with Pale Moon and let me know what the results are?


Just re-installed HTTPS Everywhere 4.0.2 in Pale Moon 25.1.0. The HTTPS Everywhere icon w/options is missing from the toolbar and no where to be found in 'Customize...'.

Whether HTTPS Everywhere 4.0.2 is functioning correctly otherwise, I'm not sure since the DEV version of HTTPS Everywhere 5.x I had installed previously which did display the toolbar icon was so painful to use I ended up disabling HTTPS Everywhere completely? I will monitor HTTPS Everywhere 4.0.2 and get back to you.

Last edited 4 years ago by martywd (previous) (diff)

comment:5 Changed 4 years ago by martywd

HTTPS-Everywhere 4.0.3 recently updated in Pale Moon 25.2.1 (Linux and Windows). Still no toolbar icon displayed.

comment:6 Changed 4 years ago by jsha


Thanks for the update. I've been considering the issue of Pale Moon support in HTTPS Everywhere, and it's not something I have the resources to actively debug and support at this time. I'm happy to accept patches to fix issues and keep the requisite version numbers in install.rdf.


comment:7 Changed 4 years ago by cypherpunks

To fix this: edit install.rdf so it adds Pale Moon 25.x's guid. min version should be 25.0, max version 25.*. The second file that has to be edited is chrome.manifest. Here you have to point it to toolbar_button.xul for that guid. This will add the button to the nav toolbar in Pale Moon 25.x. I tested this on 25.2.1, and it works for 4.0.3. Pale Moon 24.x and earlier have the same guid as Firefox. The options window appears to be broken if I try this on 5.0dev2. I haven't tried this on dev3 or dev4. Hope to see PM25 support in 4.0.4 or 5.0.


<em:targetApplication><!-- Pale Moon 25.x+ -->






# Firefox windows
overlay chrome://browser/content/browser.xul chrome://https-everywhere/content/toolbar_button.xul application={ec8030f7-c20a-464f-9b0e-13a3a9e97384}
# Pale Moon 25.x+ windows
overlay chrome://browser/content/browser.xul chrome://https-everywhere/content/toolbar_button.xul application={8de7fcbb-c55c-4fbe-bfc5-fc555c87dbc4}

Not sure if I had to include the Firefox section, but on my fixed version I added it anyways. The button appears to have been added to the nav toolbar in PM25 using https-everywhere 3.5.3 without any editing. One issue I ran into for this 4.0.3 edit version was the checkmark Show Counter, where it would be enabled if I unchecked it and vice versa. But I don't see that issue anymore.

comment:8 Changed 4 years ago by jsha

Resolution: wontfix
Status: newclosed

Update: HTTPS Everywhere won't support Pale Moon due to limited developer resources. If someone from the Pale Moon community is willing to become a long-term maintainer and test their patches on all supported platforms, that would be fine.

Note: See TracTickets for help on using tickets.