You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MacOS text input plugin should be properly incorporated into the view hierarchy and the responder chain #100590
Today the macOS text input plugin is a subclass of NSTextView which must be in the view hierarchy for it to properly interact with the OS input system.
Moreover the macOS text input plugin calls multiple API that are only supposed to be invoked by the system (-[NSTextInputContext active], -[NSTextInputContext deactive], -[NSResponder becomeFirstResponder], etc.). Setting up the view hierarchy could potentially remove these incorrect API usages.
This issue covers the long-term strategic fix for #100272, which was fixed by a short-term workaround.
changed the title [-]MacOS text input plugin should be properly incorporated into the view hierarchy and responder chain[/-][+]MacOS text input plugin should be properly incorporated into the view hierarchy and the responder chain[/+]on Mar 22, 2022
Maybe Android’s camera writes the image rotated with an EXIF orientation flag (e.g. “Rotate 90°”), rather than physically rotating pixels. as a result getResizedImagePath() method uses the raw image dimensions before rotation
Activity
[-]MacOS text input plugin should be properly incorporated into the view hierarchy and responder chain[/-][+]MacOS text input plugin should be properly incorporated into the view hierarchy and the responder chain[/+]raju-muliyashiya commentedon Nov 13, 2025
Maybe Android’s camera writes the image rotated with an EXIF orientation flag (e.g. “Rotate 90°”), rather than physically rotating pixels. as a result getResizedImagePath() method uses the raw image dimensions before rotation