-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[iOS] Not display InputAccessoryView closing the Software keyboard #22394
base: main
Are you sure you want to change the base?
Conversation
#if !MACCATALYST | ||
if(_keyboardObserverWillShow is not null) | ||
{ | ||
NSNotificationCenter.DefaultCenter.RemoveObserver(_keyboardObserverWillShow); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I recall that Manuel was saying things that NSNotificationCenter
is a bad API to use and creates leaks or something.
However, @tj-devel709 as our keyboard expert, is this the right place? Should we be putting things in some keyboard manager class or something that handles things? I know you have some special classes for keyboard things.
Description of Change
Not display InputAccessoryView closing the Software keyboard on the Editor control.
NOTE: The d character is captured from the physical keyboard, closing the virtual one.
Issues Fixed
Fixes #22286