[Qtwebengine] [Interest] Fixing up console.log() in QtWebEngine
Kai.Koehne at qt.io
Wed Mar 6 15:18:37 CET 2019
Alright, it's qtwebengine at qt-project.org ...
From: Interest <interest-bounces at qt-project.org> on behalf of Kai Köhne <Kai.Koehne at qt.io>
Sent: Wednesday, March 6, 2019 3:14 PM
To: Steve Atkins; Qt Project; webengine at qt-project.org
Subject: Re: [Interest] Fixing up console.log() in QtWebEngine
So it looks like fixing this would either above change to be merged, or finding other ways to get the same information ...
PS: webengine at qt-project.org is arguably the better mailing list for discussion implementation details like this, CC'ed
From: Interest <interest-bounces at qt-project.org> on behalf of Steve Atkins <steve at blighty.com>
Sent: Monday, March 4, 2019 2:42:12 PM
To: Qt Project
Subject: [Interest] Fixing up console.log() in QtWebEngine
In a normal web browser console.log() takes one or more values as parameters and renders them for the user in some appropriate way. If the first parameter is a string containing %s style escapes it'll do some printf style formatting of the remaining parameters. ( https://developers.google.com/web/tools/chrome-devtools/console/api#log ).
Console API Reference | Tools for Web Developers | Google Developers<https://developers.google.com/web/tools/chrome-devtools/console/api#log>
The first parameter of console.log() is converted to a string - e.g. "[Object object]" - and delivered as a QString. The remaining parameters are discarded.
Does anyone know where inside the Qt-Chromium interface I should start looking if I wanted to improve things?
Interest mailing list
Interest at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the QtWebEngine