diff options
author | Tor Arne Vestbø <tor.arne.vestbo@qt.io> | 2021-09-21 17:05:26 +0200 |
---|---|---|
committer | Tor Arne Vestbø <tor.arne.vestbo@qt.io> | 2021-09-21 20:49:00 +0200 |
commit | ab4fb3ffd40c0bf694161d955d4a58602b9f1a4c (patch) | |
tree | 16056b593d84881fcb7cdcd61a4bba31d535ae55 /mkspecs/features | |
parent | 388e7504be285151dc10a79662eecdbecf1cd1bc (diff) |
macOS: Don't re-send key event through input method on focus object change
In 0c2ca26cd9583092f3ade7b18bc2423336a6202b we started re-sending the
key event through the input method when we detected a focus object change,
to support the use-case of QAbstractItemView opening an editor and changing
focus in response to the first QEvent::InputMethod event.
Unfortunately this doesn't work as a general approach, because we don't
know what the reason was for the change in focus object. For example,
a client might respond to a Qt::Key_Return press by changing the focus
to the next input element, and re-sending the key event would in that
case insert a new-line in the new focus object -- counter to the
expectations of the client.
Since we can't know the reason for the changed focus object we can't
assume re-sending the key event is safe.
Task-number: QTBUG-54848
Fixes: QTBUG-96726
Pick-to: 6.2 6.2.0
Change-Id: Iea8b166385925cd1a05ef62d5cf763638d9f8a67
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
Diffstat (limited to 'mkspecs/features')
0 files changed, 0 insertions, 0 deletions