From g4jc at openmailbox.org Tue Jan 24 00:45:41 2017 From: g4jc at openmailbox.org (Luke) Date: Mon, 23 Jan 2017 23:45:41 +0000 Subject: [Qtwebengine] QTWebengine compliance with FSDG Message-ID: Hello, I am currently a packager for Parabola GNU/Linux-libre. While investigating the change from Webkit to Webengine, I discovered several concerning issues that affect our compliance with the Free Software Foundation's Free System Distribution Guidelines (FSDG).[1] I am hopeful that some developers will be able to clarify these issues for us as it affects hundreds of projects downstream including nearly all of KDE, as well as many QT programs. In particular, your website claims it is not just a rendering engine, "it is the entire Chromium platform."[2] If this is true, there are many outstanding issues with Chromium which we would need to be addressed. 1) Was any attempt made to remove Google specific code from Chromium prior to preparing QTWebengine? - If not, could ungoogled-chromium patches be applied to your code?[3] By default, Chromium has many lines of code that make internet queries to Google. Building it using the default settings essentially puts your browser into the cloud. As mentioned in the GNU.org article "Who does that server really serve?"[4], free software is only free when you are in control. Any use of Google API, Google Sync, Google Hangouts, and Google OK, does not classify as free software. 2) Is any form of proprietary code such as Adobe pepperflash, webvine DRM[5], or proprietary codecs included? If so, can they be removed or disabled with a compile time option? 3) Is it possible to compile QTWebengine with specific chrome://flags?[6] Due to privacy and security concerns of Geolocation API, and GamePad API, among others, we would like to have the ability to disable these settings for our distribution. 4) Was any work done to fix outstanding proxy leaks in Chromium, which ignore system proxy settings?[7] Once these issues are resolved we will able to include QTWebengine in our distribution without issue, otherwise we may have to remove it. Due to this being a core package we are hesitant to remove it due to the hundreds of packages now depending upon it. Thank you for your time and concern regarding this important matter. Sincerely, Luke Parabola GNU/Linux-libre Packager https://parabola.nu 1. https://www.gnu.org/distros/free-system-distribution-guidelines.html 2. https://wiki.qt.io/QtWebEngine 3. https://github.com/Eloston/ungoogled-chromium 4. https://www.gnu.org/philosophy/who-does-that-server-really-serve.html 5. http://defectivebydesign.org/ 6. http://stackoverflow.com/questions/17060363/google-chrome-how-can-i-programmatically-enable-chrome-flags-some-of-the-mod 7. https://bugs.chromium.org/p/chromium/issues/detail?id=80722#c33 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From me at herrie.org Tue Jan 24 09:35:40 2017 From: me at herrie.org (Herman van Hazendonk) Date: Tue, 24 Jan 2017 09:35:40 +0100 Subject: [Qtwebengine] QTWebengine compliance with FSDG In-Reply-To: References: Message-ID: Hi Luke, For our little OS distribution LuneOS (based on HP/Palm's open sourced webOS) with various added bits we did the migration to QtWebEngine a while ago (we've went through a number of updates and are at 5.6.x now), so I can share something about our experience: 1. As far as I know this doesn't happen since it's a very stripped down Chromium, but I'm unable to double check & confirm this. You could have a look at https://github.com/qt/qtwebengine-chromium/ to see if there are any clues. Sync, Hangouts etc are for sure not there. 2. a. You need to specifically enable these during the build. See https://github.com/webOS-ports/meta-webos-ports/blob/krogoth/meta-luneui/recipes-qt/qt5/qtwebengine_git.bbappend#L6 what we do in our recipe for this. We use the meta-qt5 layer for this. b. You need to enable this again in your WebEngineView as well like we did here: https://github.com/webOS-ports/luneos-components/blob/master/modules/LuneOS/Components/LunaWebEngineView.qml#L56 3. Not sure what flags you're referring to specifically, but we use the following to enable proprietary (MP3) plugins, use PulseAudio and enable plugins: https://github.com/webOS-ports/meta-webos-ports/blob/krogoth/meta-luneui/recipes-qt/qt5/qtwebengine_git.bbappend#L4 meta-qt5 does something similar for other options: https://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/qt5/qtwebengine_git.bb#L32 For Geolocation API: This is denied by default: You'd need to implement a dialog to allow the user to accept these requests, similar to what we've done here: https://github.com/webOS-ports/luneos-components/blob/master/modules/LuneOS/Components/LunaWebEngineView.qml#L45 4. Not sure, we haven't tested this. meta-qt5 would be a good layer to start with for qtwebengine, a lot of work has been done to get this working properly already on embedded systems, qemux86 etc, so it should save you a lot of work for reinventing the wheel. Best regards, Herrie On 2017-01-24 00:45, Luke wrote: > Hello, > I am currently a packager for Parabola GNU/Linux-libre. While > investigating the change from Webkit to Webengine, I discovered several > concerning issues that affect our compliance with the Free Software > Foundation's Free System Distribution Guidelines (FSDG).[1] I am > hopeful > that some developers will be able to clarify these issues for us as it > affects hundreds of projects downstream including nearly all of KDE, as > well as many QT programs. > > In particular, your website claims it is not just a rendering engine, > "it is the entire Chromium platform."[2] > > If this is true, there are many outstanding issues with Chromium which > we would need to be addressed. > > 1) Was any attempt made to remove Google specific code from Chromium > prior to preparing QTWebengine? > - If not, could ungoogled-chromium patches be applied to your code?[3] > > By default, Chromium has many lines of code that make internet queries > to Google. Building it using the default settings essentially puts your > browser into the cloud. As mentioned in the GNU.org article "Who does > that server really serve?"[4], free software is only free when you are > in control. Any use of Google API, Google Sync, Google Hangouts, and > Google OK, does not classify as free software. > > 2) Is any form of proprietary code such as Adobe pepperflash, webvine > DRM[5], or proprietary codecs included? If so, can they be removed or > disabled with a compile time option? > > 3) Is it possible to compile QTWebengine with specific > chrome://flags?[6] > > Due to privacy and security concerns of Geolocation API, and GamePad > API, among others, we would like to have the ability to disable these > settings for our distribution. > > 4) Was any work done to fix outstanding proxy leaks in Chromium, which > ignore system proxy settings?[7] > > Once these issues are resolved we will able to include QTWebengine in > our distribution without issue, otherwise we may have to remove it. Due > to this being a core package we are hesitant to remove it due to the > hundreds of packages now depending upon it. > > Thank you for your time and concern regarding this important matter. > > > Sincerely, > Luke > Parabola GNU/Linux-libre Packager > https://parabola.nu > > 1. https://www.gnu.org/distros/free-system-distribution-guidelines.html > 2. https://wiki.qt.io/QtWebEngine > 3. https://github.com/Eloston/ungoogled-chromium > 4. > https://www.gnu.org/philosophy/who-does-that-server-really-serve.html > 5. http://defectivebydesign.org/ > 6. > http://stackoverflow.com/questions/17060363/google-chrome-how-can-i-programmatically-enable-chrome-flags-some-of-the-mod > 7. https://bugs.chromium.org/p/chromium/issues/detail?id=80722#c33 > > > > _______________________________________________ > QtWebEngine mailing list > QtWebEngine at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qtwebengine From allan.jensen at qt.io Tue Jan 24 14:48:24 2017 From: allan.jensen at qt.io (Allan Sandfeld Jensen) Date: Tue, 24 Jan 2017 14:48:24 +0100 Subject: [Qtwebengine] QTWebengine compliance with FSDG In-Reply-To: References: Message-ID: <201701241448.24637.allan.jensen@qt.io> On Tuesday 24 January 2017, Luke wrote: > > 1) Was any attempt made to remove Google specific code from Chromium > prior to preparing QTWebengine? > - If not, could ungoogled-chromium patches be applied to your code?[3] > Yes, we remove a large amount of code from Chromium. Note in particular we are using the Chromium content API, not the Chromium browser implementation, which means we are a step lower that most Chromium forks. > By default, Chromium has many lines of code that make internet queries > to Google. Building it using the default settings essentially puts your > browser into the cloud. As mentioned in the GNU.org article "Who does > that server really serve?"[4], free software is only free when you are > in control. Any use of Google API, Google Sync, Google Hangouts, and > Google OK, does not classify as free software. None of that code is included or works at the moment, we might want to enable some of it optionally at some point, but at the moment everything that relies on Google or reports back to Google has not only been disabled, but have been striped from sources. > > 2) Is any form of proprietary code such as Adobe pepperflash, webvine > DRM[5], or proprietary codecs included? If so, can they be removed or > disabled with a compile time option? They are not part of the opensource Chromium project, we support the plugins if they are found on the system or you ship them with your QtWebEngine using application, but we do not ship them. > > 3) Is it possible to compile QTWebengine with specific chrome://flags?[6] > > Due to privacy and security concerns of Geolocation API, and GamePad > API, among others, we would like to have the ability to disable these > settings for our distribution. Many of those are exported through our QWebEngineSettings, and others are not yet implemented. Geolocation and camera sharing is implemented but requires the QtWebEngine using application to approve access (we assume it will ask the user when appropriate). > 4) Was any work done to fix outstanding proxy leaks in Chromium, which > ignore system proxy settings?[7] > We use Qt proxy settings if set, otherwise fall back to the Chromium proxy implementation which should follow system settings. If I read the bug correct you linked, it is about ignoring system settings, and was rejected. Do I read that correct? Best Regards `Allan Jensen -- The Qt Company Rudower Chausse 13, 12489 D-Berlin From Kai.Koehne at qt.io Tue Jan 24 15:14:46 2017 From: Kai.Koehne at qt.io (Kai Koehne) Date: Tue, 24 Jan 2017 14:14:46 +0000 Subject: [Qtwebengine] QTWebengine compliance with FSDG In-Reply-To: References: Message-ID: > -----Original Message----- > From: QtWebEngine [mailto:qtwebengine-bounces+kai.koehne=qt.io at qt- > project.org] On Behalf Of Luke > Sent: Tuesday, January 24, 2017 12:46 AM > To: qtwebengine at qt-project.org > Cc: Parabola Mail List > Subject: [Qtwebengine] QTWebengine compliance with FSDG > > Hello, > I am currently a packager for Parabola GNU/Linux-libre. While investigating > the change from Webkit to Webengine, I discovered several concerning > issues that affect our compliance with the Free Software Foundation's Free > System Distribution Guidelines (FSDG).[1] I am hopeful that some > developers will be able to clarify these issues for us as it affects hundreds of > projects downstream including nearly all of KDE, as well as many QT > programs. > > In particular, your website claims it is not just a rendering engine, "it is the > entire Chromium platform."[2] This means that Qt WebEngine not only use the rendering engine of Chromium, but also the networking stack, plugin architecture etc. It doesn't mean though that we support every single feature of Chrome. > If this is true, there are many outstanding issues with Chromium which we > would need to be addressed. > > 1) Was any attempt made to remove Google specific code from Chromium > prior to preparing QTWebengine? > - If not, could ungoogled-chromium patches be applied to your code?[3] > > By default, Chromium has many lines of code that make internet queries to > Google. Building it using the default settings essentially puts your browser > into the cloud. As mentioned in the GNU.org article "Who does that server > really serve?"[4], free software is only free when you are in control. Any use > of Google API, Google Sync, Google Hangouts, and Google OK, does not > classify as free software. Not sure what you mean by "Google API", but we do not ship code for Google Sync, and Google OK, and do not compile in hangout services. Qt WebEngine should never 'call home' to Google servers. > 2) Is any form of proprietary code such as Adobe pepperflash, webvine > DRM[5], or proprietary codecs included? If so, can they be removed or > disabled with a compile time option? We do not include Adobe Flash, or Widevine (but support finding them at runtime). We ship some proprietary codecs in the sources, these need to be enabled explicitly during build though (default is off). > 3) Is it possible to compile QTWebengine with specific chrome://flags?[6] > > Due to privacy and security concerns of Geolocation API, and GamePad API, > among others, we would like to have the ability to disable these settings for > our distribution. There's no general mechanism, we're open to add compile time flags though for cases where it makes sense. Please file feature requests for these at https://bugreports.qt.io/ . That said, most flags also have matching command line arguments, which you can use with Qt WebEngine, too. > 4) Was any work done to fix outstanding proxy leaks in Chromium, which > ignore system proxy settings?[7] To my knowledge we didn't do any specific patches in this area. Anyhow, the bug you linked is pretty convoluted, so it's hard for me to say in what way it applies to Qt WebEngine. > Once these issues are resolved we will able to include QTWebengine in our > distribution without issue, otherwise we may have to remove it. Due to this > being a core package we are hesitant to remove it due to the hundreds of > packages now depending upon it. Alright, I hope I could clarify some things :) Feel free to ask if you need further information. Regards Kai Koehne > Thank you for your time and concern regarding this important matter. > > > Sincerely, > Luke > Parabola GNU/Linux-libre Packager > https://parabola.nu > > 1. https://www.gnu.org/distros/free-system-distribution-guidelines.html > 2. https://wiki.qt.io/QtWebEngine > 3. https://github.com/Eloston/ungoogled-chromium > 4. https://www.gnu.org/philosophy/who-does-that-server-really-serve.html > 5. http://defectivebydesign.org/ > 6. http://stackoverflow.com/questions/17060363/google-chrome-how-can-i- > programmatically-enable-chrome-flags-some-of-the-mod > 7. https://bugs.chromium.org/p/chromium/issues/detail?id=80722#c33 > From mohammads_32 at yahoo.com Tue Jan 31 10:45:02 2017 From: mohammads_32 at yahoo.com (Mohammad Moradi) Date: Tue, 31 Jan 2017 09:45:02 +0000 (UTC) Subject: [Qtwebengine] QWebengine on ARMv8 References: <1809604089.395703.1485855902879.ref@mail.yahoo.com> Message-ID: <1809604089.395703.1485855902879@mail.yahoo.com> Hello everybody I'm about to build qtwebengine 5.7.0 from sources for RPi3.But it seems the chromium doesn't support armv8!.Is there anyway to have qwebengine on Pi3?I just want to run some java scripts(pdf viewer plugin). *I tried cross compiling* Thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: From jp.kuraisu at gmail.com Tue Jan 31 11:49:20 2017 From: jp.kuraisu at gmail.com (Aleksey Yermakov) Date: Tue, 31 Jan 2017 13:49:20 +0300 Subject: [Qtwebengine] QWebengine on ARMv8 In-Reply-To: <1809604089.395703.1485855902879@mail.yahoo.com> References: <1809604089.395703.1485855902879.ref@mail.yahoo.com> <1809604089.395703.1485855902879@mail.yahoo.com> Message-ID: Hi Mohammad, As I understood from some googling and this article https://www.chromium.org/developers/how-tos/android-build-instructions, Chromium does support armv8 at least for android as a target OS. Could you please describe, what are you trying to do with it on Pi 3? Maybe there is a better way for it than using qtwebengine. Cheers, Aleksey On Tue, Jan 31, 2017 at 12:45 PM, Mohammad Moradi via QtWebEngine < qtwebengine at qt-project.org> wrote: > Hello everybody > > I'm about to build qtwebengine 5.7.0 from sources for RPi3. > But it seems the chromium doesn't support armv8!. > Is there anyway to have qwebengine on Pi3? > I just want to run some java scripts(pdf viewer plugin). > *I tried cross compiling* > > Thank you > > _______________________________________________ > QtWebEngine mailing list > QtWebEngine at qt-project.org > http://lists.qt-project.org/mailman/listinfo/qtwebengine > > -- Aleksey Yermakov -------------- next part -------------- An HTML attachment was scrubbed... URL: From jp.kuraisu at gmail.com Tue Jan 31 13:42:46 2017 From: jp.kuraisu at gmail.com (Aleksey Yermakov) Date: Tue, 31 Jan 2017 15:42:46 +0300 Subject: [Qtwebengine] QWebengine on ARMv8 In-Reply-To: <1253941520.439294.1485865681272@mail.yahoo.com> References: <1809604089.395703.1485855902879.ref@mail.yahoo.com> <1809604089.395703.1485855902879@mail.yahoo.com> <1253941520.439294.1485865681272@mail.yahoo.com> Message-ID: Hi Mohammad, Patch looks ok to me (just sets a build configuration variable). Still, please describe a problem you're trying to solve with qtwebengine. I think there could be another, possibly more simple solution. >From your first email I've understood that your problem has something to do with PDF? P.S. Please, use "Reply to All", so that your problem and solution would be available in mail list archives. Cheers, Aleksey On Tue, Jan 31, 2017 at 3:28 PM, Mohammad Moradi wrote: > Found a solution but i'm not sure, it's still compiling... > > I extracted the "qtwebengine" from source 5.7.0 and tried to compile: > http://pastebin.com/wcy3Gzdu. The error is at line 53, related to the > 'arm_fpu'. > I asked from guys on irc channel(#qtwebengine), some one recommended to > use this patch: https://paste.kde.org/pv55fowbf. It's still compiling[not > home, using a corei3 laptop :( ]. > But I'm not sure if it's a good way to build qtwebengine. Since the patch > is not official, I afraid it causes some problem in future use. > > > > > > > > On Tuesday, January 31, 2017 2:19 PM, Aleksey Yermakov < > jp.kuraisu at gmail.com> wrote: > > > Hi Mohammad, > > As I understood from some googling and this article > https://www.chromium.org/developers/how-tos/android-build-instructions, > Chromium does support armv8 at least for android as a target OS. > > Could you please describe, what are you trying to do with it on Pi 3? > Maybe there is a better way for it than using qtwebengine. > > Cheers, > Aleksey > > > On Tue, Jan 31, 2017 at 12:45 PM, Mohammad Moradi via QtWebEngine < > qtwebengine at qt-project.org> wrote: > > Hello everybody > > I'm about to build qtwebengine 5.7.0 from sources for RPi3. > But it seems the chromium doesn't support armv8!. > Is there anyway to have qwebengine on Pi3? > I just want to run some java scripts(pdf viewer plugin). > *I tried cross compiling* > > Thank you > > ______________________________ _________________ > QtWebEngine mailing list > QtWebEngine at qt-project.org > http://lists.qt-project.org/ mailman/listinfo/qtwebengine > > > > > > -- > Aleksey Yermakov > > > > -- Aleksey Yermakov -------------- next part -------------- An HTML attachment was scrubbed... URL: From allan.jensen at qt.io Tue Jan 31 15:28:11 2017 From: allan.jensen at qt.io (Allan Sandfeld Jensen) Date: Tue, 31 Jan 2017 15:28:11 +0100 Subject: [Qtwebengine] QWebengine on ARMv8 In-Reply-To: <1809604089.395703.1485855902879@mail.yahoo.com> References: <1809604089.395703.1485855902879.ref@mail.yahoo.com> <1809604089.395703.1485855902879@mail.yahoo.com> Message-ID: <201701311528.11360.allan.jensen@qt.io> On Tuesday 31 January 2017, Mohammad Moradi via QtWebEngine wrote: > Hello everybody > I'm about to build qtwebengine 5.7.0 from sources for RPi3.But it seems > the chromium doesn't support armv8!.Is there anyway to have qwebengine on > Pi3?I just want to run some java scripts(pdf viewer plugin). *I tried > cross compiling* > Thank you You could probably change gyp_run.pro and set arm_version=7 or fix Chromium in src/3rdparty/chromium/build/common.gypi (look for the line matching arm_version to either 6 or 7 but not 8. `Allan -- The Qt Company Rudower Chausse 13, 12489 D-Berlin From allan.jensen at qt.io Tue Jan 31 15:43:20 2017 From: allan.jensen at qt.io (Allan Sandfeld Jensen) Date: Tue, 31 Jan 2017 15:43:20 +0100 Subject: [Qtwebengine] QWebengine on ARMv8 In-Reply-To: <201701311528.11360.allan.jensen@qt.io> References: <1809604089.395703.1485855902879.ref@mail.yahoo.com> <1809604089.395703.1485855902879@mail.yahoo.com> <201701311528.11360.allan.jensen@qt.io> Message-ID: <201701311543.20607.allan.jensen@qt.io> On Tuesday 31 January 2017, Allan Sandfeld Jensen wrote: > On Tuesday 31 January 2017, Mohammad Moradi via QtWebEngine wrote: > > Hello everybody > > > > I'm about to build qtwebengine 5.7.0 from sources for RPi3.But it seems > > > > the chromium doesn't support armv8!.Is there anyway to have qwebengine on > > Pi3?I just want to run some java scripts(pdf viewer plugin). *I tried > > cross compiling* > > Thank you > > You could probably change gyp_run.pro and set arm_version=7 or fix Chromium > in src/3rdparty/chromium/build/common.gypi (look for the line matching > arm_version to either 6 or 7 but not 8. > Though it probably wouldn't be necessary to change this if you had set an mfpu compiler flag to go with the march flag. Like -march=armv8-a -mfpu=neon-fp- armv8 for some reason architecture flags on ARM doesn't imply otherwise mandatory "fpu" features. -- The Qt Company Rudower Chausse 13, 12489 D-Berlin From mohammads_32 at yahoo.com Tue Jan 31 17:41:50 2017 From: mohammads_32 at yahoo.com (Mohammad Moradi) Date: Tue, 31 Jan 2017 16:41:50 +0000 (UTC) Subject: [Qtwebengine] QWebengine on ARMv8 In-Reply-To: <711992483.610133.1485880846921@mail.yahoo.com> References: <1809604089.395703.1485855902879.ref@mail.yahoo.com> <1809604089.395703.1485855902879@mail.yahoo.com> <201701311528.11360.allan.jensen@qt.io> <201701311543.20607.allan.jensen@qt.io> <711992483.610133.1485880846921@mail.yahoo.com> Message-ID: <606496766.635275.1485880910496@mail.yahoo.com> Hi AllanI guess the errors related to arch has been solved by adding arm_fpu=\"\" to the GYP_CONFIG. However I still don't know what is it doing. For now, I have to fix this problem :(http://pastebin.com/6YF0Y0uf On Tuesday, January 31, 2017 6:13 PM, Allan Sandfeld Jensen wrote: On Tuesday 31 January 2017, Allan Sandfeld Jensen wrote: > On Tuesday 31 January 2017, Mohammad Moradi via QtWebEngine wrote: > > Hello everybody > > > >  I'm about to build qtwebengine 5.7.0 from sources for RPi3.But it seems > > > > the chromium doesn't support armv8!.Is there anyway to have qwebengine on > > Pi3?I just want to run some java scripts(pdf viewer plugin). *I tried > > cross compiling* > > Thank you > > You could probably change gyp_run.pro and set arm_version=7 or fix Chromium > in src/3rdparty/chromium/build/common.gypi (look for the line matching > arm_version to either 6 or 7 but not 8. > Though it probably wouldn't be necessary to change this if you had set an mfpu compiler flag to go with the march flag. Like -march=armv8-a -mfpu=neon-fp- armv8 for some reason architecture flags on ARM doesn't imply otherwise mandatory "fpu" features. -- The Qt Company Rudower Chausse 13, 12489 D-Berlin _______________________________________________ QtWebEngine mailing list QtWebEngine at qt-project.org http://lists.qt-project.org/mailman/listinfo/qtwebengine -------------- next part -------------- An HTML attachment was scrubbed... URL: