[Qtwebengine] Dev tools and request signals

Jarred Nicholls jarred at webkit.org
Mon Dec 22 04:56:08 CET 2014

On Sat, Dec 13, 2014 at 6:24 PM, Philipp A. <flying-sheep at web.de> wrote:

> Sorry, i didn’t quite phrase that well:
> The decision not to sync Qt Webkit

It's not just as easy as a "sync."  It doesn't work like that.  In the
world of WebKit/2, keeping a port up-to-date with the latest functionality
offered by the WebKit engine usually requires some port-specific
implementation.  That means development time and resources.  And the more
development time and resources spent on QtWebKit is less time and resources
spent on QtWebEngine.  Rather than making the trip to QtWebEngine even
longer and more painful of a transition, I believe they are doing the
correct thing and focusing completely on getting the future engine up to
par as quickly as possible.  Unlike Apple and Google, the Digia team does
not have 500 engineers working on their browser.

With that said, I'm not the right person to comment on this decision
because as a Chromium developer, any deficiencies that are currently in
QtWebEngine I've been able to work around in my own fork of it.  I realize
that not everyone has the expertise to do so.  But if I were them, choosing
to spend cycles on the WebKit port would be like eating a bucket of nails
because it is very counter productive to getting QtWebEngine up to feature
parity as quickly as possible.

> while Qt WebEngine isn’t ready to replace it yet was a bad decision.
> browsers based on Qt now have a lean period during which they can’t ship
> proper functionality (newest HTML5 features, as well as cookie, request &
> proxy management, dev tools)
> 2014-12-13 16:30 GMT+01:00 Florian Bruhin <me at the-compiler.org>:
>> Hey Philip,
>> * Philipp A. <flying-sheep at web.de> [2014-12-13 14:06:30 +0100]:
>> > I impatiently awaited the new Qt WebEngine, because it has a non-ancient
>> > webkit/blink version and promised to supersede the old Qt Webkit module.
>> >
>> > Now how do i enable/trigger the blink dev tools?
>> >
>> > And how do i hook into requests the page wants to make without
>> > QNetworkAccessManager interop (in order to find out why the hell that
>> > request was denied even with LocalContentCanAccessRemoteUrls and
>> > LocalContentCanAccessFileUrls)?
>> >
>> > if any of the answers are “you don’t”, Qt WebEngine was a bad decision.
>> i
>> > want one thing that is up-to-date and powerful, not thing A that is
>> > deprecated and powerful together with thing B that is up-to-date and
>> inept.
>> I'm not a QtWebEngine developer, just someone writing a browser using
>> QtWebKit and also looking forward to QtWebEngine. But let me share my
>> thoughts about this.
>> The answer to all of this is probably "not yet". This means you can
>> either patiently wait (what I'm doing), start to contribute, or pay
>> other people to allow them to work on it more.
>> That doesn't make QtWebEngine "a bad decision". It's just not there
>> yet. 5.4 is the first Qt release to include QtWebEngine, you shouldn't
>> expect to be able to use it for too sophisticated stuff already ;)
>> That being said, QtWebKit is still being maintained (in terms of
>> bugfixes) and works just fine for me and a lot of other Qt based
>> browsers. Nobody said it's deprecated, and I don't expect it to be
>> deprecated until QtWebEngine is more advanced.
>> Florian
>> --
>> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>>              GPG 0xFD55A072 | http://the-compiler.org/pubkey.asc
>>          I love long mails! | http://email.is-not-s.ms/
>> _______________________________________________
>> QtWebEngine mailing list
>> QtWebEngine at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/qtwebengine
> _______________________________________________
> QtWebEngine mailing list
> QtWebEngine at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qtwebengine
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20141221/9a2825af/attachment.html>

More information about the QtWebEngine mailing list