Skip to content

Commit

Permalink
Merge pull request #1884 from patrickhlauke/mq4-range-vs-minmax-expand
Browse files Browse the repository at this point in the history
[mediaqueries-4] Expand example for min-/max- shortcoming vs proper range context
  • Loading branch information
frivoal authored Oct 17, 2017
2 parents 8b3e9a4 + 98ff70c commit 2d75c52
Showing 1 changed file with 10 additions and 1 deletion.
11 changes: 10 additions & 1 deletion mediaqueries-4/Overview.bs
Original file line number Diff line number Diff line change
Expand Up @@ -735,8 +735,17 @@ Using “min-” and “max-” Prefixes On Range Features</h4>
it does not take into account the possibility of fractional viewport sizes which can occur as a result of non-integer pixel densities
(e.g. on high-dpi displays or as a result of zooming/scaling).
Any viewport widths that fall between 320px and 321px will result in none of the styles being applied.

One approach to work around this problem is to increase the precision of the values used for the comparison. Using the example above,
changing the second comparison value to 320.01px significantly reduces the change that a viewport width on a device would fall
between the cracks.

<pre>
@media (max-width: 320px) { /* styles for viewports <= 320px */ }
@media (min-width: 320.01px) { /* styles for viewports >= 320.01px */ }
</pre>

In these situations, <a>range context</a> queries (which are not limited to “>=” and “<=” comparisons) offer a more appropriate solution:
However, in these situations, <a>range context</a> queries (which are not limited to “>=” and “<=” comparisons) offer a more appropriate solution:

<pre>
@media (width <= 320px) { /* styles for viewports <= 320px */ }
Expand Down

0 comments on commit 2d75c52

Please sign in to comment.