Hover not working

[raviinstaller]

What version of Tailwind CSS are you using?

v4.0.3

What build tool (or framework if it abstracts the build tool) are you using?

Next js 15

What version of Node.js are you using?

Node 20

What browser are you using?

Chrome

What operating system are you using?

Windows 11

Reproduction URL

https://tailwindcss.com/docs/hover-focus-and-other-states#hover-focus-and-active

Describe your issue

I was just tryin to use tailwindcss v4 for my new project but I noticed that hover: is not working, so, tried to check docs, but on the docs page itself hover is not working.

try hovering on the button in the attached link.

[wongjn]

Seems to be working for me. Consider checking your Chrome browser is sufficiently recent (111+).

[raviinstaller]

my chrome browser version is: Version 132.0.6834.160

[raviinstaller]

loom: https://www.loom.com/share/a08af782d55248568bbcd415c6c6a0dc?sid=eb50d62a-7c2d-43e9-9ba0-fcb9d418fdcc

[adamwathan]

Are you using a device with a touchscreen? It could be that your device doesn’t match the (hover: hover) media query and reports that touch is the primary method of interaction. What specific computer is it?

[raviinstaller]

thnx @adamwathan ,

yes, I've asus z flow x 13, that's a touch laptop, & it went in tablet mode automatically, after shaking device. now its working.

thnx a lot man.

[duprayae179dpl]

I ran into a similar issue related to issue #16416 and posted a comment there you should check out. Seems related to all touchscreen devices including 2-in-1 laptops.

[davidfishlock]

Just FYI everyone there is a regression tracked on Chromium here.

https://issues.chromium.org/issues/394519480

Causing issues with hover: hover and pointer: fine media queries on devices like laptops with a touchscreen but also a mouse connected.

If you are using hoverOnlyWhenSupported in your tailwind config to avoid sticky touch states then this will impact you as it relies on those media queries specifically.

Would recommend considering removing hoverOnlyWhenSupported from your config for now until this is resolved in a future Chrome update, although given it has been set at P0 then shouldn't hopefully be too long.