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

Qt6 won't render into cutout area (regression)

    XMLWordPrintable

Details

    • Android
    • 792a5b15c (dev), 57e3030f9 (6.5), fb2d2fa02 (tqtc/lts-6.2), df8e1cc73 (dev), b87c8a325 (6.6), adb7e2525 (dev), 07839c11f (6.5), 061a057d5 (6.6), 0e4110aa6 (tqtc/lts-6.2), 154771b42 (6.5), 30990b0dc (tqtc/lts-6.2)
    • 2023wk02FOQtforAndroid, 2022wk44FOQtforAndroid, 2022wk46FOQtforAndroid, 2022wk48FOQtforAndroid, 2022wk50FOQtforAndroid, 2022wk52FOQtforAndroid, 2023wk04FOQtforAndroid, 2023wk08FOQtforAndroid, 2023wk10FOQtforAndroid, 2023wk12FOQtforAndroid, 2023wk14FOQtforAndroid

    Description

      Consider a QQuickWindow in a fullscreen mode:

      window()->setVisibility(QWindow::FullScreen);

      and allow the window to extend into the DisplayCutout areas:

      WindowManager.LayoutParams attr = getWindow().getAttributes();
attr.layoutInDisplayCutoutMode = WindowManager.LayoutParams.LAYOUT_IN_DISPLAY_CUTOUT_MODE_SHORT_EDGES;
getWindow().setAttributes(attr);

      Expected behavior (like in Qt 5.15): Quick item occupies full screen.
      Actual behavior in Qt 6.x: the item is not rendered into cutout areas, they are left filled with white color.

      Attachments

        1. 1p7tandr11_dev+patch10.mp4
          1.15 MB
        2. 1p7tandr11_dev+patch13.mp4
          3.00 MB
        3. fullscreen.jpg
          fullscreen.jpg
          43 kB
        4. image-2021-11-16-15-51-41-773.png
          image-2021-11-16-15-51-41-773.png
          322 kB
        5. QTBUG-96877-1+7tAndroid11patch1.mp4
          808 kB
        6. qtdev+hup30proandr10+patch6.png
          qtdev+hup30proandr10+patch6.png
          17 kB
        7. Screenshot_20210927-115115[2].jpg
          Screenshot_20210927-115115[2].jpg
          183 kB
        8. Screenshot_20210927-115507.jpg
          Screenshot_20210927-115507.jpg
          176 kB
        9. Screenshot_20210927-115824.jpg
          Screenshot_20210927-115824.jpg
          180 kB
        10. Screenshot_20210927-120230.jpg
          Screenshot_20210927-120230.jpg
          189 kB
        11. Screenshot_20210927-120352.jpg
          Screenshot_20210927-120352.jpg
          186 kB
        12. Screenshot_20210927-120517.jpg
          Screenshot_20210927-120517.jpg
          184 kB
        13. screenshot-1.png
          screenshot-1.png
          26 kB

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-110004 Android applications in FullScreen extend past screen

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

          User Story - Created by Jira Software - do not edit or delete. Issue type for a user story. QTBUG-98989 Android 11 - Display Cutout (Waterfall insets)

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

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-96105 When a window is switched to be FullScreen then it will end up keeping a bar at the bottom of the window which should not be visible

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

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-107923 Wrong height of the window on Android

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          resulted in

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-114437 REG: Android: Layout in display cut mode being overridden to short edges always

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              rampe Rami Potinkara
              chainik Konstantin Dondoshanskiy
              Votes:
              6 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: