By andreaswienes


2015-09-23 20:17:51 8 Comments

I defined two TextInput fields as follows:

<TextInput 
   style = {styles.titleInput}
   returnKeyType = {"next"}
   autoFocus = {true}
   placeholder = "Title" />
<TextInput
   style = {styles.descriptionInput}          
   multiline = {true}
   maxLength = {200}
   placeholder = "Description" />

But after pressing the "next" button on my keyboard, my react-native app isn't jumping to the second TextInput field. How can I achieve that?

Thanks!

16 comments

@Mohamed Ben Hartouz 2019-01-09 11:09:06

If you are using NativeBase as UI Components you can use this sample


         <Item floatingLabel>
              <Label>Title</Label>
              <Input
              returnKeyType = {"next"}
              autoFocus = {true}
              onSubmitEditing={(event) => {
                  this._inputDesc._root.focus(); 
              }}
              />
          </Item>
          <Item floatingLabel>
              <Label>Description</Label>
              <Input
              getRef={(c) => this._inputDesc = c}
              multiline={true} style={{height: 100}} />
              onSubmitEditing={(event) => { this._inputLink._root.focus(); }}
          </Item>```

@Janaka Pushpakumara 2018-07-10 09:53:02

This is the way I achieved it. And the example below has used the React.createRef() API introduced in React 16.3.

class Test extends React.Component {
  constructor(props) {
    super(props);
    this.secondTextInputRef = React.createRef();
  }

  render() {
    return(
        <View>
            <TextInput
                placeholder = "FirstTextInput"
                returnKeyType="next"
                onSubmitEditing={() => { this.secondTextInputRef.current.focus(); }}
            />
            <TextInput
                ref={this.secondTextInputRef}
                placeholder = "secondTextInput"
            />
        </View>
    );
  }
}

I think this will help you.

@boredgames 2015-09-24 05:08:59

Set the second TextInput focus, when the previous TextInput's onSubmitEditing is triggered.

Try this

  1. Adding a Ref to second TextInput
    ref={(input) => { this.secondTextInput = input; }}

  2. Bind focus function to first TextInput's onSubmitEditing event.
    onSubmitEditing={() => { this.secondTextInput.focus(); }}

  3. Remember to set blurOnSubmit to false, to prevent keyboard flickering.
    blurOnSubmit={false}

When all done, it should looks like this.

<TextInput
    placeholder = "FirstTextInput"
    returnKeyType = { "next" }
    onSubmitEditing={() => { this.secondTextInput.focus(); }}
    blurOnSubmit={false}
/>

<TextInput
    ref={(input) => { this.secondTextInput = input; }}
    placeholder = "secondTextInput"
/>

@e1dar 2016-08-01 17:37:31

Worth to mention, that onSubmitEditing callback is called after blur event. So the keyboard may go crazy if focused on next element immediately. So it might be helpful to set blurOnSubmit={false} to all elements in form but leave at true on last element, to allow Done button to blur the last input.

@Mitch 2016-11-01 05:56:03

This doesn't work anymore, as of v0.36. There is no method "focus" on the component. How should we do this now?

@tarkanlar 2016-11-27 19:44:54

@Mitch could you find an answer for this?

@Mitch 2016-11-28 04:47:30

@tarkanlar Yes. My solution feels like a hack, but I think it is the best solution available right now. See my answer below.

@vikki 2017-02-06 06:24:16

@Mitch works fine on 0.40.0. Might have been a bug in the version you were running.

@Ravi Mishra 2017-04-04 09:54:19

Use funcution setFocus() instead focus()

@jasan 2017-06-15 20:54:32

this.refs.SecondInput.focus(); or this.refs.SecondInput.setFocus(); do not work . Using react-native 0.45.1

@Olivia 2017-07-04 15:31:46

@jasan it worked for me. Make sure to use onEndEditing instead of onSubmitEditing.

@roadev 2017-07-13 02:27:29

I have just one input and I need to focus itself after each submit but I'm still trying to achieve it. Some idea? I'm using the example in facebook.github.io/react/docs/refs-and-the-dom.html for RN 0.44. onEndEditing doesn't work to me because I have other buttons in the view that need to keep working.

@MattyK14 2017-07-13 12:59:06

@jasan @Olivia I'm using onSubmitEditing on react-native 0.45.1 just fine.

@Adnan Ali 2017-10-22 09:24:32

How can we focus react-native Picker?

@achu 2017-10-24 07:29:47

i am using this same code but not working

@achu 2017-10-24 07:54:31

I am using react-native : 0.48.4 this sample code is not working @boredgames

@nabil london 2017-11-09 00:12:11

Using RN 0.49, adding blurOnSubmit={false} to prevent keyboard flickering caused this to stop working, any one that knows what's going on?

@Walter Monecke 2017-12-20 09:54:40

Tried this in RN 0.47 aaaaand... IT WORKS!

@Cihad Turhan 2018-01-27 00:18:36

For anyone who couldn't manage to make focus work, make sure you don't use a wrapper for TextInput component. If you have a say CustomTextInput component that wraps TextInput, you need to implement TextInput blur and focus methods for that component so it will work as expected.

@Bap 2018-02-24 23:53:42

Works with 0.53

@Rishabh Bhardwaj 2018-04-11 12:21:37

how can we add next button in keyboard with keyboardType=phone-pad''??

@DeveloperACE 2018-07-16 00:17:31

@RishabhBhardwaj i believe phone pad does not have a next button

@Dmitry 2018-01-16 08:48:36

For me on RN 0.50.3 it's possible with this way:

<TextInput 
  autoFocus={true} 
  onSubmitEditing={() => {this.PasswordInputRef._root.focus()}} 
/>

<TextInput ref={input => {this.PasswordInputRef = input}} />

You must see this.PasswordInputRef._root.focus()

@Developia 2018-08-30 07:44:59

This is 'native-base' specific

@Rodrigo Tessarollo 2018-01-16 03:34:50

My scenario is < CustomBoladonesTextInput /> wrapping a RN < TextInput />.

I solved this issue as follow:

My form looks like:

  <CustomBoladonesTextInput 
      onSubmitEditing={() => this.customInput2.refs.innerTextInput2.focus()}
      returnKeyType="next"
      ... />

  <CustomBoladonesTextInput 
       ref={ref => this.customInput2 = ref}
       refInner="innerTextInput2"
       ... />

On CustomBoladonesTextInput's component definition, I pass the refField to the inner ref prop like this:

   export default class CustomBoladonesTextInput extends React.Component {
      render() {        
         return (< TextInput ref={this.props.refInner} ... />);     
      } 
   }

And voila. Everything get back works again. Hope this helps

@amorenew 2017-09-18 08:22:57

in your component:

constructor(props) {
        super(props);
        this.focusNextField = this
            .focusNextField
            .bind(this);
        // to store our input refs
        this.inputs = {};
    }
    focusNextField(id) {
        console.log("focus next input: " + id);
        this
            .inputs[id]
            ._root
            .focus();
    }

Note: I used ._root because it is a ref to TextInput in NativeBase'Library' Input

and in your text inputs like this

<TextInput
         onSubmitEditing={() => {
                          this.focusNextField('two');
                          }}
         returnKeyType="next"
         blurOnSubmit={false}/>


<TextInput      
         ref={input => {
              this.inputs['two'] = input;
                        }}/>

@zackify 2017-08-02 19:47:45

I created a small library that does this, no code change needed other than replacing your wrapping view and import of TextInput:

import { Form, TextInput } from 'react-native-autofocus'

export default () => (
  <Form>
    <TextInput placeholder="test" />
    <TextInput placeholder="test 2" />
  </Form>
)

https://github.com/zackify/react-native-autofocus

Explained in detail here: https://zach.codes/autofocus-inputs-in-react-native/

@Jack Robson 2017-08-21 22:42:50

Excellent pattern for achieving this result. Should be top answer from ease of use stand point. Looks like I can easily edit my custom FormInput (TextInput extensions) to still work with your Form inputs. Mind if I include it to your answer if for further example?

@zackify 2017-08-22 03:02:39

Sure! I know... I posted this on the other popular post about this but got in trouble for duplicates. Just trying to help because I know how annoying this problem is!!

@GenericJam 2017-10-23 02:26:28

This is great if you have a bunch of TextInputs right after each other but if you want to add styling between them it breaks down. Thanks for the contribution though.

@zackify 2017-10-23 04:45:27

Feel free to adjust the code. I’m sure you could make a way that would skip over elements that are not text inputs. Shouldn’t be too hard to do.

@Phil Andrews 2017-12-28 10:39:45

This does not build for production [email protected]

@zackify 2018-01-09 16:33:19

Feel free to make a pr, I'll check it out when i get some free time!

@ROI 2018-09-10 04:22:38

Excellent Work!

@kuhr 2017-07-22 09:51:02

Using react-native 0.45.1 I also encountered problems trying to set focus on a password TextInput after pressing return key on a username TextInput.

After having tried most of the top rated solutions here on SO I found a solution on github that fulfilled my needs: https://github.com/shoutem/ui/issues/44#issuecomment-290724642

To sum it up:

import React, { Component } from 'react';
import { TextInput as RNTextInput } from 'react-native';

export default class TextInput extends Component {
    render() {
        const { props } = this;

        return (
            <RNTextInput
                {...props}
                ref={(input) => props.inputRef && props.inputRef(input)}
            />
        );
    }
}

And then I use it like this:

import React, {Component} from 'react';
import {
    View,
} from 'react-native';
import TextInput from "../../components/TextInput";

class Login extends Component {
    constructor(props) {
        super(props);
        this.passTextInput = null
    }

    render() {
        return (
            <View style={{flex:1}}>
                <TextInput
                    style={{flex:1}}
                    placeholder="Username"
                    onSubmitEditing={(event) => {
                        this.passTextInput.focus()
                    }}
                />

                <TextInput
                    style={{flex:1}}
                    placeholder="Password"
                    inputRef={(input) => {
                        this.passTextInput = input
                    }}
                />
            </View>
        )
    }
}

@JaysQubeXon 2017-11-18 16:01:03

Your solution work for me. Thanks!

@John Lim 2018-01-02 10:19:28

this is the only solution that work on me

@tokinonagare 2018-10-11 08:49:57

You save my life : )

@Eldelshell 2016-12-17 18:48:02

For the accepted solution to work if your TextInput is inside another component, you'll need to "pop" the reference from ref to the parent container.

// MyComponent
render() {
    <View>
        <TextInput ref={(r) => this.props.onRef(r)} { ...this.props }/>
    </View>
}

// MyView
render() {
    <MyComponent onSubmitEditing={(evt) => this.myField2.focus()}/>
    <MyComponent onRef={(r) => this.myField2 = r}/>
}

@Liang 2017-06-12 11:29:59

Hi @Eldelshell, I would like to achieve the same thing, but could not sort out your sample, would you mind show us a hint?

@David Cheung 2018-02-01 09:06:25

I think this should be the correct answer. I follow this and it works.

@DeveloperACE 2018-07-16 00:16:24

are these both in the same file?

@Mitch 2016-11-28 04:46:35

As of React Native 0.36, calling focus() (as suggested in several other answers) on a text input node isn't supported any more. Instead, you can use the TextInputState module from React Native. I created the following helper module to make this easier:

// TextInputManager
//
// Provides helper functions for managing the focus state of text
// inputs. This is a hack! You are supposed to be able to call
// "focus()" directly on TextInput nodes, but that doesn't seem
// to be working as of ReactNative 0.36
//
import { findNodeHandle } from 'react-native'
import TextInputState from 'react-native/lib/TextInputState'


export function focusTextInput(node) {
  try {
    TextInputState.focusTextInput(findNodeHandle(node))
  } catch(e) {
    console.log("Couldn't focus text input: ", e.message)
  }
}

You can, then, call the focusTextInput function on any "ref" of a TextInput. For example:

...
<TextInput onSubmit={() => focusTextInput(this.refs.inputB)} />
<TextInput ref="inputB" />
...

@tarkanlar 2016-11-28 15:03:18

I couldn't make this work maybe because I use redux-form

@tarkanlar 2016-11-28 22:18:49

Works awesome but if anyone uses redux-form should do something like this. <Field ... onSubmitEditing={() => focusTextInput(this._password)} /> and ref should be like this <Field ... withRef refName={e => this._password = e}/>

@Adam Jakiela 2016-12-21 14:55:56

I had to use 'onSubmitEditing' to make this work but great solution none the less.

@lawrence 2017-03-09 21:20:36

Works great in 0.42.

@jasan 2017-06-16 08:14:54

@tarkanlar can you share code snippet for the solution? I can't seem to focus when using redux-form Field, using just TextInput works, fine

@Sound Blaster 2017-08-10 10:05:34

Works with 0.46

@bds 2017-10-13 17:27:50

Works in 0.46 with a small change: import * as TextInputState from 'react-native/lib/TextInputState'

@tanguy_k 2017-10-31 00:27:31

calling focus() on a text input node isn't supported any more => bold claim, source? Calling focus() works fine with v0.49.5 + TextInputState is not documented while focus() and blur() are mentioned: facebook.github.io/react-native/releases/next/docs/…

@Mitch 2017-11-09 16:51:14

@tanguy_k My source is the RN source code as of v0.36 . It seems that this has been addressed in later versions of RN.

@riqitang 2019-01-10 15:46:05

I can confirm that focus() works with RN 0.57, I got it to work very similarly to this answer: onSubmitEditing={() => (this.refs.password as TextInput).focus()}

@fagerbua 2016-11-11 12:17:24

Using callback refs instead of the legacy string refs:

<TextInput
    style = {styles.titleInput}
    returnKeyType = {"next"}
    autoFocus = {true}
    placeholder = "Title"
    onSubmitEditing={() => {this.nextInput.focus()}}
/>
<TextInput
    style = {styles.descriptionInput}  
    multiline = {true}
    maxLength = {200}
    placeholder = "Description"
    ref={nextInput => this.nextInput = nextInput}
/>

@Jacob Lauritzen 2017-03-16 08:51:11

Doesn't work as the focus-method has been removed from TextInput.

@marius 2016-09-06 08:18:00

There is a way to capture tabs in a TextInput. It's hacky, but better than nothing.

Define an onChangeText handler that compares the new input value with the old, checking for a \t. If one is found, advance the field as shown by @boredgames

Assuming the variable username contains the value for the username and setUsername dispatches an action to change it in the store (component state, redux store, etc), do something like this:

function tabGuard (newValue, oldValue, callback, nextCallback) {
  if (newValue.indexOf('\t') >= 0 && oldValue.indexOf('\t') === -1) {
    callback(oldValue)
    nextCallback()
  } else {
    callback(newValue)
  }
}

class LoginScene {
  focusNextField = (nextField) => {
    this.refs[nextField].focus()
  }

  focusOnPassword = () => {
    this.focusNextField('password')
  }

  handleUsernameChange = (newValue) => {
    const { username } = this.props            // or from wherever
    const { setUsername } = this.props.actions // or from wherever

    tabGuard(newValue, username, setUsername, this.focusOnPassword)
  }

  render () {
    const { username } = this.props

    return (
      <TextInput ref='username'
                 placeholder='Username'
                 autoCapitalize='none'
                 autoCorrect={false}
                 autoFocus
                 keyboardType='email-address'
                 onChangeText={handleUsernameChange}
                 blurOnSubmit={false}
                 onSubmitEditing={focusOnPassword}
                 value={username} />
    )
  }
}

@Bufke 2016-12-21 22:35:39

This didn't work for me using a physical keyboard. the onChangeText event doesn't fire on tab.

@Knotschi 2016-04-15 17:48:47

Here a reagent solution for a input component that has a :focus property.

The field will be focused as long as this prop is set to true and will not have focus as long as this is false.

Unfortunately this component needs to have a :ref defined, I could not find an other way to call .focus() on it. I am happy about suggestions.

(defn focusable-input [init-attrs]
  (r/create-class
    {:display-name "focusable-input"
     :component-will-receive-props
       (fn [this new-argv]
         (let [ref-c (aget this "refs" (:ref init-attrs))
               focus (:focus (ru/extract-props new-argv))
               is-focused (.isFocused ref-c)]
           (if focus
             (when-not is-focused (.focus ref-c))
             (when is-focused (.blur ref-c)))))
     :reagent-render
       (fn [attrs]
         (let [init-focus (:focus init-attrs)
               auto-focus (or (:auto-focus attrs) init-focus)
               attrs (assoc attrs :auto-focus auto-focus)]
           [input attrs]))}))

https://gist.github.com/Knotschi/6f97efe89681ac149113ddec4c396cc5

@Bap 2018-02-24 23:55:42

What in the world is this coded in!?

@Stedman Blake 2016-01-28 19:56:12

You can do this without using refs. This approach is preferred, since refs can lead to fragile code. The React docs advise finding other solutions where possible:

If you have not programmed several apps with React, your first inclination is usually going to be to try to use refs to "make things happen" in your app. If this is the case, take a moment and think more critically about where state should be owned in the component hierarchy. Often, it becomes clear that the proper place to "own" that state is at a higher level in the hierarchy. Placing the state there often eliminates any desire to use refs to "make things happen" – instead, the data flow will usually accomplish your goal.

Instead, we'll use a state variable to focus the second input field.

  1. Add a state variable that we'll pass as a prop to the DescriptionInput:

    initialState() {
      return {
        focusDescriptionInput: false,
      };
    }
    
  2. Define a handler method that will set this state variable to true:

    handleTitleInputSubmit() {
      this.setState(focusDescriptionInput: true);
    }
    
  3. Upon submitting / hitting enter / next on the TitleInput, we'll call handleTitleInputSubmit. This will set focusDescriptionInput to true.

    <TextInput 
       style = {styles.titleInput}
       returnKeyType = {"next"}
       autoFocus = {true}
       placeholder = "Title" 
       onSubmitEditing={this.handleTitleInputSubmit}
    />
    
  4. DescriptionInput's focus prop is set to our focusDescriptionInput state variable. So, when focusDescriptionInput changes (in step 3), DescriptionInput will re-render with focus={true}.

    <TextInput
       style = {styles.descriptionInput}          
       multiline = {true}
       maxLength = {200}
       placeholder = "Description" 
       focus={this.state.focusDescriptionInput}
    />
    

This is a nice way to avoid using refs, since refs can lead to more fragile code :)

EDIT: h/t to @LaneRettig for pointing out that you'll need to wrap the React Native TextInput with some added props & methods to get it to respond to focus:

    // Props:
    static propTypes = { 
        focus: PropTypes.bool,
    } 

    static defaultProps = { 
        focus: false,
    } 

    // Methods:
    focus() {
        this._component.focus(); 
    } 

    componentWillReceiveProps(nextProps) {
        const {focus} = nextProps; 

        focus && this.focus(); 
    }

@Lane Rettig 2016-02-22 20:07:29

I'm using RN 0.19 and this approach isn't working for me. Setting focus={} on a TextInput doesn't seem to have any effect when the prop's value changes.

@Stedman Blake 2016-02-23 20:42:11

@LaneRettig can you make sure that your component is re-rendering upon changes to this.state.focusDescriptionInput? You can just log it in the render() method (console.log(this.state.focusDescriptionInput);) and see if it prints out upon calling handleTitleInputSubmit(). Also, make sure that the value being set to either true or false.

@Lane Rettig 2016-02-27 21:21:04

I tried this again. Confirmed that the variables are being set properly, and that the view is being re-rendered. Setting focus={this.state.foo} on a TextInput does not work in the current version of RN, as far as I can tell!

@Stedman Blake 2016-02-28 23:19:24

@LaneRettig You're totally right -- thanks for pointing that out. We wrap RN TextInput with some added props and methods -- please see the bottom of the answer w/ those additions and let me know if you have any further issues!

@Lane Rettig 2016-02-28 23:33:05

Cool. You should submit this as a PR to RN. I'm surprised this isn't already supported out of the box.

@Piotr 2016-04-08 14:21:26

what if you click next on keyboard, and then click directly on first input? focus goes back to second which is bad experience with that solution

@chapinkapa 2016-05-15 02:16:41

This is a much messier solution than the first solution. The best solution would be a memo-bind type solution: github.com/airbnb/javascript/issues/659 and specifically github.com/supnate/memobind

@Stephen Horvath 2016-10-02 21:39:49

@chapinkapa Can you give an example of how this would work with the memobind solution?

@Petr Peller 2017-07-21 22:46:16

How is this._component initialized?

@Singh 2017-12-25 12:18:57

I couldn't get it to work. Could you please post the complete code?

@davidgoli 2018-03-20 21:30:08

I don't love this solution, in particular because it doesn't scale well for even slightly longer forms of 5-6 elements, where you'd need a focus boolean in state for each element & manage them all accordingly.

@Noah Allen 2018-06-19 03:33:17

Interestingly, the docs also state: "There are a few good use cases for refs: Managing focus, text selection, or media playback..." So in this case, using refs for focusing text input would be a valid use of the tool.

@Lane Rettig 2016-02-05 00:24:52

If you happen to be using tcomb-form-native as I am, you can do this, too. Here's the trick: instead of setting the props of the TextInput directly, you do it via options. You can refer to the fields of the form as:

this.refs.form.getComponent('password').refs.input.focus()

So the final product looks something like this:

var t = require('tcomb-form-native');
var Form = t.form.Form;

var MyForm = t.struct({
  field1:     t.String,
  field2:     t.String,
});

var MyComponent = React.createClass({

  _getFormOptions () {
    return {
      fields: {
        field1: {
          returnKeyType: 'next',
          onSubmitEditing: () => {this.refs.form.getComponent('field2').refs.input.focus()},
        },
      },
    };
  },

  render () {

    var formOptions = this._getFormOptions();

    return (
      <View style={styles.container}>
        <Form ref="form" type={MyForm} options={formOptions}/>
      </View>
    );
  },
});

(Credit to remcoanker for posting the idea here: https://github.com/gcanti/tcomb-form-native/issues/96)

@chetan 2017-12-14 11:22:38

how do I call function onSubmitEditing ? for ex: I want to call login() function when user press last textinput's returnkeytype 'done'.

@APAquino 2015-09-24 04:10:36

Try this solution on React Native's GitHub issues.

https://github.com/facebook/react-native/pull/2149#issuecomment-129262565

You need to use the ref prop for the TextInput component.
Then you need a create a function that gets called on onSubmitEditing prop that moves the focus on the second TextInput ref.

var InputScreen = React.createClass({
    _focusNextField(nextField) {
        this.refs[nextField].focus()
    },

    render: function() {
        return (
            <View style={styles.container}>
                <TextInput
                    ref='1'
                    style={styles.input}
                    placeholder='Normal'
                    returnKeyType='next'
                    blurOnSubmit={false}
                    onSubmitEditing={() => this._focusNextField('2')}
                />
                <TextInput
                    ref='2'
                    style={styles.input}
                    keyboardType='email-address'
                    placeholder='Email Address'
                    returnKeyType='next'
                    blurOnSubmit={false}
                    onSubmitEditing={() => this._focusNextField('3')}
                />
                <TextInput
                    ref='3'
                    style={styles.input}
                    keyboardType='url'
                    placeholder='URL'
                    returnKeyType='next'
                    blurOnSubmit={false}
                    onSubmitEditing={() => this._focusNextField('4')}
                />
                <TextInput
                    ref='4'
                    style={styles.input}
                    keyboardType='numeric'
                    placeholder='Numeric'
                    blurOnSubmit={false}
                    onSubmitEditing={() => this._focusNextField('5')}
                />
                <TextInput
                    ref='5'
                    style={styles.input}
                    keyboardType='numbers-and-punctuation'
                    placeholder='Numbers & Punctuation'
                    returnKeyType='done'
                />
            </View>
        );
    }
});

@Wes Foster 2015-09-24 04:27:56

Please include the relative information from the link in your answer.

@yura 2016-08-09 21:05:12

Keep in mind that string refs may become deprecated so this solution may not work in the future: "...Although string refs are not deprecated, they are considered legacy, and will likely be deprecated at some point in the future. Callback refs are preferred." -- facebook.github.io/react/docs/more-about-refs.html

@Mitch 2016-11-01 05:57:43

This doesn't work anymore, as of v0.36. There is no method "focus" on the component. How should we do this now? Can you update the answer?

@Eldelshell 2016-12-17 18:41:46

@Mitch not sure if this is back on 0.39.2 but this works fine now.

Related Questions

Sponsored Content

21 Answered Questions

[SOLVED] Hide keyboard in react-native

1 Answered Questions

1 Answered Questions

[SOLVED] React native IOS, when TextInput is focused, button press does not register

  • 2018-05-24 07:43:10
  • Adam Lagevik
  • 514 View
  • 4 Score
  • 1 Answer
  • Tags:   react-native

1 Answered Questions

1 Answered Questions

[SOLVED] react native modal issue when containing TextInput and Button

  • 2017-08-22 20:56:15
  • sushil bansal
  • 1157 View
  • 2 Score
  • 1 Answer
  • Tags:   react-native

1 Answered Questions

[SOLVED] How to create a floating button in react-native?

  • 2017-10-31 15:05:52
  • JMaylin
  • 876 View
  • 0 Score
  • 1 Answer
  • Tags:   react-native

3 Answered Questions

[SOLVED] React Native add text to TextInput on button click

1 Answered Questions

[SOLVED] clear TextInput value on button click - React Native

1 Answered Questions

2 Answered Questions

[SOLVED] How to auto focus a second text input after confirming the first in react native

  • 2015-07-06 12:47:22
  • Martin Mueller
  • 838 View
  • 0 Score
  • 2 Answer
  • Tags:   ios react-native

Sponsored Content