📜 Description

Fixed a problem when input looses a focus, but FocusedInputObserver doesn't send noFocusedInputEvent to JS.

💡 Motivation and Context

The problem was introduced in this PR #760 before we were relying on keyboard evens, but in #760 I re-worked the approach and started to use blur/focus events. However I couldn't use only input events, because on iOS 15 keyboard event (keyboardWillShow) was arriving earlier than focus event, and for us it's crucial to know the layout of focused input inside onStart (i. e. before keyboard movement starts).

I decided to keep backward compatibility and keep keyboard events in place. However it comes with own set of challenges. For example:

This check works well for Paper, but doesn't work for Fabric. And for focus events we can keep two event sources, because logic for focus is simple -> "we got a focus -> save the state and push event to JS". For blur it's different:

• keyboard can be closed but focus still can be present;
• when we switch between inputs we also receive blur event but we should ignore it;
• we may have a random order of events including some missing events.

Initially I don't know how to fix it. But then I realized, that on Android we already have a similar situation. We can looses a focus and keyboard will be focus, we can have a focus and close a keyboard, so overall it's a very similar to what we can have on iOS right now. But why I don't experience any problems on Android? Because I just rely on "focus"/"blur" events there (and actually relying on keyboardWillShow on iOS is needed to have a stable order of events in JS). So at this point of time I thought "what if I remove keyboardWillHide handler?". Yes, it will not work as before (some events may be delayed), but for dismissing keyboard it's not so important at the moment (because on Android we can also have any order of those events).

So after thinking a lot I decided that it can be safe to remove that handler completely and reduce logic complexity presented in this class.

Closes #798

📢 Changelog

iOS

• rely on blur event only for sending noFocusedInputEvent (remove keyboardWillHide event);
• check in blur event UIResponder.current presence instead of self.currentResponder.

🤔 How Has This Been Tested?

Tested manually on iPhone 15 Pro iOS 17.5

📸 Screenshots (if appropriate):

📝 Checklist

• CI successfully passed
• I added new mocks and corresponding unit-tests if library API was changed