Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ETA for css-flexbox-2 initial draft #11432

Closed
gitspeaks opened this issue Jan 3, 2025 · 1 comment
Closed

ETA for css-flexbox-2 initial draft #11432

gitspeaks opened this issue Jan 3, 2025 · 1 comment
Labels
Closed as Question Answered Used when the issue is more of a question than a problem, and it's been answered.

Comments

@gitspeaks
Copy link

@astearns Just wondering if there's an estimated timeline for the initial draft of css-flexbox-2. Looking through the issues tagged with css-flexbox-2, it looks like discussions about an update started over 7.5+ years ago. Any concrete date on when this update might actually happen?

Also, I’m not sure if it makes sense to open more issues for css-flexbox-1. I noticed that two issues I opened, #11414 and #11392, didn’t get any tags or were rejected, while my other issues about more "editorial" stuff did get tagged. This got me wondering about where things stand with the Flexbox spec.

Thanks in advance!

@tabatkins
Copy link
Member

Just wondering if there's an estimated timeline for the initial draft of css-flexbox-2.

There is no estimated timeline. We'll draft a new version if/when we have an editor who feels it's a worthwhile thing to spend time on. At the moment, the interested editors (me and @fantasai) are working on other things. In the meantime, the flexbox-2 issues list serves as an archive for us to revisit later.

Also, I’m not sure if it makes sense to open more issues for css-flexbox-1. I noticed that two issues I opened [...] didn't get any tags or were rejected

Those issues were opened around the December holidays, when many of us are either on holiday or working on lowkey projects. It's not unexpected for things to be delayed during this season.

@tabatkins tabatkins added the Closed as Question Answered Used when the issue is more of a question than a problem, and it's been answered. label Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed as Question Answered Used when the issue is more of a question than a problem, and it's been answered.
Projects
None yet
Development

No branches or pull requests

2 participants