Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Learn More

Changing tabs leaves artifacts from previous tab on the changed-to tab

  • 2 отговора
  • 2 имат този проблем
  • 7 изгледи
  • Последен отговор от jacob2i

more options

This started happening when I upgraded to FF13 and still does it now if FF14.

To make it happen, bring up youtube in the first tab and start and pause a video. Create a new tab and go to ESPN or google maps. Click to the tab with youtube and then back to the other tab and again to the tab with youtube. NOW you should see the ESPN or google maps information on top of the youtube video player area.

This kind of thing happens on many sites and makes FF very hard to use. The only "solution/workaround" i've found is to minimize and restore firefox or grab and move the tab off the screen and back on again. Major pain.

Any help would be appreciated.

This started happening when I upgraded to FF13 and still does it now if FF14. To make it happen, bring up youtube in the first tab and start and pause a video. Create a new tab and go to ESPN or google maps. Click to the tab with youtube and then back to the other tab and again to the tab with youtube. NOW you should see the ESPN or google maps information on top of the youtube video player area. This kind of thing happens on many sites and makes FF very hard to use. The only "solution/workaround" i've found is to minimize and restore firefox or grab and move the tab off the screen and back on again. Major pain. Any help would be appreciated.

Всички отговори (2)

more options

Try to disable hardware acceleration in Firefox.

more options

Yep. I tried all three of these. It still does not work. My computer is 3 years old now. Wonder if my video cards are just "old school" and don't handle something firefox is doing.

I have no problems like this in Chrome however. And it happened upon upgrade to FF13. Would go back to 12 if I could.

Did you attempt to reproduce the issue as I detailed in my question? Would you mind doing that test and letting me know if you encounter any issues?

thx! :)