Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Search 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.

Learn More

Este fío pechouse e arquivouse. Faga unha nova pregunta se precisa axuda.

Firefox hover state

  • 3 respostas
  • 1 has this problem
  • 24 views
  • Last reply by SuMo Bot

more options

Hi, normaly I used the @media (hover: none) and (pointer: coarse) to remove time animation on mobile, so that when we click, the hover state appears instantly. But recently I noticed this happens on Firefox "desktop". On other browsers the animation is still smooth. Is it something that is gonna come back as before or I should change my query, or find a workaround? Thanks.

Hi, normaly I used the @media (hover: none) and (pointer: coarse) to remove time animation on mobile, so that when we click, the hover state appears instantly. But recently I noticed this happens on Firefox "desktop". On other browsers the animation is still smooth. Is it something that is gonna come back as before or I should change my query, or find a workaround? Thanks.

Chosen solution

Turns out, rebooting the computer did the trick...

Ler a resposta no contexto 👍 0

All Replies (4)

more options

On this site : https://hover-pointer-media-query.glitch.me/ we see Firefox has @media(hover:none) which is not the outpu I think we should expect.

more options

nbilodeau said

Hi, normaly I used the @media (hover: none) and (pointer: coarse) to remove time animation on mobile, so that when we click, the hover state appears instantly. But recently I noticed this happens on Firefox "desktop". On other browsers the animation is still smooth. Is it something that is gonna come back as before or I should change my query, or find a workaround? On this site : https://hover-pointer-media-query.glitch.me/ we see Firefox has @media(hover:none) which I think is not the ouput we should expect.
more options

Chosen Solution

Turns out, rebooting the computer did the trick...

more options

This question has been locked because the original author has deleted their account. While you can no longer post new replies, the existing content remains available for reference.