Min property and scroll bug #64
Open
Conversation
This file contains 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
…ax of min and explicit property
…nt fully initializes
|
@Devin-Harris Hi Devin, When can these fixes will be available to us. We are using Katoid in our application. Could you please tell me. So after merging do they need to release this in new version or how it will be. |
I would imagine it would it would be available upon a new release, assuming its good to merge. As far as when that would be you would probably need to ask a maintainer of the repo as I'm not sure what the plan is for future releases. |
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.
Changes for issues described in #63
Change list includes doing width and height calculations off the max between the w and minW properties and the h and minH properties. Also triggering the calculateRenderData method after the content fully inits because the width of the parent was being consumed incorrectly in the ngOnInit method causing items to overflow outside parents bounds causing scroll.