![]() * Something asks for a NativeModule instance - ideally it should just get nil at this point * The bridge gets invalidated, and native modules are cleaning up themselves (but not done yet) * iOS: when the bridge has been invalidated, NativeModule lookup should just return nil I removed 1 MiB from `jscodeshift` as it was shipping with docs: įbshipit-source-id: 452fd4cedcc749d972adbb69df5c95117dd55b15 You'd use this just like you would in the Android implementation:įbshipit-source-id: 561e72fc2cf16b30446132f6b96b8aa2b4a92daf So perhaps the Android implementation needs to be looked at as well (I myself have not gotten around to confirming whether it works or not) On a related note, when searching this repo's issues for `showSoftInputOnFocus`, it appears that there are several closed issues that claim that the Android implementation doesn't work ( #25685, #25687, #26643). The issue with iOS was brought up again on #27243. There was a lot of discussion on the original issue being addressed ( #14045), that there is a need for this on iOS as well. `showSoftInputOnFocus` was added in #25028, but it was only added for Android. ![]() There should be some way we can make iOS and Android behave the same for this. Try to hide the keyboard from showing while still maintaining the ability to paste into it.System Images: android-28 | Google APIs Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom_64 How can we make this work sufficiently for both iOS and Android? (Side note: it seems this prop isn't included in the latest typings in 0.61.4, so there is a typescript error even though the prop works) Using the new prop showSoftInputOnFocus does exactly what is wanted but it only works for Android.If you set editable= is not acceptable because the keyboard pops up for a second (both iOS and Android) so this can't be used.The issue here is that there is no way to disable the keyboard from popping up on a text input field while still allowing the user to paste into the field, which works for both iOS and Android. It would be great if we could have sufficient resolution of this issue without it being prematurely closed. I read the full discussion in #14045 and it seems to have been auto-closed without sufficient resolution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |