Jaffa Pepsi

Device Class Detection in JavaScript

The unusual way by using CSS Media Queries

In some occasions it is necessary to know which device a user is using while writing JavaScript Web Apps. Should be nothing regarding layout, because for this we have CSS Media Queries.

Somewhere around 2011 W3C introduced matchMedia(), which returns a MediaQueryList object that can be used to detemnine if the document matches the media query string. The using is pretty straightforward and feels a bit like RegEx matching in JS:

1
2
3
4
const mediaQuery = window.matchMedia('(min-width: 1025px)')
if (mediaQuery.matches) {
// do something...
}

If you are interested in this API, you will find good introductions to the topic here, here and here (German).

One point of criticism on this pure JS approach can be, that you have to maintain the breakpoints in addition to CSS … but why not use these existing breakpoints in JS?

If you implement a feature that is based on the different device classes, you don’t have to determine the current class with dozens of lines of JavaScript code, if you just can ask the DOM.

The CSS/JS Breakpoint Hack

For this approach, we take advantage of the fact, that CSS can be used to define not only styles, but also content. We always use it, when showing an icon by using a symbol font like FontAwesome:

1
2
3
4
my-fancy-icon::before {
font-family: FontAwesome5Solid;
content: "\f186";
}

Mixed with a @media rule, we can “inject” the needed device value into the DOM, for example into the BODY tag, but you can take whatever you want:

1
2
3
4
5
@media (min-width: 1025px) {
body:before {
content: "DESKTOP";
}
}

Just one line more in the masses of CSS code to make a Web App responsive, but with this one you can do without many lines of JS.

Now you can read out this value via JavaScript by getting the styles of the tag and get the injected content:

1
2
var style = window.getComputedStyle(document.querySelector("body"), ":before");
var breakpoint = style.getPropertyValue("content").replace(/\"/g, "");

It is advisable to embed this request into an event listener of DOMContentLoaded, because the rule has to be set, before you can access it.

See a simple working pen:

You can interact with this article (applause, criticism, whatever) by mention it in one of your posts, which will be shown here as a Webmention, or by leaving a good old comment with your GitHub account.

Webmentions

No Webmentions yet...

In case your blog software can't send Webmentions, you can use this form to submit me a mention of this article...


Comments

Related