-
Notifications
You must be signed in to change notification settings - Fork 58
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
Media & Text - Alignment #1312
Comments
This came up in 13.5 beta testing. Steps to reproduce:
Result: horizontal alignment options don't work in the Media & Text block. It's quite easy to spot on iPad. (26s) /hat tip @rachelmcr for the report (internal reference: p5T066-136-p2#comment-3658) |
I was investigating this on Friday, and what I know so far is that we have code in place to make this work, and that in a way it's doing what's expected. When you align some items vertically you'd expect to see something like this: However, there is something making the media container and the inner blocks 100% tall, so even if they're actually aligned, there's no visual difference: I started investigating the nested BlockList because I thought maybe that was problematic. Normally you want to specify a fixed height for a scroll view so its container view is bounded, and it can scroll when the content size is larger than the container: However, I started a sample project with nested FlatList and it was working fine: https://snack.expo.io/@kokejb/scrollview-flexbox (I'd recommend testing on an iPad) I noticed that FlatList is smart enough to detect when it's nested, and instead of adding a second ScrollView, it will use the context of the parent one. Our Also, our media container is using I started #1502, which doesn't have much yet, but the sample content is useful for testing all the cases. |
Media & Text block text part is not aligning due to alignment options.
Since text is shorter than media in this case it is expected that it moves:
Expected behaviour:
Text part is aligned similar to web:
The text was updated successfully, but these errors were encountered: