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

Fix bug where absolute nodes were not insetted correctly in certain cases #43417

Closed
wants to merge 1 commit into from

Conversation

joevilches
Copy link
Contributor

Summary: There was a bug where we did not position absolute nodes correctly if the static node had a different main/cross axis from the containing node. This fixes that. The change is somewhat complicated unfortunately but I tried to add sufficient comments to explain what is happening

Reviewed By: NickGerleman

Differential Revision: D54703955

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Mar 11, 2024
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D54703955

joevilches added a commit to joevilches/yoga that referenced this pull request Mar 11, 2024
…ases

Summary:
X-link: facebook/react-native#43417

There was a bug where we did not position absolute nodes correctly if the static node had a different main/cross axis from the containing node. This fixes that. The change is somewhat complicated unfortunately but I tried to add sufficient comments to explain what is happening

Reviewed By: NickGerleman

Differential Revision: D54703955
joevilches added a commit to joevilches/react-native that referenced this pull request Mar 11, 2024
…ases (facebook#43417)

Summary:

There was a bug where we did not position absolute nodes correctly if the static node had a different main/cross axis from the containing node. This fixes that. The change is somewhat complicated unfortunately but I tried to add sufficient comments to explain what is happening

Reviewed By: NickGerleman

Differential Revision: D54703955
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D54703955

…ases (facebook#43417)

Summary:
X-link: facebook/yoga#1593


There was a bug where we did not position absolute nodes correctly if the static node had a different main/cross axis from the containing node. This fixes that. The change is somewhat complicated unfortunately but I tried to add sufficient comments to explain what is happening

Reviewed By: NickGerleman

Differential Revision: D54703955
joevilches added a commit to joevilches/yoga that referenced this pull request Mar 12, 2024
…ases (facebook#1593)

Summary:

X-link: facebook/react-native#43417

There was a bug where we did not position absolute nodes correctly if the static node had a different main/cross axis from the containing node. This fixes that. The change is somewhat complicated unfortunately but I tried to add sufficient comments to explain what is happening

Reviewed By: NickGerleman

Differential Revision: D54703955
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D54703955

facebook-github-bot pushed a commit to facebook/litho that referenced this pull request Mar 12, 2024
…ases

Summary:
X-link: facebook/yoga#1593

X-link: facebook/react-native#43417

There was a bug where we did not position absolute nodes correctly if the static node had a different main/cross axis from the containing node. This fixes that. The change is somewhat complicated unfortunately but I tried to add sufficient comments to explain what is happening

Reviewed By: NickGerleman

Differential Revision: D54703955

fbshipit-source-id: 096c643f61d4f9bb3ee6278d675ebd69b57350d7
facebook-github-bot pushed a commit to facebook/yoga that referenced this pull request Mar 12, 2024
…ases (#1593)

Summary:
Pull Request resolved: #1593

X-link: facebook/react-native#43417

There was a bug where we did not position absolute nodes correctly if the static node had a different main/cross axis from the containing node. This fixes that. The change is somewhat complicated unfortunately but I tried to add sufficient comments to explain what is happening

Reviewed By: NickGerleman

Differential Revision: D54703955

fbshipit-source-id: 096c643f61d4f9bb3ee6278d675ebd69b57350d7
@facebook-github-bot facebook-github-bot added the Merged This PR has been merged. label Mar 12, 2024
@facebook-github-bot
Copy link
Contributor

This pull request has been merged in 3341ab7.

NickGerleman pushed a commit to facebook/yoga that referenced this pull request Mar 13, 2024
…ases (#1593)

Summary:
Pull Request resolved: #1593

X-link: facebook/react-native#43417

There was a bug where we did not position absolute nodes correctly if the static node had a different main/cross axis from the containing node. This fixes that. The change is somewhat complicated unfortunately but I tried to add sufficient comments to explain what is happening

Reviewed By: NickGerleman

Differential Revision: D54703955

fbshipit-source-id: 096c643f61d4f9bb3ee6278d675ebd69b57350d7
huntie pushed a commit that referenced this pull request Mar 18, 2024
…ases (#43417)

Summary:
X-link: facebook/yoga#1593

Pull Request resolved: #43417

There was a bug where we did not position absolute nodes correctly if the static node had a different main/cross axis from the containing node. This fixes that. The change is somewhat complicated unfortunately but I tried to add sufficient comments to explain what is happening

Reviewed By: NickGerleman

Differential Revision: D54703955

fbshipit-source-id: 096c643f61d4f9bb3ee6278d675ebd69b57350d7
This was referenced Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported Merged This PR has been merged. p: Facebook Partner: Facebook Partner
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants