From greg.hellings at gmail.com Fri Mar 10 06:31:47 2017 From: greg.hellings at gmail.com (Greg Hellings) Date: Thu, 9 Mar 2017 23:31:47 -0600 Subject: [Qtwebengine] QWebChannel question Message-ID: I'm working with an embedded QWebEngineView widget through which I'm connecting by means of QWebChannel. The documentation for QWebChannel::registerObject includes the following text "*Note: *A current limitation is that objects must be registered before any client is initialized.". Does anyone happen to know if there are efforts to remove that limitation? Is there significant difficulty in removing that limitation, or has there simply been no demand for it, so no effort has been put into removing it? Is it something that would be open and accessible to a newcomer to contribute if there is a market for it? --Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From milian.wolff at kdab.com Sun Mar 12 14:28:14 2017 From: milian.wolff at kdab.com (Milian Wolff) Date: Sun, 12 Mar 2017 14:28:14 +0100 Subject: [Qtwebengine] QWebChannel question In-Reply-To: References: Message-ID: <2035841.ZT0lPijYPn@agathebauer> On Freitag, 10. März 2017 06:31:47 CET Greg Hellings wrote: > I'm working with an embedded QWebEngineView widget through which I'm > connecting by means of QWebChannel. The documentation for > QWebChannel::registerObject includes the following text "*Note: *A current > limitation is that objects must be registered before any client is > initialized.". > > Does anyone happen to know if there are efforts to remove that limitation? As the QWebChannel maintainer, I'm not aware of any effort to remove this limitation. > Is there significant difficulty in removing that limitation, or has there > simply been no demand for it, so no effort has been put into removing it? Exactly this, no demand and it simplified things. But note that the webchannel nowadays can cope with dynamic registration to some degree internally already - namely when it encounters a new QObject as a return value, or signal argument, or property value. > Is it something that would be open and accessible to a newcomer to > contribute if there is a market for it? See above: The basis should be there already, patches welcome to use that for supporting registration of new clients later on. Note that you'll also have to deal with deregistration, which you can probably handle like a "destroyed" event on the JavaScript side. Cheers -- Milian Wolff | milian.wolff at kdab.com | Software Engineer KDAB (Deutschland) GmbH&Co KG, a KDAB Group company Tel: +49-30-521325470 KDAB - The Qt Experts -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5903 bytes Desc: not available URL: From e-ruei1 at ti.com Wed Mar 22 19:42:41 2017 From: e-ruei1 at ti.com (Ruei, Eric) Date: Wed, 22 Mar 2017 18:42:41 +0000 Subject: [Qtwebengine] QT5.6.2 to 5.7.1 default behavior changes and qtWebengine ozone bridge Message-ID: <009C030982313E4589C6BC55FBF1E82A25358F91@DFLE09.ent.ti.com> Hi, All: I have a few questions and some interesting observations regarding qtwebengine 5.6.2 and 5.7.1. Your kind assistance will be highly appreciated. 1. For qtwebengine 5.6.2, the SUID sandbox is not supported and disabled with chromium command-line option -no-sandbox within the webengine context code or by build options. Do you know where this option is added? 2. For qtwebengine 5.7.1, the Chromium LOG(ERROR, FATAL) is enabled by default. Do you know how the logging is enabled? 3. For qtwebengine 5.7.1, it looks like that the SUID sandbox is enabled by default. For embedded linux, where does the sandbox binary reside? Do we need kernel support to use SUID sandbox? 4. The QtWebengine contains some platform related code under src/core, which seems to either implement the chromium ozone layer or provide a bridge between Chromium and the QT platform code. In the function SurfaceFactoryQt::LoadEGLGLES2Bindings() @ surface_factory_qt.cpp, the hard-coded library libGLESv2.so.2 is loaded and if the library does not exist, this function will fail and return false and the function GLSurface::CreateOffscreenGLSurface() @ gl_surface_qt.cpp will also fail and return NULL subsequently. The interesting observation is that the qtwebengine demo browser will still work with GPU rendering whether or not the above failure occurs. Therefore, the EGLGLES2 related initialization does not seem to have any effect on the qtwebengine operation and the corresponding errors may be ignored. If it is true, should we update the latest GLSurface::CreateOffscreenGLSurface() implementation at QT 5.7.1 to avoid potential system crash due to Q_UNREACHABLE() macro()?. scoped_refptr GLSurface::CreateOffscreenGLSurface(const gfx::Size& size) { scoped_refptr surface; switch (GetGLImplementation()) { case kGLImplementationDesktopGL: { surface = new GLSurfaceQtWGL(size); if (surface->Initialize()) return surface; break; #elif defined(USE_X11) if (!g_initializedEGL) { surface = new GLSurfaceQtGLX(size); if (surface->Initialize()) return surface; } // no break #endif } case kGLImplementationEGLGLES2: { if (g_egl_surfaceless_context_supported) surface = new GLSurfacelessQtEGL(size); else surface = new GLSurfaceQtEGL(size); if (surface->Initialize()) return surface; break; } default: printf("GLSurface::CreateOffscreenGLSurface: %d!\n", GetGLImplementation()); break; } LOG(ERROR) << "Requested OpenGL platform is not supported."; //Q_UNREACHABLE(); return NULL; } Best regards, Eric Ruei -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.croitor at qt.io Thu Mar 23 16:34:58 2017 From: alexandru.croitor at qt.io (Alexandru Croitor) Date: Thu, 23 Mar 2017 15:34:58 +0000 Subject: [Qtwebengine] QT5.6.2 to 5.7.1 default behavior changes and qtWebengine ozone bridge In-Reply-To: <009C030982313E4589C6BC55FBF1E82A253592C1@DFLE09.ent.ti.com> References: <009C030982313E4589C6BC55FBF1E82A25358F91@DFLE09.ent.ti.com> <76CCF44C-8D37-4AC0-B921-C34A5779CE39@qt.io> <009C030982313E4589C6BC55FBF1E82A253592C1@DFLE09.ent.ti.com> Message-ID: <1A26B0C1-A936-4E25-BF0E-9EBFF5B46268@qt.io> Hi, I am not aware of the reason for the seccomp crash, but you can find some similar reports with some info at https://bugreports.qt.io/browse/QTBUG-57709 maybe that helps you investigate the issue further. Regarding GLES, I am not very familiar with that code, but it is plausible it is incomplete. You could check if there are any code changes in Qt 5.8.x and in unreleased Qt 5.9.0. Rergards, Alex. On 23 Mar 2017, at 16:14, Ruei, Eric > wrote: Hi, Alexandru: Thank you so much! The information that you provided is extremely helpful and it may take me forever to get without your help! For question #3, we are using Linux kernel 4.9.13 and seccomp-bpf is enabled. With the default setting, the following error occurs continuously and the Seccomp is set to 0 at /proc//status. Render process exited with code 256 (abnormal exit) /home/a0850410/yocto_builds/LTS2017_0/oe-layersetup/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0/git/src/3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:futex() failure Received signal 11 SEGV_MAPERR 000000000007 [end of stack trace] … The qtwebengine demo browser works if seccomp-bpf sandbox is disabled by --disable-seccomp-filter-sandbox. Do you have any idea for question #4? Best regards, Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From bryan.chan at pacbell.net Fri Mar 24 19:10:39 2017 From: bryan.chan at pacbell.net (Bryan Chan) Date: Fri, 24 Mar 2017 18:10:39 +0000 (UTC) Subject: [Qtwebengine] Http2 with qt 5.8 References: <1432671304.3129436.1490379039161.ref@mail.yahoo.com> Message-ID: <1432671304.3129436.1490379039161@mail.yahoo.com> Hello, Is http2 available with webengine on qt 5.8? It still seems to use http 1.1? ThanksBryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Sat Mar 25 11:32:16 2017 From: me at the-compiler.org (Florian Bruhin) Date: Sat, 25 Mar 2017 11:32:16 +0100 Subject: [Qtwebengine] Http2 with qt 5.8 In-Reply-To: <1432671304.3129436.1490379039161@mail.yahoo.com> References: <1432671304.3129436.1490379039161.ref@mail.yahoo.com> <1432671304.3129436.1490379039161@mail.yahoo.com> Message-ID: <20170325103216.tjsqjocbo44qnstz@hooch> On Fri, Mar 24, 2017 at 06:10:39PM +0000, Bryan Chan wrote: > Hello, > Is http2 available with webengine on qt 5.8? It still seems to use http 1.1? https://http2.akamai.com/demo seems to work fine here with Qt 5.8. Florian -- http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/