How to remove/ignore :hover css style on touch devices
I want to ignore all :hover CSS declarations if a user visits our website via touch device. Because the :hover CSS does not make sense, and it can even be disturbing if a tablet triggers it on click/tap because then it might stick until the element loses focus. To be honest, I don’t know why touch devices feel the need to trigger :hover in first place — but this is reality, so this problem is reality as well.
a:hover < color:blue; border-color:green; /* etc. >ignore all at once for touch devices */ > So, (how) can I remove/ignore all CSS :hover declarations at once (without having to know each one) for touch devices after having them declared?
I get around this with a php solution where I discover if the viewing device is mobile or not and use the correct stylesheet with various changes based on that. That doesn’t answer your question though. You could potentially use @media queries but that’s not guaranteed to work either when phones and tablets have full hd resolutions.
18 Answers 18
If you’re interested why or what other options there are, read on.
Quick’n’dirty — remove :hover styles using JS
You can remove all the CSS rules containing :hover using Javascript. This has the advantage of not having to touch CSS and being compatible even with older browsers.
function hasTouch() < return 'ontouchstart' in document.documentElement || navigator.maxTouchPoints >0 || navigator.msMaxTouchPoints > 0; > if (hasTouch()) < // remove all the :hover stylesheets try < // prevent exception on browsers not supporting DOM styleSheets properly for (var si in document.styleSheets) < var styleSheet = document.styleSheets[si]; if (!styleSheet.rules) continue; for (var ri = styleSheet.rules.length - 1; ri >= 0; ri--) < if (!styleSheet.rules[ri].selectorText) continue; if (styleSheet.rules[ri].selectorText.match(':hover')) < styleSheet.deleteRule(ri); >> > > catch (ex) <> > Limitations: stylesheets must be hosted on the same domain (that means no CDNs). Disables hovers on mixed mouse & touch devices like Surface or iPad Pro, which hurts the UX.
CSS-only — use media queries
Place all your :hover rules in a @media block:
or alternatively, override all your hover rules (compatible with older browsers):
Limitations: works only on iOS 9.0+, Chrome for Android or Android 5.0+ when using WebView. hover: hover breaks hover effects on older browsers, hover: none needs overriding all the previously defined CSS rules. Both are incompatible with mixed mouse & touch devices.
The most robust — detect touch via JS and prepend CSS :hover rules
This method needs prepending all the hover rules with body.hasHover . (or a class name of your choice)
The hasHover class may be added using hasTouch() from the first example:
if (!hasTouch()) document.body.className += ' hasHover' However, this whould have the same drawbacks with mixed touch devices as previous examples, which brings us to the ultimate solution. Enable hover effects whenever a mouse cursor is moved, disable hover effects whenever a touch is detected.
function watchForHover() < // lastTouchTime is used for ignoring emulated mousemove events let lastTouchTime = 0 function enableHover() < if (new Date() - lastTouchTime < 500) return document.body.classList.add('hasHover') >function disableHover() < document.body.classList.remove('hasHover') >function updateLastTouchTime() < lastTouchTime = new Date() >document.addEventListener('touchstart', updateLastTouchTime, true) document.addEventListener('touchstart', disableHover, true) document.addEventListener('mousemove', enableHover, true) enableHover() > watchForHover() This should work basically in any browser and enables/disables hover styles as needed.
Thank you! Just one comment: wouldn’t it be better to check first if document.styleSheets exists instead of using the try/catch ?
I’ve used try/catch just in case some odd error shows up, that could crash the script, like deleteRule not working because of same-origin policy or flaky support on IE (edited the comment to reflect that). But yeah, in most cases, just a simple check should be sufficient.
It’s worth mentioning that desktop browsers including Firefox will not results in ‘notouch’. They report understanding touch events.
This solution does not work for mixed devices where hover shall work for the mouse but not for touch events
@Haneev it is correct for most cases, although not for your specific one. Making your rule work would add a lot of complexity to the code, which would make the answer harder to understand. I would suggest either splitting the rules or using the 2nd solution, which is more robust anyway. However, you’re very welcome to suggest an edit, if you can improve the first solution without making it too complicated.
2020 Solution — CSS only — No Javascript
Use media hover with media pointer will help you resolve this issue. Tested on chrome Web and android mobile. I known this old question but I didn’t find any solution like this.
@media (hover: hover) and (pointer: fine) < a:hover < color: red; >>I think it’s possible due to the pointer: fine media query evaluating not the actual pointer being used, but the primary pointer — which is mouse. It works great on iOS though.
@MaciejKrawczyk Because your touch screen will be triggering the «coarse» property of pointer. Pointer has 2 options. Fine and Coarse. Fine = The primary input mechanism includes an accurate pointing device. Coarse = The primary input mechanism includes a pointing device of limited accuracy. AKA, a mouse = fine, but your finger will be coarse
hover CSS Media Feature to the rescue! Using only CSS, you can override styles when a device does not have hover capabilities.
The following demo is supported by modern touch devices.
/* hover query styles */ a < color: red; font-size: 3em; >a:hover < color: blue; >@media (hover: none) < a:link, a:visited < color: blue; text-decoration: none; border: 0.1em solid currentColor; padding: 0 0.1em; >> /* used to show if demo browser has hover capabilities */ .detection:before < content: 'UNKNOWN'; color: red; >@media(hover) < .detection:before < content: 'YES'; color: green; >> @media (hover: none) < .detection:before < content: 'NO'; >>- should be red
- should be blue when hovered
- should always be blue
- should be surrounded by a blue border
Note: Keep in mind that since a Surface PC’s primary input (capability) is a mouse, it will end up being a blue link, even if it’s a detached (tablet) screen. Browsers will (should) always default to the most precise input’s capability.
Thanks, this would be convenient! However, I tried it out with Chrome in mobile mode, but it didn’t work out — when I «tapped» it, it went blue anyway.
@SimonFerndriger That’s just a limitation of Chrome devtools. Try opening the link in an actual touch-only device.
Working perfectly on iPad Chrome / Safari vs. OS X Chrome / Safari. Thanks! Finally the elegant solution you’d want for such a small visual issue.
According to Jason´s answer we can address only devices that doesn’t support hover with pure css media queries. We can also address only devices that support hover, like moogal´s answer in a similar question, with @media not all and (hover: none) . It looks weird but it works.
I made a Sass mixin out of this for easier use:
Update 2019-05-15: I recommend this article from Medium that goes through all different devices that we can target with CSS. Basically it’s a mix of these media rules, combine them for specific targets:
@media (hover: hover) < /* Device that can hover (desktops) */ >@media (hover: none) < /* Device that can not hover with ease */ >@media (pointer: coarse) < /* Device with limited pointing accuracy (touch) */ >@media (pointer: fine) < /* Device with accurate pointing (desktop, stylus-based) */ >@media (pointer: none) < /* Device with no pointing */ >Example for specific targets:
@media (hover: none) and (pointer: coarse) < /* Smartphones and touchscreens */ >@media (hover: hover) and (pointer: fine) < /* Desktops with mouse */ >I love mixins, this is how I use my hover mixin to only target devices that supports it:
that doesn’t work at all. you have hover: none in the media query for a hover-supported mixin? you need pointer: coarse as per the other answer here.
Have you even tried it or do you just say it doesn’t work because it looks weird? That’s why I wrote «It looks weird».. And it DOES work for me without pointer: coarse.
I had some inconsistent results with the CSS-approach to this on my OnePlus 5T (in both Chrome and Firefix). This worked fine on iOS, but I couldn’t get it to work on the OnePlus. I tested thoroughly using the any-pointer and any-hover
I have encountered the same problem (in my case with Samsung mobile browsers) and therefore I stumbled upon this question.
Thanks to Calsal’s answer I found something that I believe will exclude virtually all desktop browsers because it seems to be recognized by the mobile browsers I tried (see screenshot from a compiled table: CSS pointer feature detection table ).
The pointer CSS @media feature can be used to apply styles based on whether the user’s primary input mechanism is a pointing device, and if so, how accurate it is
What I discovered is that pointer: coarse is something that is unknown to all desktop browsers in the attached table but known to all mobile browsers in the same table. This seems to be most effective choice because all other pointer keyword values give inconsistent results.
Hence you could construct a media query like Calsal described but slightly modified. It makes use of a reversed logic to rule out all touch devices.
a < color: green; border-color: blue; >@media not all and (pointer: coarse) < a:hover < color: blue; border-color: green; >> It is also described in this gist I created after researching the problem. Codepen for empirical research.
UPDATE (2018): As of writing this update, 2018-08-23, and pointed out by @DmitriPavlutin this technique no longer seems to work with Firefox desktop.
UPDATE (2021): It has been pointed out to me that it seems to work as of Firefox 87.
Thanks @DmitriPavlutin, according to the table (when it was compiled) it should, but I could take another look.
You mean it doesn’t work on Firefox Desktop if used with an exclusively touch device? It works great with everything I’ve tried.
@FuzzeeLowgeek Sounds good! Last time I checked was 2018-08-23, so if you can confirm this for sure, perhaps I can update the answer again?
I’m dealing with a similar problem currently.
There are two main options that occur to me immediately: (1) user-string checking, or (2) maintaining separate mobile pages using a different URL and having users choose what’s better for them.
- If you’re able to use an internet duct-tape language such as PHP or Ruby, you can check the user string of the device requesting a page, and simply serve the same content but with a instead of the normal style.
User strings have identifying information about browser, renderer, operating system, etc. It would be up to you to decide what devices are «touch» versus non-touch. You may be able to find this information available somewhere and map it into your system.
A. If you’re allowed to ignore old browsers, you just have to add a single rule to the normal, non-mobile css, namely: EDIT: Erk. After doing some experimentation, I discovered the below rule also disables the ability to follow links in webkit-browsers in addition to just causing aesthetic effects to be disabled — see http://jsfiddle.net/3nkcdeao/
As such, you’ll have to be a bit more selective as to how you modify rules for the mobile case than what I show here, but it may be a helpful starting point:
As a sidenote, disabling pointer-events on a parent and then explicitly enabling them on a child currently causes any hover-effects on the parent to become active again if a child-element enters :hover .
See http://jsfiddle.net/38Lookhp/5/
B. If you’re supporting legacy web-renderers, you’ll have to do a bit more work along the lines of removing any rules which set special styles during :hover . To save everyone time, you might just want to build an automated copying + seding command which you run on your standard style sheets to create the mobile versions. That would allow you to just write/update the standard code and scrub away any style-rules which use :hover for the mobile version of your pages.
- (I) Alternatively, simply make your users aware that you have an m.website.com for mobile devices in addition to your website.com. Though subdomaining is the most common way, you could also have some other predictable modification of a given URL to allow mobile users to access the modified pages. At that stage, you would want to be sure they don’t have to modify the URL every time they navigate to another part of the site.
Again here, you may be able to just add an extra rule or two to the stylesheets or be forced to do something slightly more complicated using sed or a similar utility. It would probably be easiest to apply :not to your styling rules like div:not(.disruptive):hover <. wherein you would add class="disruptive" to elements doing annoying things for mobile users using js or the server language, instead of munging the CSS.
- (II) You can actually combine the first two and (if you suspect a user has wandered to the wrong version of a page) you can suggest that they switch into/out of the mobile-type display, or simply have a link somewhere which allows users to flop back and forth. As already-stated, @media queries might also be something to look use in determining what’s being used to visit.
- (III) If you’re up for a jQuery solution once you know what devices are «touch» and which aren’t, you might find CSS hover not being ignored on touch-screen devices helpful.