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 }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
I think this was a known issue but I don't see any other bug tracking it. The problem is that 'smartautocomplete' only listens for key events, not text field change events in general.
We might be able to hack around it by catching oninput and forcing a fake onkeyup -- similar to what QuickNavigateDialog.setSearchFieldValue() does when setting the initial text value. But it would be tricky to do that without triggering double notifications for normal typing input.
Oh, I remember -- this used to work because the keyup from the Ctrl+V shortcut was still visible as a DOM event, and it would trigger smartautocomplete's keyup handler. But now with native menus, I think the shortcut is completely eaten at the native level and no DOM key event occurs.
Steps to reproduce:
Note that the Quick Find doesn't update the results. If you press some arrow keys or any other keydown event -- it will eventually fire.
What should happen:
The Quick Find input should detect a paste command and execute the search for that value.
The text was updated successfully, but these errors were encountered: