Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Remove no theme support error message

  • 2 답장
  • 1 이 문제를 만남
  • 9 보기
  • 최종 답변자: 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?