Skip to content

Fixed MessagesCollectionView's bottom inset when hardware keyboard is…#707

Merged
SD10 merged 9 commits intoMessageKit:developmentfrom
zhongwuzw:fix-bottom-inset
Jun 1, 2018
Merged

Fixed MessagesCollectionView's bottom inset when hardware keyboard is…#707
SD10 merged 9 commits intoMessageKit:developmentfrom
zhongwuzw:fix-bottom-inset

Conversation

@zhongwuzw
Copy link
Member

Closed #568 .
Fixed #562 , Fixed #690 .


messageCollectionViewBottomInset = afterBottomInset

guard !isMessagesControllerBeingDismissed else { return }
Copy link
Member

Choose a reason for hiding this comment

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

@zhongwuzw Ok, I can see how this fixes the dismissal in #562. How does this also solve the hardware keyboard in #690?

Copy link
Member Author

Choose a reason for hiding this comment

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

@SD10 Another way to calculate the bottomInset.

@SD10 SD10 changed the base branch from master to development June 1, 2018 04:40
@SD10 SD10 changed the base branch from development to bugix/messageinputbar June 1, 2018 04:40
@SD10 SD10 changed the base branch from bugix/messageinputbar to development June 1, 2018 04:41
@SD10 SD10 changed the base branch from development to master June 1, 2018 04:41
@SD10
Copy link
Member

SD10 commented Jun 1, 2018

Sorry, GitHub UI malfunction 😂 @zhongwuzw do you think we could point this at development instead? I still need to release the official 1.0, just waiting for my company to migrate from our custom fork of MessageKit.

@SD10 SD10 mentioned this pull request Jun 1, 2018
@zhongwuzw
Copy link
Member Author

@SD10 It's ok, not big bug. I'll switch to development and merge it.

@zhongwuzw zhongwuzw changed the base branch from master to development June 1, 2018 09:58
@SD10 SD10 merged commit 46bebec into MessageKit:development Jun 1, 2018
@SD10
Copy link
Member

SD10 commented Jun 1, 2018

@zhongwuzw Great thanks 👌 We have to do a better job of keeping master and development in sync so that this doesn't happen, but the blame is on me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants