Commits (14)
-
Alexandru Croitor authored
When an asian IME is used to compose a new word, and a modifier key is pressed (shift, alt, etc), WebEngine would notify Chromium to cancel the composition, thus clearing the text. But the actual IME window would still be present, and if another "letter" key was pressed, the composition would continue with the previous pre-edit text, which leads to unusual text flickering. The previous behavior was introduced in 31efe25d to fix a Windows double character input bug. The current change makes sure to clear the IME composition only in case the last received QInputMethodEvent pre-edit and commit strings were empty, which is not the case when pressing a modifier key for instance. Change-Id: Ic968404c90e1e0eb703fe1c2849990467bedd5e1 Reviewed-by:
Allan Sandfeld Jensen <allan.jensen@qt.io>
e263573d -
Alexandru Croitor authored
Before this change, it was possible to select parts of the pre-edit text in an ongoing IME composition, by click-dragging with the mouse (which also looked wrong, because the styling of the text did not change to a selection box to signal selection). This is inconsistent with how Chrome does it, which commits the pre-edit string entered so far, when clicking anywhere in the content area or in the input. This change makes sure to commit the pre-edit string when a mouse click is done anywhere on the displayed web page. The behavior was present on Windows and Linux. Change-Id: I9cb148c591b5d09fb4dd477ae96c29ca32cc34de Reviewed-by:
Allan Sandfeld Jensen <allan.jensen@qt.io>
afc9e2d9 -
Alexandru Croitor authored
Currently when composing a word using an IME, and backspace is pressed to remove the last character present in the pre-edit string, instead of the character being removed, nothing happens. In reality the character is removed, but Chromium isn't notified of it, and the change will be seen only after another key is pressed. Fix consists in notifying Chromium to cancel the IME composition when both the pre-edit string and the commit string are empty. There is still an issue with japanese, when trying to input "aaa", press space, then "b" and you don't see the "b" until you press one more key. Change-Id: Idf2ef4888caead26d19eabbbdf4f98fbee601049 Reviewed-by:
Allan Sandfeld Jensen <allan.jensen@qt.io>
ad568f11 -
Alexandru Croitor authored
Currently if a QInputMethodEvent is received, which contains text in both the pre-edit and commit strings, Chromium would only show the commit string in the text input (or other html element). The IME though still knows about the non-empty pre-edit string, which means that if another key is pressed, Chromium will suddenly show the content of the previous pre-edit string AND the result of the new key press. To fix this, WebEngine will now properly set the pre-edit string as the new composition, after confirming the previous commit string. Change-Id: If22dd2038aca35a6fe6bb58a521f0a7124c7d468 Reviewed-by:
Allan Sandfeld Jensen <allan.jensen@qt.io>
089f7968 -
Alexandru Croitor authored
Previously while entering a Japanese succession of characters, followed by transforming a substring into a word suggestion, the caret would disappear, and pressing the arrow keys would not indicate which part of the pre-edit string will be transformed next. This change makes sure the caret is always present, to indicate which part of the pre-edit string will be replaced by a possible IME suggestion. Change-Id: I350310c198bcacf0bcb48217f84b08e95ab8e8ef Reviewed-by:
Allan Sandfeld Jensen <allan.jensen@qt.io>
323f300f -
Kai Koehne authored
Setting the Qt::AA_EnableHighDpiScaling attribute makes sure that the scrollbars are scaled, and that the default zoom level is sensible. Task-number: QTBUG-54113 Change-Id: I0ae7eb97cb9e2824e7f9b92d77cf2986cac66685 Reviewed-by:
Allan Sandfeld Jensen <allan.jensen@qt.io>
aceda160 -
Michael Bruning authored
Add a flag to let checkForExpired remove the entries directly. Task-number: QTBUG-54222 Change-Id: Iddac9e50f645d74b95d0ea13ed76d7f858ddd137 Reviewed-by:
Allan Sandfeld Jensen <allan.jensen@qt.io>
7494836e -
Allan Sandfeld Jensen authored
To ensure Chromium is given a chance to handle editor commands, we must override these short-cuts. On OS X we must also perform the action afterwards as these are not handled internally by the Blink Editor. The patch solves copy/paste in flash plugins and copy/paste on OS X when no application short-cuts have been defined. The handling of short-cut override events is based on how it was handled in Qt WebKit Task-number: QTBUG-54221 Change-Id: I748671c7bfa5662aae16c6a4b9bbe5e2bce1b907 Reviewed-by:
Alexandru Croitor <alexandru.croitor@theqtcompany.com>
e0bd650c -
Kai Koehne authored
This is somewhat artificial, since the QtWebEngine module now also has public C++ API. Change-Id: I2067a3eb4e84cfac2b3e6766b272445b9bd31ae7 Reviewed-by:
Leena Miettinen <riitta-leena.miettinen@qt.io>
f77a9e1b -
Allan Sandfeld Jensen authored
Switch to using the Qt5 angleDelta instead of the Qt4 style delta that can only handle single orientation wheel events. Change-Id: I181dda03c7fc9c676100cb31ab7717f9641b625e Reviewed-by:
Joerg Bornemann <joerg.bornemann@qt.io>
99d3c341 -
Michal Klocek authored
If a user does not handle onCertificateError the instance of QQuickWebEngineCertificateError never gets to JavaScript land and never gets deleted. Create a strong reference before emitting the onCertificateError to guard against the memory leak. Change-Id: I49dbf89445d32291e2f52976f0f5e9deda201fcb Reviewed-by:
Simon Hausmann <simon.hausmann@qt.io> Reviewed-by:
Allan Sandfeld Jensen <allan.jensen@qt.io>
964963f7 -
Alexandru Croitor authored
Test was flaky due to a couple of reasons, mainly: 1) Size of event recording widget did not match web view size, which led to some events not being caught. 2) There were some bogus QHoverEvents being sent by QQuickWindow whenever a QQuickItem is repositioned (can happen when using a tiling window manager on a Linux machine). 3) Usual timing issues. Change-Id: Idd9d4fa6bd65095f98125196025e0ad560025348 Reviewed-by:
Allan Sandfeld Jensen <allan.jensen@qt.io>
cc8fc6ca -
Allan Sandfeld Jensen authored
We were not handling -march= arguments and we were not setting the result in GYP_CONFIG. Task-number: QTBUG-54336 Change-Id: I63e45f153aa46d5879aa968aa6c3d898ef58855e Reviewed-by:
Michael Brüning <michael.bruning@qt.io>
722732d1 -
Allan Sandfeld Jensen authored
Change-Id: Ic6686df8f82f710a3441501b7eeaffe69fbcbdf7
ec5a99b0
Showing