[Interest] Fixing up console.log() in QtWebEngine
steve at blighty.com
Wed Mar 6 18:58:29 CET 2019
> On Mar 6, 2019, at 2:14 PM, Kai Köhne <Kai.Koehne at qt.io> wrote:
> Hi Steve,
> So it looks like fixing this would either above change to be merged, or finding other ways to get the same information ...
Digging deeper it looks like several projects have flagged it as an issue and there's work in progress to support multiple parameters and % escapes (though not handling objects) going on fairly recently at https://chromium-review.googlesource.com/c/v8/v8/+/1374595
With luck we should have most of the nice-to-have features once that gets integrated and we move to a new enough version.
> 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 ).
> 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
More information about the Interest