חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

Remove no theme support error message

  • 2 תגובות
  • 1 has this problem
  • 9 views
  • תגובה אחרונה מאת 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?