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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Firefox hover state

  • 3 uphendule
  • 1 inale nkinga
  • 64 views
  • Igcine ukuphendulwa ngu nbilodeau

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.

Isisombululo esikhethiwe

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

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 0

All Replies (3)

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.

Okulungisiwe ngu nbilodeau

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

Isisombululo Esikhethiwe

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