Opened 16 months ago

Closed 16 months ago

Last modified 14 months ago

#13575 closed enhancement (fixed)

qt-everywhere-src-5.15.0 and qtwebengine

Reported by: Bruce Dubbs Owned by: Douglas R. Reno
Priority: high Milestone: 10.0
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

New point version.

Change History (7)

comment:1 by Douglas R. Reno, 16 months ago

Owner: changed from blfs-book to Douglas R. Reno
Status: newassigned

comment:2 by Douglas R. Reno, 16 months ago

Priority: normalhigh
Summary: qt-everywhere-src-5.15.0qt-everywhere-src-5.15.0 and qtwebengine

A link to all of the changelogs can be found here: https://wiki.qt.io/Qt_5.15.0_Change_Files

Some things that stand out with regards to deprecations and behavior changes:

QtBase (https://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.15.0/?h=v5.15.0) Contains binary incompatible changes and many deprecations.

QtDeclarative (which handles QML) https://code.qt.io/cgit/qt/qtdeclarative.git/tree/dist/changes-5.15.0/?h=v5.15.0 has several deprecations and may cause problems.

QtMultimedia (https://code.qt.io/cgit/qt/qtmultimedia.git/tree/dist/changes-5.15.0/?h=v5.15.0) has some deprecations as well.

In QtQuickControls2 (https://code.qt.io/cgit/qt/qtquickcontrols2.git/tree/dist/changes-5.15.0/?h=v5.15.0):

****************************************************************************
*                        Important Behavior Changes                        *
****************************************************************************

 - [QTBUG-72085] Old delegate items (background, contentItem, etc.) are no
   longer destroyed, as they are technically owned by user code. Instead,
   they are hidden, unparented from the control (QQuickItem parent, not
   QObject), and Accessible.ignored is set to true. This prevents them from
   being unintentionally visible and interfering with the accessibility
   tree when a new delegate item is set.

   See the following page for more information:

   https://doc.qt.io/qt-5/qtquickcontrols2-customize.html#considerations-for-custom-styles

QtWebEngine has the normal host of security fixes (https://code.qt.io/cgit/qt/qtwebengine.git/tree/dist/changes-5.15.0/?h=v5.15.0):

Chromium Snapshot
-----------------

 - Updated the Chromium version to 80.0.3987.163
 - Applied security fixes from Chrome up to version 81.0.4044.138

We'll need to test to see whether the GCC-10 patch is needed there or not (same with Qt itself).

comment:3 by Douglas R. Reno, 16 months ago

The GCC patch isn't needed for Qt5.

On the other hand, qtwebengine needs the ICU patch (as Thomas mentioned in IRC). All but one of the GCC-10 fixes were implemented into the chromium build shipped with QtWebEngine-5.15.0. I've implented that one, the ICU fix, and another gcc-10 fix needed in "src/3rdparty/chromium/base/trace_event/trace_event_memory_overhead.h" (#include <string> *below* #include <unordered_map>). These will all be present in a new consolidated_fixes patch that I'll submit with the update

comment:4 by Douglas R. Reno, 16 months ago

The patch for qtwebengine has been added to the patches repo at r4131.

The Qt developers have decided to develop their own PDF Reader implementation for Falkon, which is called QtPdf. It's built with QtWebEngine

comment:5 by Douglas R. Reno, 16 months ago

Resolution: fixed
Status: assignedclosed

Fixed at r23206

comment:6 by Bruce Dubbs, 14 months ago

Milestone: 9.210,0

Milestone renamed

comment:7 by Bruce Dubbs, 14 months ago

Milestone: 10,010.0

Milestone renamed

Note: See TracTickets for help on using tickets.