Valentin Shergin 52648326e6 Generalization of `isInAParentText` context ... Summary: Currently `isInAParentText` context works as imaginary `isInAAncestorText` context (not like a real `isInAParentText`). Let's imagine we have hierarchy like: `View -> Text -> Text* -> View* -> Text* -> Text* -> View*` With current implementation all nodes marked with asterisk have `isInAParentText` context, which is incorrect (because some of them actually in View context). With the new implemetations it will work like this: `View -> Text -> Text* -> View* -> Text -> Text* -> View*` So, only nodes which have <Text> (or <TextInput>) as a parent will have `isInAParentText` context. This change allows to select proper `Text` vs. `VirtualText` component in cases where <Text> and <View> components can interleave each other. Reviewed By: sahrens Differential Revision: D6690495 fbshipit-source-id: f7c59b23d0eaf68a1d08036b858d99c9547f7878		2018-01-14 20:03:32 -08:00
..
TextInput.js	Generalization of `isInAParentText` context	2018-01-14 20:03:32 -08:00
TextInputState.js	Fixed an incorrect word in the blurTextInput() documentation.	2017-06-20 19:31:29 -07:00