We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

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

详细了解

Remove no theme support error message

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

more options

I'm noticing that now under Firefox 29, you can install themes (personas) in the private browsing mode. However, you still get an error message saying this isn't possible despite the fact that it is. How, then, do you disable the annoying error message?

Why the browser wouldn't support changing themes in private browsing I'll never understand. After all, "private browsing" means nothing more than it keeps no history of what you've done. Before I went to the private browsing mode I deleted all histories anyway, so what's the big deal?

I'm noticing that now under Firefox 29, you can install themes (personas) in the private browsing mode. However, you still get an error message saying this isn't possible despite the fact that it is. How, then, do you disable the annoying error message? Why the browser wouldn't support changing themes in private browsing I'll never understand. After all, "private browsing" means nothing more than it keeps no history of what you've done. Before I went to the private browsing mode I deleted all histories anyway, so what's the big deal?

由humbz于修改

所有回复 (2)

more options

See:

  • bug 854126 - Lift the lightweight theme restrictions for private windows on Windows and Linux

Please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html

more options

Kindly re-read my original post. My question regarded the fact that I was getting an error message despite the fact that changing personas in private browsing is now possible under FF29.

Under previous versions I was under the impression this was a policy similar to that of other browsers that don't allow add-ons in private browsing. Never did I ever suspect this was a bug. I even searched before posting and found nothing.

Therefore, my original question remains - is there a way to simply disable the error message despite bug 854126 being fixed?