Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

tab focus animation takes up too much CPU

  • 8 Antworten
  • 3 haben dieses Problem
  • 9 Aufrufe
  • Letzte Antwort von cor-el

more options

The attached video show how Firefox uses a lot of CPU just to render the tab switching animations when repeatedly swapping between tabs. That, in itself is probably something that I can live with here, considering I have a powerful machine, but I have concerns the effect this will have when I use Quantum on my older laptop.

Furthermore, I find the animations quite distracting. I trued to use the `toolkit.cosmeticAnimations.enabled` variable to disable this, but setting it to false has no effect. I have also tried the following stylesheet, with no effect:

.tab-loading-burst[bursting]::before {
    background-image: none !important;
}
The attached video show how Firefox uses a lot of CPU just to render the tab switching animations when repeatedly swapping between tabs. That, in itself is probably something that I can live with here, considering I have a powerful machine, but I have concerns the effect this will have when I use Quantum on my older laptop. Furthermore, I find the animations quite distracting. I trued to use the `toolkit.cosmeticAnimations.enabled` variable to disable this, but setting it to false has no effect. I have also tried the following stylesheet, with no effect: .tab-loading-burst[bursting]::before { background-image: none !important; }

Alle Antworten (8)

more options

anarcat said

I have also tried the following stylesheet, with no effect: .tab-loading-burst[bursting]::before { background-image: none !important; }

I may be wrong about this - I added the above to $PROFILE/chrome/userContent.css, but it doesn't seem to take effect. In fact, none of the changes I make to this file seem to take effect. I wonder if that file is still read since Quantum was released?

more options

Hi, userContent.css is for web pages. userChrome.css is for the toolbar area.

Also, try:

/* No swipe of blue when tab loads */
.tab-loading-burst {
  display: none !important;
}
more options

Ausgewählte Lösung

more options

jscher2000 said

Hi, userContent.css is for web pages. userChrome.css is for the toolbar area. Also, try:
/* No swipe of blue when tab loads */
.tab-loading-burst {
  display: none !important;
}


So that didn't quite work - the animation still showed up. What worked was:

.tab-line:not([selected=true]) {
    transition: none !important;
}

Unfortunately, the CPU usage remains, so I'm not sure there is even a way to fix that problem...

more options

anarcat said

What worked was:
.tab-line:not([selected=true]) {
    transition: none !important;
}

Unfortunately, the CPU usage remains, so I'm not sure there is even a way to fix that problem...

Hmm, I wasn't thinking of the tab line. Could you try this to see whether it saves any cycles involved in animations:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.

(2) In the search box above the list, type or paste anim and pause while the list is filtered

(3) Double-click the toolkit.cosmeticAnimations.enabled preference to switch the value from true to false

I'm not sure which animations are considered "cosmetic animations."

more options

as i said in the original post, i did try toolkit.cosmeticAnimations.enabled - it doesn't affect those.

more options

cor-el said

See also:

I am sorry but what excatly are we suppose to do with this CSS code? Do we embed it into another Firefox configuration file?

more options

That is the CSS code that Firefox currently uses. You can modify this code and add CSS rules to change the behavior or disable its effect.

In this case search the page for .tab-loading-burst to see what CSS rules are applied to this class name. You can your your custom rules to userChrome.css and make sure not to forget to add the !important flag to be able to override existing CSS rules.