Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Open

Many extensions don't work on support.mozilla.org

Firefox Extensions
sagenuage81 replied
Thomas
Thomas

Hi 🙂 This is a follow-up to https://support.mozilla.org/en-US/questions/1511440.

The problem is this: support.mozilla.org is a site intended for asking support questions, and it is very inconvenient not to be able to use extensions that assist with typing (notably Unicodify and Clippings).


i have 2 suggestions to do:

1) Let the user choose whether to keep extensions enabled (in which case support.mozilla.org is not privileged, the user cannot send "Troubleshooting Information", and there is no security vulnerability), or to send "Troubleshooting Information" (in which case extensions are disabled).

2) Review the design of support.mozilla.org in a way that a subdomain like ffinfos.support.mozilla.org is privileged instead of support.mozilla.org, Firefox sends "Troubleshooting Information" to ffinfos.support.mozilla.org, and extensions are enabled on support.mozilla.org but can never interact with data that Firefox would send to ffinfos.support.mozilla.org.

What do you think about this?

Hi 🙂 This is a follow-up to https://support.mozilla.org/en-US/questions/1511440. The problem is this: support.mozilla.org is a site intended for asking support questions, and it is very inconvenient not to be able to use extensions that assist with typing (notably Unicodify and Clippings). i have 2 suggestions to do: 1) Let the user choose whether to keep extensions enabled (in which case support.mozilla.org is not privileged, the user cannot send "Troubleshooting Information", and there is no security vulnerability), or to send "Troubleshooting Information" (in which case extensions are disabled). 2) Review the design of support.mozilla.org in a way that a subdomain like ffinfos.support.mozilla.org is privileged instead of support.mozilla.org, Firefox sends "Troubleshooting Information" to ffinfos.support.mozilla.org, and extensions are enabled on support.mozilla.org but can never interact with data that Firefox would send to ffinfos.support.mozilla.org. What do you think about this?

All Replies (3)

Thomas
Thomas Question owner

James said
https://support.mozilla.org/en-US/kb/quarantined-domains


Unicodify (https://addons.mozilla.org/fr/firefox/addon/unicodify-text-transformer/) has a section "Run on sites with restrictions" which is set to "Allow". it doesn't work. what's wrong?

Clippings (https://addons.mozilla.org/fr/firefox/addon/clippings/) has no section "Run on sites with restrictions". is it right?

sagenuage81
sagenuage81

The important detail is that this is controlled per add-on, not only per site. If an add-on shows “Run on sites with restrictions” and it is set to Allow, then Firefox is letting it try to run there. But the add-on still has to request the right host/content-script permissions and support that mode itself.

So yes, it is possible that Unicodify shows that option while Clippings does not. For Clippings I would treat that as an add-on limitation/design choice, unless its developer adds support for restricted domains. For support.mozilla.org specifically, the safer workaround is probably an OS-level text replacement/clipboard tool, because that works outside Firefox’s extension permission model.

Modified by sagenuage81

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.