CSS container query has always been one of the features that developers strongly demand improvement. It is a general view that if we have container queries, we don't need to write so many global media queries based on page size. Because what we really want to control is a more local container, and now we can only implement it using media queries, simply because it is the best tool in CSS. I totally agree with this.
But there is also a view that appears from time to time: "Developers think that container queries are needed, but they are not." I don't agree with this statement. If the container query is available, we can obviously do a lot of useful things with it, the most important of which is to write cleaner, easier to port, easier to understand code. It seems to be a consensus to build component-based UIs today, which makes the demand for container queries even more obvious.
There are currently some modern JavaScript methods that can help us use container queries today - but that doesn't mean that this technology needs to stay in the JavaScript realm. It makes more sense in CSS.
Here are some of my thoughts on this topic at the end of 2019:
- Philip Walton's "Responsive Components: Solutions to Solve Container Query Problems" shows a good way to use JavaScript's ResizeObserver to solve the current problem. It performs well and works anywhere. The demo website is the best one because it highlights the needs of responsive components (although there are other documented use cases). Philip even says pure CSS solutions would be more ideal.
- About a year ago, CSS nesting caused a craze. Discussions seem to show that nesting is feasible. As a longtime advocate for rational Sass nesting, I agree with that. This makes me wonder whether the syntax of container query can take advantage of something similar. Maybe the scope of nested queries is limited to the parent selector? Or do you use an ampersand as prefix to represent media statements, as the current specification does with descendant selectors?
- Other proposed syntaxes usually involve the use of some kind of colon, such as
.container:media(max-width: 400px) { }
. I like this, too. Single colon selectors (pseudo-selectors) are philosophically "selecting elements under these conditions" - for example:hover
,:nth-child
, etc. - so media scope makes sense. - I don't think syntax is the biggest obstacle to this feature; it's its implementation performance. As far as I know last, it's even more of a performance issue, it's disrupting the entire rendering process of how the browser works. This seems to be a huge obstacle. But I still don't want to forget it. There are a lot of innovations happening on the Internet, and just because it’s not clear how to achieve it today doesn’t mean that tomorrow no one will find a viable way forward.
The above is the detailed content of Let's Not Forget About Container Queries. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

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

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

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

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

There are three ways to create a CSS loading rotator: 1. Use the basic rotator of borders to achieve simple animation through HTML and CSS; 2. Use a custom rotator of multiple points to achieve the jump effect through different delay times; 3. Add a rotator in the button and switch classes through JavaScript to display the loading status. Each approach emphasizes the importance of design details such as color, size, accessibility and performance optimization to enhance the user experience.

To deal with CSS browser compatibility and prefix issues, you need to understand the differences in browser support and use vendor prefixes reasonably. 1. Understand common problems such as Flexbox and Grid support, position:sticky invalid, and animation performance is different; 2. Check CanIuse confirmation feature support status; 3. Correctly use -webkit-, -moz-, -ms-, -o- and other manufacturer prefixes; 4. It is recommended to use Autoprefixer to automatically add prefixes; 5. Install PostCSS and configure browserslist to specify the target browser; 6. Automatically handle compatibility during construction; 7. Modernizr detection features can be used for old projects; 8. No need to pursue consistency of all browsers,

Use the clip-path attribute of CSS to crop elements into custom shapes, such as triangles, circular notches, polygons, etc., without relying on pictures or SVGs. Its advantages include: 1. Supports a variety of basic shapes such as circle, ellipse, polygon, etc.; 2. Responsive adjustment and adaptable to mobile terminals; 3. Easy to animation, and can be combined with hover or JavaScript to achieve dynamic effects; 4. It does not affect the layout flow, and only crops the display area. Common usages are such as circular clip-path:circle (50pxatcenter) and triangle clip-path:polygon (50%0%, 100 0%, 0 0%). Notice

Themaindifferencesbetweendisplay:inline,block,andinline-blockinHTML/CSSarelayoutbehavior,spaceusage,andstylingcontrol.1.Inlineelementsflowwithtext,don’tstartonnewlines,ignorewidth/height,andonlyapplyhorizontalpadding/margins—idealforinlinetextstyling

Setting the style of links you have visited can improve the user experience, especially in content-intensive websites to help users navigate better. 1. Use CSS's: visited pseudo-class to define the style of the visited link, such as color changes; 2. Note that the browser only allows modification of some attributes due to privacy restrictions; 3. The color selection should be coordinated with the overall style to avoid abruptness; 4. The mobile terminal may not display this effect, and it is recommended to combine it with other visual prompts such as icon auxiliary logos.

TheCSSPaintingAPIenablesdynamicimagegenerationinCSSusingJavaScript.1.DeveloperscreateaPaintWorkletclasswithapaint()method.2.TheyregisteritviaregisterPaint().3.ThecustompaintfunctionisthenusedinCSSpropertieslikebackground-image.Thisallowsfordynamicvis

To create responsive images using CSS, it can be mainly achieved through the following methods: 1. Use max-width:100% and height:auto to allow the image to adapt to the container width while maintaining the proportion; 2. Use HTML's srcset and sizes attributes to intelligently load the image sources adapted to different screens; 3. Use object-fit and object-position to control image cropping and focus display. Together, these methods ensure that the images are presented clearly and beautifully on different devices.

Different browsers have differences in CSS parsing, resulting in inconsistent display effects, mainly including the default style difference, box model calculation method, Flexbox and Grid layout support level, and inconsistent behavior of certain CSS attributes. 1. The default style processing is inconsistent. The solution is to use CSSReset or Normalize.css to unify the initial style; 2. The box model calculation method of the old version of IE is different. It is recommended to use box-sizing:border-box in a unified manner; 3. Flexbox and Grid perform differently in edge cases or in old versions. More tests and use Autoprefixer; 4. Some CSS attribute behaviors are inconsistent. CanIuse must be consulted and downgraded.
