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
Test case. To be dropped in examples/ and images will resolve properly.
examples/
= Grid Wrapping Tests :imagesdir: images/ // reveal.js config :revealjs_hash: true :revealjs_center: false :revealjs_height: 1080 :revealjs_width: 1920 [.columns.wrap] == Should Wrap But Doesn't [.column] * Things here should wrap * But instead images shrink [.column] image::cover.jpg[width=900px] [.column] image::70s.jpg[width=900px]
This looks like this:
If I disable flex-basis on .columns .slide-content > .column it becomes:
flex-basis
.columns .slide-content > .column
Which would be more what I would expect.
However, I wonder if that is a viable fix. @Mogztter any ideas?
The text was updated successfully, but these errors were encountered:
Damn! And now I don't specifically remind why flex-basis was important but I'm pretty sure that if you remove it, it will have some side effects.
To limit impact, we could override it when wrap is enabled:
wrap
.columns.wrap .slide-content > .column { flex-basis: auto; }
I believe auto is the default value: https://developer.mozilla.org/en-US/docs/Web/CSS/flex-basis
auto
Sorry, something went wrong.
Fix to allow wide images in wrapping columns (asciidoctor#353)
9e4491d
Co-authored-by: Guillaume Grossetie <[email protected]>
Successfully merging a pull request may close this issue.
Test case. To be dropped in
examples/
and images will resolve properly.This looks like this:
If I disable
flex-basis
on.columns .slide-content > .column
it becomes:Which would be more what I would expect.
However, I wonder if that is a viable fix. @Mogztter any ideas?
The text was updated successfully, but these errors were encountered: