-
Notifications
You must be signed in to change notification settings - Fork 10
Should we archive this repo? #14
Comments
yeah, I'd archive it, at least for now. |
I've been in quite a few conversations with browser folks about Container Queries recently. They are still in high demand and people still very much want them. I think before closing, it'd be nice to have an official postmortem post on where we're at on this. Something like: Accomplishments
Progress on features that were said to be blocking Container Queries:
Author sentiment Still very much in high demand.
Browser sentiment
(It would be awesome if browsers could state their official position before departing) |
That's great @davatron5000 - and really insightful. I know Mozilla's CSS standards folks are passionate about this, as are our dev rel folks. I'll see if I can push our folks internally for a formal position: mozilla/standards-positions#118 I'd really like to hear from other folks here too, as @davatron5000 suggested. |
Agree with @davatron5000. If this repo isn't the best place for work on this to continue, that's fine, I just hope the work continues somewhere. This feature has remained in such demand from developers for so long now that talking about it has become a cliché. Last I heard, folks at Moz and Chrome were actively looking at it, so I'm hopeful that's still the case. Thanks! |
Also, CSS-Tricks published an article recently talking about container queries https://css-tricks.com/the-origin-story-of-container-queries/. |
@cwilso or @yoavweiss, who might be good to talk to on Chromium/Blink side? |
/cc @stubbornella |
mmmmmmmm...... let's not just yet. Who knows what the new year will bring :) |
Given that this is now in CSS proper, we should archive this now. Discussion on further improvements to container queries should happen in the CSS WG. |
Congratulation to everyone involved here, I believe efforts like these moved the needle after a decade's persistence! 😁 |
Hi y'all... given that lack of activity in over a year, it might be time to concede defeat on this and "archive" this incubation.
Although we've not managed to solve this exactly problem on the Web, would it be fair to say that we have a set of capabilities on the web that are helping solve some the same problems (e.g., CSS grid and sub-grid)?
What do you all think? Or should we try to keep going? We can always un-archive later.
cc @WICG/chairs
The text was updated successfully, but these errors were encountered: