fix: preserve Stack direct child flex semantics - #71
Merged
Conversation
This was referenced Aug 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #70.
Refs ankhorage/zora#289.
Stackused wrapperViews to synthesize spacing between children. Those wrappers became the actual flex items and prevented authored child layout props such asflex,minHeight,minWidth, andalignSelffrom participating directly in the Stack layout.This PR makes Stack spacing container-owned:
gapstyle on the Stack container;Viewpath entirely;This is the Surface-owned primitive fix required by the cross-platform viewport contract in ankhorage/zora#289. No compatibility or fallback path is added.