O'Reilly

pointer Media Query

By on  

This media query has not yet been implemented and is currently only a proposed spec. I've written this post to raise awareness of it and get general thoughts about it.

As more devices emerge and differences in device interaction are implemented, the more important good CSS code will become.  In order to write good CSS, we need some indicator about device capabilities.  We've used CSS media queries thus far, with checks for max-width and pixel ratios.  One new proposed CSS media query is the pointer media query;  the pointer media query provides information about how accurate the device pointer is (if present).

The pointer media query has three values:

  • none - device has no pointer
  • coarse - pointer has limited accuracy
  • fine - pointer has high level of accuracy

A fine pointer would be a mouse or a stylus-based touch screen, while a coarse pointer would be a finger-based touch screen, like an iPad, iPhone, or other tablet.  The example provided within the spec shows enlarging checkboxes and radio buttons on coarse-pointered devices:

/* Make radio buttons and check boxes larger if we have an inaccurate pointing device */
@media (pointer:coarse) {
	input[type="checkbox"], input[type="radio"] {
		min-width:30px;
		min-height:40px;
		background:transparent;
	}
}

I envision this API being used to enlarge navigation items and other prominent links when the pointer is coarse.  What would you do with the pointer media query?

Track.js Error Reporting

Upcoming Events

Recent Features

  • Create a CSS Cube

    CSS cubes really showcase what CSS has become over the years, evolving from simple color and dimension directives to a language capable of creating deep, creative visuals.  Add animation and you've got something really neat.  Unfortunately each CSS cube tutorial I've read is a bit...

  • Detect DOM Node Insertions with JavaScript and CSS Animations

    I work with an awesome cast of developers at Mozilla, and one of them in Daniel Buchner. Daniel's shared with me an awesome strategy for detecting when nodes have been injected into a parent node without using the deprecated DOM Events API.

Incredible Demos

  • PHP Woot Checker – Tech, Wine, and Shirt Woot

    If you haven't heard of Woot.com, you've been living under a rock. For those who have been under the proverbial rock, here's the plot: Every day, Woot sells one product. Once the item is sold out, no more items are available for purchase. You don't know how many...

  • HTML5 Input Types Alternative

    As you may know, HTML5 has introduced several new input types: number, date, color, range, etc. The question is: should you start using these controls or not? As much as I want to say "Yes", I think they are not yet ready for any real life...

Discussion

  1. This is great. Is there also a way to check this with JS? I guess you could use the “animation end event” hack for this, but would be better if it’s officially supported and always in sync.

  2. DigDug2k

    The problem with this particular query is that it assumes you have one or the other, when its becoming more common to have both a fine and a course pointer. In fact, studies have constantly shown people are really really good at using two different pointing devices at the same time!

    Webdevs need to be careful that they don’t assume just because the user is on a touch screen, they’re using touch. Sites need to design to handle both (simultaneously, CSS is the oddball here because there you can’t optimize for both experiences at the same time). PointerEvents will make that easier, but they’re barely at the starting gate right now (which is good because it means this time we can design something good and not just something that matches the iPhone).

  3. Providing a live demo for something that has no implementations at all is somewhat confusing.

  4. Alex

    Do Canary

    • Alex

      … or Aurora support this?

  5. Daniel Glazman

    With my CSS WG Co-chairmanship’s hat on, this is a part of an Editor’s Draft that was *never* discussed inside the CSS WG and is *far away* from reaching the level of first public Working Draft yet. I really hope your implementation is prefixed or behind a preference. And I think you should probably not have implemented-and-released it at all without discussing it with the CSS WG first… Speaking of the proposal, ‘coarse’ is a VERY bad choice for a value since most non english speakers will not understand it, trust me on that please.

    In summary, this is a very very very early proposal, it’s still subject to major changes, and I certainly don’t want to hear in the future “we’ve implemented and shipped it, we can’t change it any more” from Mozilla :-)

    • I just found the proposal interesting — I’m not someone who implements these things at Mozilla. I’ve updated the note at the top to make it clear that this proposal has not been approved.

  6. I’d love this media query to also tell me if I’m dealing with a touchscreen or a pointer. Basically, can I use the hover effect.

    * None
    * Fine Touch (stylus)
    * Course Touch (finger)
    * Pointer (mouse)

    Maybe even a:

    * Terrible Pointer (Wiimote)

  7. Matt

    @Justin css media query level 4 is also proposing the hover media feature, check http://dev.w3.org/csswg/mediaqueries4/#hover for spec and other level 4 stuff

  8. Here’s an interesting result when trying to match the query in Chrome: http://d.pr/i/gP5r

    Very frustrating – I’m trying to find a semi-reliable way to distinguish between desktop and touch-based users for tooltips.

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!