Skip to content
This repository was archived by the owner on Mar 7, 2025. It is now read-only.

Conversation

ceyhun
Copy link

@ceyhun ceyhun commented Jun 18, 2021

No description provided.

pinarol and others added 30 commits December 25, 2018 15:37
This is added because we shouldn't always use extraScrollHeight to
calculate the bottom inset of the content when keyboard is open.
Some unwanted bottom inset occurs if we do.
Add prop extraBottomInset to fix the unwanted bottom inset
This includes orientation change etc. We don't need to get different values for landscape/portrait modes from outside anymore.
This sometimes happens if device orientation changes
Co-Authored-By: pinarol <pinarolguc@gmail.com>
Add scroll ability relative to caret position when keyboard is open
We don't need any scrolling delay in case we trigger scroll programmatically.
We can trigger the scroll programmatically by directly calling refreshScrollForField
Open a method to refresh the scroll due to caret
We are putting a delay until caret position is available. It is probably becoming available
after the height is adjusted and caret is viewable.
Fix textinput caret position, y position and height calculating wrongly
Fix waiting on caret rect detection when caret is at the end
pinarol and others added 30 commits March 21, 2019 15:48
…r-other-viewcontrollers

Replace isDescendant check with a more decent one
…raph

Improve scroll calculations with caret under keyboard at mid paragraph
The exact error is:
ERROR    Warning: Functions are not valid as a React child. This may happen if you return a Component instead of <Component /> from render. Or maybe you meant to call this function rather than return it.
    in Unknown (at keyboard-aware-flat-list/index.ios.js:23)
This fixes the console error:
currentlyFocusedField is deprecated and will be removed in a future release. Use currentlyFocusedInput
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants