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/106 #111

Merged
merged 3 commits into from Dec 4, 2016
Merged

Fix/106 #111

merged 3 commits into from Dec 4, 2016

Conversation

joshwcomeau
Copy link
Owner

Fixes #106
(although it's really more of a band-aid than a proper fix)

@joshwcomeau joshwcomeau added the bug label Dec 4, 2016
@joshwcomeau joshwcomeau self-assigned this Dec 4, 2016
removeNodeFromDOMFlow(childData);
if (childData.boundingBox) {
removeNodeFromDOMFlow(childData);
}
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The obvious solution here is to just recalculate the bounding box if it's missing. Sadly, this doesn't work, for reasons I don't understand or have time to dig into; it does recalculate the bounding boxes, but it causes the elements to reshape in weird ways.

@joshwcomeau joshwcomeau merged commit fd380b0 into master Dec 4, 2016
@joshwcomeau joshwcomeau deleted the fix/106 branch December 4, 2016 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot read property 'top' of undefined / 'getBoundingClientRect' of null
1 participant