Uh oh!
There was an error while loading. Please reload this page.
[Android] Fix: setSelection methods is always returned. - #17894
[Android] Fix: setSelection methods is always returned.#17894jainkuniya wants to merge 1 commit into
Conversation
Because mMostRecentEventCount < mNativeEventCount is always true as mMostRecentEventCount is not updated. So determine whether text is set or not from getting current text. Also handle out of bound selection.
pull-bot
commented
Feb 7, 2018
@facebook-github-bot label Needs more information @facebook-github-bot label Android Generated by 🚫 dangerJS |
jainkuniya
commented
Feb 8, 2018
Thanks! @facebook-open-source-bot I have updated and included Test Plan. 👍 :) |
jainkuniya
commented
Feb 12, 2018
hi @janicduplessis please review this PR too. :) |
shergin
left a comment
There was a problem hiding this comment.
How removing mMostRecentEventCount can fix the problem which mMostRecentEventCount is supposed to address?
facebook-github-bot
commented
Mar 19, 2018
@jainkuniya do you have any updates for this pull request? It's been a while since the last update so wanted to check in and see if you've looked at the requested changes. |
cpojer
commented
Jan 29, 2019
Yeah this doesn't seem like the solution we are looking for here. I'm gonna close this PR. |
Motivation
Because mMostRecentEventCount < mNativeEventCount is always true as mMostRecentEventCount is not updated.
So determine whether text is set or not from getting current text. Also handle out of bound selection.
Test Plan
Use this component to test with & without this PR
Before this PR, on clicking Button, nothing will happen.
On this PR: text will be selected starting from 0 and ending at 3. (Just for testing I have barcoded
start&endvalue)Just created a component to test (below).
Current behaviour

This PR

Release Notes
[ANDROID] [BUGFIX] [TextInput] Fix: setSelection methods is always returned.