Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-81783

event.key shows corrupt value for some key combinations

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P2: Important
    • 5.14.2, 5.15.0 Beta1
    • 5.12.6, 5.14.1, 5.15
    • WebEngine
    • None
    • Windows
    • db777c7bde2ad075f2a76cf6d5e9c20b04d62a2d (qt/qtwebengine/5.14)

    Description

      To reproduce, with the Nanobrowser example. Open a web page, then open the developer console and run:

      document.addEventListener("keydown", function(event) { console.log(event); })

      Then, try typing e.g. Ctrl + Z. The wrong key is shown (see attached).

      Note that whether a particular key combination works or does not seems to depend on the keyboard layout. For example, I see similar behavior when using a German keyboard layout alongside Ctrl + Shift prefixed key combinations.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-82912 QtWebEngine ctr+key returns string like u0005

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          resulted from

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-69442 Event 'key' attribute is incorrect when multiple modifier keys pressed

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          resulted in

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-83710 Unable to input some character in web view

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Activity

            People

              pvarga Peter Varga
              kevinushey Kevin Ushey
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: