搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

add-on options non accessible

  • 3 个回答
  • 9 人有此问题
  • 1 次查看
  • 最后回复者为 andyrome64

more options

There are a number of add-ons that are reported as compatible with Android but they are unusable as it is impossible to configure them. I am using FF 47 on an Android 6.0 phone and I have 3 add-ons installed: - Adblock plus: options are available - Ghostery: options can be set at installation but later there is no way to change them - Self-destroying cookies: no way to access the configuration

Can anyone explain how to configure add-ons that miss the "option" button in the add-on page? If they cannot be configured then I would suggest that they are not reported as compatible with the Android version of firefox.

There are a number of add-ons that are reported as compatible with Android but they are unusable as it is impossible to configure them. I am using FF 47 on an Android 6.0 phone and I have 3 add-ons installed: - Adblock plus: options are available - Ghostery: options can be set at installation but later there is no way to change them - Self-destroying cookies: no way to access the configuration Can anyone explain how to configure add-ons that miss the "option" button in the add-on page? If they cannot be configured then I would suggest that they are not reported as compatible with the Android version of firefox.

所有回复 (3)

more options

Hi

Add-ons are developed by independent third parties, not Mozilla. I recommend that you contact the developers directly (their details can be found on the page you downloaded the add-on from) and they should be able to provide support and possibly make changes to heir software.

I hope this helps, but if not, please come back here and we can look into a different solution for you.

more options

Hi, Thanks for your suggestion. I have contacted the developers however my point was more on the fact that many extensions seem to have this problem so perhaps someone at mozilla should check if the instructions/API that the developers are told to use in their configuration page are actually working properly in the Android version. It seems strange that so many extensions have this problem on the Android version but are ok on the Windows version... maybe the javascript code that manages the "add-ons" page needs to be looked at? Regards, Andy

more options

I got a reply from the one of the extension developers. He seems to agree with me that this is due to a problem in Firefox. There is an open bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1269132 This bug also impacts the pre-installed OpenH264 extension so it's actually very easy to reproduce.