Qt 5.7 Beta Is In Sight

[Awesomeness]

If there were any urgent security issues that would affect end-users of QtWebengine we would made an immediate release, so far it has not been the case.

“We”? So you are part of the team that for years failed to properly maintain QtWebKit and now promise immediate ports of Chromium fixes?
I honestly like Qt and mostly use KDE and Qt software but I have zero confidence in webview modules provided by the Qt project.
I have more confidence in the vague prospect of a CEF-based KDE web browser running Servo.

[carewolf]

The news story told nothing about backported security fixes and I have less boring things to do in my life than scrolling through commit histories.
I'm also not aware that Qt releases happen at the same time as Chrome releases. The time that passes from a Chrome release to a Qt bugfix release means that known security holes are open.

If there were any urgent security issues that would affect end-users of QtWebengine we would made an immediate release, so far it has not been the case.

The vast majority of security fixes in Chromium releases are fixes of bugs introduces in the same release (for instance the bug used in Pwn2Own was only introduced two weeks before), the rest these day mainly affects extension policies and Google's policing of those.

[Awesomeness]

What makes you think it is insecure? The security patches from Chromium 50 are even backported to Qt 5.6 based on Chromium 45.

The news story told nothing about backported security fixes and I have less boring things to do in my life than scrolling through commit histories.
I'm also not aware that Qt releases happen at the same time as Chrome releases. The time that passes from a Chrome release to a Qt bugfix release means that known security holes are open.

[carewolf]

After Chrome/Chromium 50 is out. That's why it's insecure.

What makes you think it is insecure? The security patches from Chromium 50 are even backported to Qt 5.6 based on Chromium 45.

[anda_skoa]

Why would Qt have a Wayland compositor?

Qt is very popular for embedded devices with touch screens.
Linux is very popular for embedded devices.
In a single window scenario the most common Qt backend is EGLFS, but if the situation needs multiple windows then you either need X11 or Wayland.
The Qt Wayland compositor makes it easy for the device creators to have their own, custom, window managment.

Cheers,
_

[nanonyme]

Why would Qt have a Wayland compositor?

[Emdek]

@DarkClous, QJSEngine from QtQml module is good enough replacement.
It was already gone with 5.6 BTW.

[DarkCloud]

The script module is depreciated, does that mean no longer available. Anybody know if there is a replacement for it. By the way, I recall there was a great deal of discussion a while back to reduce the memory consumption of QML. But nowhere do I see any bullet points mention this.

[Emdek]

Great news this is an important improvements towards an excellent qtwebengine browser.

Just in case, QtWebKit is not dead, it's currently being revived by third party developers, based on current WebKit plus some other goodies.
At lest there will be some competition. ;-)

[Azrael5]

Great news this is an important improvements towards an excellent qtwebengine browser.