Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

clicking the close tab button is delayed or even lost

  • 1 antwurd
  • 1 hat dit probleem
  • 12 werjeftes
  • Lêste antwurd fan FredMcD

more options

Hi. After updating to 95.0.0 closing tabs in Firefox sometimes takes several seconds or requires clicking the X button again. Meanwhile, the X button animation works fine and the pages remain fully responsive. The troubleshoot mode doesn't help.

Hi. After updating to 95.0.0 closing tabs in Firefox sometimes takes several seconds or requires clicking the X button again. Meanwhile, the X button animation works fine and the pages remain fully responsive. The troubleshoot mode doesn't help.

Alle antwurden (1)

more options

What's your computer system and Firefox version?

https://support.mozilla.org/en-US/kb/update-firefox-latest-version?cache=no Did you update Firefox to the latest version?

Version 95.0, first offered to Release channel users on December 7, 2021 Version 95.0.1, first offered to Release channel users on December 16, 2021 Version 95.0.2, first offered to Release channel users on December 19, 2021


https://support.mozilla.org/en-US/questions/1359657#answer-1463359 and updated to 95.0. . . . I finally found where the plugin "Widevine Content Decryption Module provided by Google Inc." was not updating to the newest version of December 1, 2021. Ver #4.10.2391.0

cor-el; Make sure you have the latest Widevine version. You can toggle DRM off/on to see if that makes Firefox (re)load DRM components.

You can possibly check the XHR requests in the Browser Console if this doesn't work.