Condition overlap in media query_html/css_WEB-ITnose
Friends who have been exposed to responsive layout must be familiar with media query. Responsive layout is realized through this key attribute. In some responsive layout tutorials, similar settings are usually made as follows to achieve layout examples under different viewport width conditions:
@media screen and (max-width:600px){/* Style 1*/}
@media screen and (min-width:600px) and (max-width:960px){/* Style 2*/}
@media screen and (min-width:960px) {/* Style Three*/}
According to the explanation of these tutorials, the effect of this setting is: when the viewport width is less than or equal to 600px, style one is applied; when the viewport width is greater than or equal to 600px and less than or equal to When 960px, style two is applied; when the viewport width is greater than or equal to 960px, style three is applied. At first glance, there is no problem. Three style effects are set according to different viewport widths, but if you look closely, problems arise. When describing the viewport width above, the logical relationship "equal to" is used. If we only focus on one rule, there is nothing to say, but the two values of 600px and 960px satisfy two rules at the same time, that is, the first rule is less than or equal to 600px, and the second rule is greater than or equal to 600px, so This creates the problem of overlapping conditions. So what happens when the width of the window is exactly at the boundary value of 600px or 960px?
We can conduct a simple experiment. The demo is very simple. The effect achieved is a
Through the above experiments, it was found that when the browser width value is 600px, the effect still stays at the effect of style one. When the width is adjusted to 601px, it will become the effect of style two. That is to say, when a value serves as the upper limit of one condition and the lower limit of another condition, it does not contain an equal relationship for the lower limit condition. In the same way, for the min-width:960px of style 3, its meaning is also when it is greater than 960px, and does not include the case when it is equal to 960px.
There is another situation, for example, we want to change the layout of web page elements under different viewport widths, such as changing the horizontal arrangement to the vertical arrangement. When this kind of page is at a cut-off value of 600px or 960px, the arrangement of page elements will not comply with any of the rules set in CSS. You can try it manually yourself.

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The article discusses the HTML <progress> element, its purpose, styling, and differences from the <meter> element. The main focus is on using <progress> for task completion and <meter> for stati

The article discusses the HTML <datalist> element, which enhances forms by providing autocomplete suggestions, improving user experience and reducing errors.Character count: 159

The article discusses the HTML <meter> element, used for displaying scalar or fractional values within a range, and its common applications in web development. It differentiates <meter> from <progress> and ex

The article discusses the viewport meta tag, essential for responsive web design on mobile devices. It explains how proper use ensures optimal content scaling and user interaction, while misuse can lead to design and accessibility issues.

The article discusses using HTML5 form validation attributes like required, pattern, min, max, and length limits to validate user input directly in the browser.

This article explains the HTML5 <time> element for semantic date/time representation. It emphasizes the importance of the datetime attribute for machine readability (ISO 8601 format) alongside human-readable text, boosting accessibilit

Article discusses best practices for ensuring HTML5 cross-browser compatibility, focusing on feature detection, progressive enhancement, and testing methods.

The article discusses the <iframe> tag's purpose in embedding external content into webpages, its common uses, security risks, and alternatives like object tags and APIs.
