Use cases and requirements for standardizing element queries.
HTML
Latest commit 79c096c Jun 5, 2015 @marcoscaceres marcoscaceres Merge pull request #34 from wnr/patch-1
Fixed broken links in Readme.
Permalink
Failed to load latest commit information.
images
.editorconfig
.vimrc.local
CONTRIBUTING.md
README.md Fixed broken links in Readme. Jun 5, 2015
biblio.json
index.bs
index.html
tidyconfig.txt

README.md

Use Cases and Requirements for “Container Queries”

Given a complex responsive layout, developers often require a more granular level of control over how the contents of an individual module will respond relative to the size of their parent container rather than the viewport size. This is prohibitive to the goal of creating modular, independent components, often requiring a number of redundant CSS, complex exception cases, and workarounds, and the problem compounds itself depending on how dramatically a module adapts at each of its breakpoints.

This document aims to present some of the use cases that an “element query” syntax would solve, by allowing authors to define layouts within an individual module on the basis of the size of the module itself, rather than the viewport.

The spec proper can be found at https://responsiveimagescg.github.io/cq-usecases/.

Found a bug? Want to contribute something?

If you found a problem with the document, no matter how small, please file a bug.

See also our contributor's guide.

Proposals for normative changes to this document should take place on the RICG mailing list.

Join us!

Join the RICG and help make the Web a better place for images everything.