We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Commit b6c01a4 makes align-content: stretch fallback to safe flex-start in css-flexbox-1 https://drafts.csswg.org/css-flexbox-1/#valdef-align-content-stretch, which is not consistent with the fallback flex-start specifying in css-align-3 https://drafts.csswg.org/css-align-3/#valdef-align-content-stretch.
align-content: stretch
safe flex-start
flex-start
Is this an editorial error or intentional?
The text was updated successfully, but these errors were encountered:
I have a PR #11554 to fix the flexbox spec if this is just an error.
Sorry, something went wrong.
<!DOCTYPE html> <div style="display: inline-flex; border: solid; height: 50px; flex-wrap: wrap-reverse; align-content: stretch"> <div style="width: 100px; height: 100px; background: cyan"></div> </div> <div style="display: inline-flex; border: solid; height: 50px; flex-wrap: wrap-reverse; align-content: flex-start"> <div style="width: 100px; height: 100px; background: cyan"></div> </div> <div style="display: inline-flex; border: solid; height: 50px; flex-wrap: wrap-reverse; align-content: safe flex-start"> <div style="width: 100px; height: 100px; background: cyan"></div> </div>
Gecko, Blink and WebKit use flex-start. Servo uses safe flex-start.
No branches or pull requests
Commit b6c01a4 makes
align-content: stretch
fallback tosafe flex-start
in css-flexbox-1 https://drafts.csswg.org/css-flexbox-1/#valdef-align-content-stretch, which is not consistent with the fallbackflex-start
specifying in css-align-3 https://drafts.csswg.org/css-align-3/#valdef-align-content-stretch.Is this an editorial error or intentional?
The text was updated successfully, but these errors were encountered: