Søg i 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.

Læs mere

How was my Mozila tabs Transparent

  • 12 svar
  • 7 har dette problem
  • 6 visninger
  • Seneste svar af Anamon

more options

I was working with Aurora and my tabs and the Aurora icon on the top left were all transparent! I thought it was cool. Then it went back to normal. How do you recreate this effect?

I was working with Aurora and my tabs and the Aurora icon on the top left were all transparent! I thought it was cool. Then it went back to normal. How do you recreate this effect?

Alle svar (12)

more options

its theme..

Dress up your firefox with theme from

more options

Make sure that you do not run Firefox in (permanent) Private Browsing mode.

  • Tools > Options > Privacy > Firefox will: "Use custom settings for history"
  • Deselect: [ ] "Always use private browsing mode"
more options

I do have a persona. I don't know how the tabs suddenly become transparent.

more options

iamjayakumars The Personsas themes are not really themes but toolbar wallpaper basically. The Real themes are at https://addons.mozilla.org/en-US/firefox/complete-themes/

more options

Can you please answer my question?

more options

Ok, none of you guys seem to get the answer here. I've replicated it by going to sent messages on hotmail.com and then pressing back. That leads to transparent tabs for some reason. Image in attachment.

more options

I'm having this same issue and I agree the problem crops up when I am in my hotmail.com/outlook.com account and go to the sent items. I am not using private browsing so this does not apply. What is causing this inconvenience? Thanks!

more options

It's a bug: #878046 It occurs for certain "animated" websites, and only if hardware acceleration is active. In my case, on occasion the same actions that trigger the transparent toolbars will in fact crash Firefox entirely.

Other sites you can reproduce this on:

http://en.ony.ru/work/medsi, then click on 'WORK' in the top bar.

[http://www.bbc.co.uk/6music/programmes/a-z (might have to reload 1-2 times for it to happen)

more options

Try to set the Boolean pref media.windows-media-foundation.enabled to false on the about:config page.

more options

Sorry about the previous response, I misinterpreted the results.

Disabling WMF seems to have had no effect. The transparency bug remains reproducible, and Firefox occasionally crashes entirely.

Something seems to affect the chance with which these crashes occur. While Firefox used to crash about 1 in 10 times I performed the reproducing steps above, today it will crash in approximately 9 out of 10 tries.

Ændret af Anamon den

more options

While it is Firefox v23+ that is triggering the bug, the video driver (nVidia in my case) is definitely involved as well, and so far I'm not sure whether either or both of them are at fault.

At the moment the bug tends to go beyond triggering transparent toolbars, and beyond triggering Firefox crashes, to repeatedly crashing the nVIDIA kernel mode display driver. On one of the bug-reproducing pages mentioned above, my screen started to turn black, flicker back on, back off, back on, etc. -- with Windows always mentioning that it had to restart the display driver after a crash, during the second I could actually see anything before it crashed again. After going through this about 10 times, Windows finally decided to bluescreen and tell me to check my hardware for defects before rebooting.

After playing around with the above-mentioned sites some more, I succeeded in getting this to happen again. However this time, during the few moments of the display rebuilding before crashing again, I managed to quit Firefox, and the repeated display driver crashes stopped immediately, everything going back to normal.

I'm not sure how to report this, since Firefox itself didn't actually crash in these instances, it simply shot the entire system down.

Dump files report a VIDEO_TDR_FAILURE (code 116) in nvlddmkm. Stack trace (watch out for linebreak issues): nt!KeBugCheckEx dxgkrnl!TdrBugcheckOnTimeout+0xec dxgkrnl!TdrIsRecoveryRequired+0x21f dxgmms1!VidSchiReportHwHang+0x40b dxgmms1!VidSchWaitForCompletionEvent+0x196 dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9 dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xfc dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b dxgmms1!VidSchiSubmitRenderCommand+0x241 dxgmms1!VidSchiSubmitQueueCommand+0x50 dxgmms1!VidSchiWorkerThread+0xd6 nt!PspSystemThreadStartup+0x5a nt!KiStartSystemThread+0x16