ffe6c110f7
Summary: When `keyboardShouldPersistTaps` is `"never"` it would break when doing the following steps: - Tap input 1, keyboard goes up - Tap input 2, keyboard stays down (The bug I expected without the isTextInput check was that it would dismiss instead :o ) - Tap outside, keyboard stays down. It should dismiss here since it should never persist taps (unless tapping another input) What seems to happen is that RN `currentlyFocusedTextInput` goes out of sync with the focused text input and is null even if there is still a text input focused. I haven't had time to investigate the cause of that (probably some race condition because of trying to focus and blur at the same time) but we should not try to dismiss the keyboard when tapping another TextInput in the first place. I reproduced the bug mentioned by setting `keyboardShouldPersistTaps` to `"never"` in RNTesterPage.js and then using the steps described above. I made sure that the bug did not happen after this change. [GENERAL][BUGFIX][ScrollResponder] - Fix keyboard handling with keyboardShouldPersistTaps: never Closes https://github.com/facebook/react-native/pull/19255 Differential Revision: D8002818 Pulled By: mdvacca fbshipit-source-id: 6ecb8d2c30eb9338529471a958b5dc04037c7ec6 |
||
---|---|---|
.circleci | ||
.github | ||
ContainerShip | ||
IntegrationTests | ||
Libraries | ||
RNTester | ||
React | ||
ReactAndroid | ||
ReactCommon | ||
ReactNative | ||
babel-preset | ||
bots | ||
flow | ||
flow-github | ||
gradle/wrapper | ||
jest | ||
keystores | ||
lib | ||
local-cli | ||
react-native-cli | ||
react-native-git-upgrade | ||
scripts | ||
third-party-podspecs | ||
.buckconfig | ||
.buckjavaargs | ||
.editorconfig | ||
.eslintignore | ||
.eslintrc | ||
.flowconfig | ||
.gitattributes | ||
.gitignore | ||
.npmignore | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
DockerTests.md | ||
Jenkinsfile | ||
LICENSE | ||
LICENSE-docs | ||
README.md | ||
React.podspec | ||
Releases.md | ||
build.gradle | ||
cli.js | ||
gradlew | ||
gradlew.bat | ||
jest-preset.json | ||
package.json | ||
react.gradle | ||
rn-cli.config.js | ||
rn-get-polyfills.js | ||
runXcodeTests.sh | ||
settings.gradle | ||
setupBabel.js |
README.md
React Native ·
Learn once, write anywhere: Build mobile apps with React.
- Build native mobile apps using JavaScript and React: React Native lets you build mobile apps using only JavaScript. It uses the same design as React, letting you compose a rich mobile UI from declarative components.
- A React Native app is a real mobile app: With React Native, you don't build a "mobile web app", an "HTML5 app", or a "hybrid app". You build a real mobile app that's indistinguishable from an app built using Objective-C, Java, or Swift. React Native uses the same fundamental UI building blocks as regular iOS and Android apps. You just put those building blocks together using JavaScript and React.
- Don't waste time recompiling: React Native lets you build your app faster. Instead of recompiling, you can reload your app instantly. With hot reloading, you can even run new code while retaining your application state. Give it a try - it's a magical experience.
- Use native code when you need to: React Native combines smoothly with components written in Objective-C, Java, or Swift. It's simple to drop down to native code if you need to optimize a few aspects of your application. It's also easy to build part of your app in React Native, and part of your app using native code directly - that's how the Facebook app works.
The focus of React Native is on developer efficiency across all the platforms you care about - learn once, write anywhere. Facebook uses React Native in multiple production apps and will continue investing in React Native.
See the official React Native website for an introduction to React Native.
Supported operating systems are >= Android 4.1 (API 16) and >= iOS 8.0.
Getting Started
Follow the Getting Started guide. The recommended way to install React Native depends on your project. Here you can find short guides for the most common scenarios:
Documentation
The website’s documentation is divided into multiple sections.
- There are Guides that discuss topics like debugging, integrating with existing apps, and the gesture responder system.
- The Components section covers React components such as
View
andButton
. - The APIs section covers other libraries like Animated and StyleSheet that aren’t React components themselves.
- Finally, React Native provides a small number of Polyfills that offer web-like APIs.
Another great way to learn more about the components and APIs included with React Native is to read their source. Look under the Libraries/Components
directory for components like ScrollView
and TextInput
, for example. The RNTester example is also here to demonstrate some of the ways to use these components. From the source you can get an accurate understanding of each component’s behavior and API.
The React Native documentation only discusses the components, APIs and topics specific to React Native (React on iOS and Android). For further documentation on the React API that is shared between React Native and React DOM, refer to the React documentation.
Upgrading
React Native is under active development. See the guide on upgrading React Native to keep your project up-to-date.
Contributing
Read below to learn how you can take part in improving React Native.
Code of Conduct
Facebook has adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.
Contributing Guide
Read our contributing guide to learn about our development process, how to propose bug fixes and improvements, and how to build and test your changes to React Native.
Beginner Friendly Bugs
We have a list of beginner friendly issues to help you get your feet wet in the React Native codebase and familiar with our contribution process. This is a great place to get started.
License
React Native is MIT licensed.
React Native documentation is Creative Commons licensed.