{"id":307873,"date":"2020-04-29T08:50:13","date_gmt":"2020-04-29T15:50:13","guid":{"rendered":"https:\/\/css-tricks.com\/?p=307873"},"modified":"2020-04-29T09:35:26","modified_gmt":"2020-04-29T16:35:26","slug":"david-barons-thoughts-on-an-implementable-path-forward-for-container-queries","status":"publish","type":"post","link":"https:\/\/css-tricks.com\/david-barons-thoughts-on-an-implementable-path-forward-for-container-queries\/","title":{"rendered":"[David Baron’s] Thoughts on an implementable path forward for Container Queries"},"content":{"rendered":"\n
That’s the title of a public post from David Baron, a Principal Engineer at Firefox, with thoughts toward container queries. I know a lot of people have been holding their breath waiting for David’s ideas, as he’s one of few uniquely qualified to understand the ins and outs of this and speak to implementation possibility.<\/p>\n\n\n\n
We’re still in the early stages of container queries. Every web designer and developer wants them, the browsers know it, but it’s a super complicated situation. It was very encouraging in February 2020 to hear positive signals about a possible switch-statement syntax<\/a> that would give us access to an available-inline-size<\/code> used to conditionally set individual values. <\/p>\n\n\n\n