Hasty Treat - The Status of Element Queries / Container Queries

Syntax - Tasty Web Development Treats - Een podcast door Wes Bos & Scott Tolinski - Full Stack JavaScript Web Developers

Probeer Podimo de eerste 30 dagen gratis gratis

Luister 30 dagen gratis naar exclusieve podcasts en duizenden luisterboeken

Sponsored

Categorieën:

Technologie

In this Hasty Treat, Scott and Wes talk about container queries, what they are and how you can use them.

Sentry - Sponsor

If you want to know what’s happening with your errors, track them with Sentry. Sentry is open-source error tracking that helps developers monitor and fix crashes in real time. Cut your time on error resolution from five hours to five minutes. It works with any language and integrates with dozens of other services. Syntax listeners can get two months for free by visiting Sentry.io and using the coupon code “tastytreat”.

Show Notes

4:30 - The General Idea

6:20 - Problems

  • It’s not as easy as, “how do we write them”
  • Some of the requirements may need a fundamental change to browser engines
    • May be very impractical and take a long time

“Did you know, for example, that there are multiple many year long efforts with huge investments underway already aimed at unlocking many new things in CSS? There are - and I don’t mean Houdini!” ~ Brian Kardell

8:56 - What’s been happening?

  • Lots of conversations
  • Dead ends

“How do we make this into more solvable problems?” and “How do we actually make some progress, mitigate risk - take a step, and and actually get something to developers?” ~ Brian Kardell

12:00 - Progress

  • Lot’s of discussion
    • Goog, Moz, Apple, smart people
  • Not there yet
  • Big ideas that could go somewhere

.foo { display: grid; grid-template-columns: switch( (available-inline-size > 1024px) 1fr 4fr 1fr; (available-inline-size > 400px) 2fr 1fr; (available-inline-size > 100px) 1fr; default 1fr; ); }

“A whole lot of the problems with existing ideas is that they heave to loop back through (expensive) phases potentially several times and make it (seemingly) impossible to keep CSS rendering in the same frame.” ~ Brian Kardell

  • Or a system based on resizeObserver

“In the coming months I hope to continue to think about, explore this space and continue discussions with others. I would love to publish some research and maybe some new (functional) experiments with JS that aim to be ‘closer’ to a path that might be paveable.” ~ Brian Kardell

Links

Tweet us your tasty treats!

Visit the podcast's native language site