Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/buymeasoda/less-media-queries

Using LESS CSS to develop a media query driven solution for modern and legacy browsers
https://github.com/buymeasoda/less-media-queries

Last synced: 18 days ago
JSON representation

Using LESS CSS to develop a media query driven solution for modern and legacy browsers

Host: GitHub
URL: https://github.com/buymeasoda/less-media-queries
Owner: buymeasoda
Created: 2012-11-16T03:07:13.000Z (almost 12 years ago)
Default Branch: master
Last Pushed: 2012-11-16T09:43:18.000Z (almost 12 years ago)
Last Synced: 2024-07-31T17:23:49.692Z (3 months ago)
Size: 109 KB
Stars: 17
Watchers: 3
Forks: 1
Open Issues: 0
Metadata Files:
- Readme: readme.md

Awesome Lists containing this project

README

# CSS and Media Query Strategies Using LESS

How can we create a CSS authoring strategy that will:

* Allow non-media query capable browsers (such as Internet Exploere 8 and earlier) to receive the "Desktop" version of a layout, rather than the "mobile first" layout
* Avoid having to excessively override a desktop first strategy when styling for smaller form factors
* Let CSS widgets and components remain self contained with their rules grouped together for different targeted resolutions and dimensions
* Efficiently output media queries, collating together queries of the same type into single blocks rather than multiple repeating media query definitions
* Make it easy to change the media query rules for breakpoints or retina
* Remain transparent to developers and designers while authoring
* Maintain as much of the natural order of CSS as possible (eg. retain cascade order)
* Allow the result to be efficiently concatenated and minified for optimal delivery over the wire

What follows is an exploration of using LESS to achieve as many of these goals as possible.

## Basic CSS Structure

The solution aims to map to the following broad (and deliberately verbose) over-arching structure, based on 320 and up:

Note: These files wouldn't be delivered to the user like this in the production result, it just illustrates the designers intent on how they'd like to mentally deal with the design strategy.

## Sample Component CSS

CSS rules for a single component can be grouped together, along with the design and layout adjustments for different media query breakpoints and resolutions.

.selector {
/* Universal rules for #selector go here, all browsers get these rules */
}

.320up() {
.selector {
/* Rules for any desired media query triggers go here, in this case it's a min-width: 320px rule */
}
}

.768up() {
.selector a {
/* Additional rules. Not all defined trigger points need to be included, only where relevant */
}
}

.all2x() {
.selector {
/* Rules for image overrides that apply at all dimensions for user agents that meet the @2x / hi-dpi rules */
}
}

.768up2x() {
.selector {
/* Hi-dpi / @2x rules for the 768px breakpoint */
}
}

## Sample LESS Stucture

The output files are generated from the same source CSS, so there is no double maintenance or divergence of styles.

* `utilities.less` contains the media query trigger points, named media query variables and pre-defined output for legacy and modern styles
* `styles.less` is a demo file that represents your project styles. In practise, this would be a collection of project structured project files

### Legacy LESS

@import "utilities";
@import "styles";

.legacyStyles;

### Modern LESS

@import "utilities";
@import "styles";

.modernStyles;

## Sample CSS Output

Based on the example "sample component" code above, this is the resulting output.

### Legacy CSS

.selector {
/* Universal rules for #selector go here, all browsers get these rules */
}
.selector {
/* Rules for any desired media query triggers go here, in this case it's a min-width: 320px rule */
}
.selector a {
/* Additional rules. Not all defined trigger points need to be included, only where relevant */
}

### Modern CSS

Note: Empty media query blocks have been removed in the example output to keep things focussed.

.selector {
/* Universal rules for #selector go here, all browsers get these rules */
}

@media only screen and (max-width: 767px) {
.selector {
/* Rules for any desired media query triggers go here, in this case it's a min-width: 320px rule */
}
}

@media only screen and (min-width: 768px) {
.selector a {
/* Additional rules. Not all defined trigger points need to be included, only where relevant */
}
}

@media only screen and (min-device-pixel-ratio: 1.3), only screen and (-webkit-min-device-pixel-ratio: 1.3), only screen and (-o-min-device-pixel-ratio: 13/10), only screen and (min-resolution: 120dpi) {
.selector {
/* Rules for image overrides that apply at all dimensions for user agents that meet the @2x / hi-dpi rules */
}
}

@media only screen and (min-device-pixel-ratio: 1.3), only screen and (-webkit-min-device-pixel-ratio: 1.3), only screen and (-o-min-device-pixel-ratio: 13/10), only screen and (min-resolution: 120dpi), only screen and (min-width: 768px) {
.selector {
/* Hi-dpi / @2x rules for the 768px breakpoint */
}
}

## Caveats

The strategy outlined above meets all of the criteria listed at the start of the document, and provides a clean optimisation of grouping media queries together without repeating the same query over and over. There is however, one caveat that needs to be evaluated before adopting this strategy.

**While rules within media queries always retain their original order, the media query blocks (groups of rules) will always be output in the pre-defined media query group order**

This caveat is less about the technical implemention used, and more about the semantic debate of "grouped media queries" vs. "in-place / repeated media queries". If you're happily in the "grouped media queries" camp, then the caveat instead becomes a desirable feature.

To describe the situation in more detail:

* When CSS is authored, it honours the order of the rules when applying the cascade. If two rules are valid (and equally specific), the latter rule applies
* By grouping the media query rules into defined and ordered blocks (eg. `320 followed by 480, 768, 992, 1200, 1320`), rules in different media query blocks can be output in a different order than authored.

For example, when both of the below rules match, the final colour will be red:

@media only screen and (min-width: 768px) {
color: blue;
}

@media only screen and (min-width: 320px) {
color: red;
}

However, with media query grouping and pre-defined ordering, the rule set will be output in the order `320, 480, 768, 992, 1200, 1320`, regardless of the authored order. So the above rules would be renderers as follows, causing the final colour to be blue:

@media only screen and (min-width: 320px) {
color: red;
}

@media only screen and (min-width: 768px) {
color: blue;
}

**To avoid this sitation causing suprises, order your media query definitions in the same order as your predefined media query blocks. The resulting output will then semantically match the original cascade**

## Todo

* Do not write out any media query boilerplate for defined trigger points that are empty and unused
* Remove need for pre-defining media query variables by using a default / undefined check when outputting the rules