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

CSS blocks page rendering because browsers view inline and external CSS as key resources by default, especially with imported stylesheets, header large amounts of inline CSS, and unoptimized media query styles. 1. Extract critical CSS and embed it into HTML; 2. Delay loading non-critical CSS through JavaScript; 3. Use media attributes to optimize loading such as print styles; 4. Compress and merge CSS to reduce requests. It is recommended to use tools to extract key CSS, combine rel="preload" asynchronous loading, and use media delayed loading reasonably to avoid excessive splitting and complex script control.

ThebestapproachforCSSdependsontheproject'sspecificneeds.Forlargerprojects,externalCSSisbetterduetomaintainabilityandreusability;forsmallerprojectsorsingle-pageapplications,internalCSSmightbemoresuitable.It'scrucialtobalanceprojectsize,performanceneed

CSSismostlycase-insensitive,butURLsandfontfamilynamesarecase-sensitive.1)Propertiesandvalueslikecolor:red;arenotcase-sensitive.2)URLsmustmatchtheserver'scase,e.g.,/images/Logo.png.3)Fontfamilynameslike'OpenSans'mustbeexact.

Autoprefixer is a tool that automatically adds vendor prefixes to CSS attributes based on the target browser scope. 1. It solves the problem of manually maintaining prefixes with errors; 2. Work through the PostCSS plug-in form, parse CSS, analyze attributes that need to be prefixed, and generate code according to configuration; 3. The usage steps include installing plug-ins, setting browserslist, and enabling them in the build process; 4. Notes include not manually adding prefixes, keeping configuration updates, prefixes not all attributes, and it is recommended to use them with the preprocessor.

Theconic-gradient()functioninCSScreatescirculargradientsthatrotatecolorstopsaroundacentralpoint.1.Itisidealforpiecharts,progressindicators,colorwheels,anddecorativebackgrounds.2.Itworksbydefiningcolorstopsatspecificangles,optionallystartingfromadefin

TocreatestickyheadersandfooterswithCSS,useposition:stickyforheaderswithtopvalueandz-index,ensuringparentcontainersdon’trestrictit.1.Forstickyheaders:setposition:sticky,top:0,z-index,andbackgroundcolor.2.Forstickyfooters,betteruseposition:fixedwithbot

The scope of CSS custom properties depends on the context of their declaration, global variables are usually defined in :root, while local variables are defined within a specific selector for componentization and isolation of styles. For example, variables defined in the .card class are only available for elements that match the class and their children. Best practices include: 1. Use: root to define global variables such as topic color; 2. Define local variables inside the component to implement encapsulation; 3. Avoid repeatedly declaring the same variable; 4. Pay attention to the coverage problems that may be caused by selector specificity. Additionally, CSS variables are case sensitive and should be defined before use to avoid errors. If the variable is undefined or the reference fails, the fallback value or default value initial will be used. Debug can be done through the browser developer

CSSanimationsenhancewebpagesbyimprovinguserexperienceandsitefunctionality.1)Usetransitionsforsmoothstylechanges,asinthebuttoncolorexample.2)Employkeyframesfordetailedanimations,likethebouncingball.3)Ensureperformancebykeepinganimationssimpleandusingt
