fix: Fix info center layout issue #3453
Open
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.
Issue #3450
Change the logic for calculation the initial height of the info center based on the number of currently populated messages. Initially we set the height to be equal to the number of all messages multiplied by 100 which can lead to the described issue when a lot of messages are populated very fast at the start of the application. Each info center message has max 130px of height when the message contains a lot of text. So first it is better to use 130 instead of 100 px in case there is only one message at the start to avoid cutting the message content and to slightly change the height calculation: instead of all messages we use min(allMessagesCount, 3) * 130 - this will create a container initially which can accommodate at most 3 rows with max height - 130px. If the user is not satisfied with the size the splitter can be used for a manual resize.
Testing done: manually verified
