Bug 390745 - Request Of New Features For Falkon/QupZilla
Summary: Request Of New Features For Falkon/QupZilla
Status: RESOLVED NOT A BUG
Alias: None
Product: Falkon
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-19 16:41 UTC by Alberto Díaz López
Modified: 2018-02-19 17:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alberto Díaz López 2018-02-19 16:41:08 UTC
I have been using Falkon/QupZilla since 2 days as the main web browser on my system. And i would like to request and comment new features that i think improve the UX and the quality of the software.
1: Update to latests versions of the software core, at "About QupZilla" window, i see that the Chrome/Chromium version mentioned is 61.x, being the actual on stable channel, the 64.x. I think the update of these core parts would be better for the performance of the web browser.
2: Deloper tools. I notified since the first day i tried this software (about 4 weeks ago more or less), that i can't open any developer tools or anything like that, (i tried with the habitual keyboard shortcuts, like F12, Ctrl-Shift-I but nothing opened, even searching for any of that at the options, but i didn't find anything) and i think this is an essential feature for this kind of software.
3: Advanced options. I can't see any advanced options, like on Firefox is "about:config" or the flags on Chromium/Chrome etc. I would like to have this on this software, to configure some advanced parameters, like the way that the web browser reacts to a click on the URL bar, and if the url is selected, double click on it, trim the URL or not, etc.
4: Support of the plugins. I'm not a heavy user of this kind of addons/plugins/extensions, however you prefer to call them. But i really would like to can install uBlock Origin (yeah, i know that QupZilla/Falcon has its own adblocker but uBlock Origin is for me, better, because it's FOSS too, and above all, it allows much more configurability than i have seen on the built-in adblock) or some others plugins, available on Chromium/Firefox, etc.
I really have a lot of hope on this web browser and i would like to use it as an alternative that hasn't got any difference of base features when it's compared with Firefox, Chromium and that. I have to add that the Speed Dial (a feature that i never found on Firefox or Chromium and i missed very much from Opera, Maxthon, Vivaldi, etc) is really great, i didn't try it a lot, but looks great, and i remember from Opera too, the feature to could change the wallpaper on that screen, just amazing.
Comment 1 David Rosca 2018-02-19 16:48:14 UTC
1. That depends on QtWebEngine. New Qt release usually ships with QtWebEngine based on newer Chromium.
2. Developer tools can be enabled by setting QTWEBENGINE_REMOTE_DEBUGGING=12345 env variable (you can use any port you like, 12345 in this example). QtWebEngine 5.11 will have proper developer tools without this hack.
3. Advanced options are in preferences, I don't see any reason for this.
4. AdBlock implementation can be improved, but if you really want uBlock you should write to the uBlock addon developer.
There is a GSoC project to add support for JavaScript/QML extension which should make writing extensions easier.
Comment 2 David Rosca 2018-02-19 16:49:10 UTC
Also this is not a way to request new features. Each bugreport should only have one separate bug/feature.
Comment 3 Alberto Díaz López 2018-02-19 17:01:59 UTC
(In reply to David Rosca from comment #1)
> 1. That depends on QtWebEngine. New Qt release usually ships with
> QtWebEngine based on newer Chromium.
> 2. Developer tools can be enabled by setting
> QTWEBENGINE_REMOTE_DEBUGGING=12345 env variable (you can use any port you
> like, 12345 in this example). QtWebEngine 5.11 will have proper developer
> tools without this hack.
> 3. Advanced options are in preferences, I don't see any reason for this.
> 4. AdBlock implementation can be improved, but if you really want uBlock you
> should write to the uBlock addon developer.
> There is a GSoC project to add support for JavaScript/QML extension which
> should make writing extensions easier.

Thanks, i read something about that yeah, on Twitter, i'm very excited about that.
2: So basically at the future, the developer tools will be implemented as native? With QtWebEngine, right?
3: I saw them, but there are only 4 options on the Appearance, what i can see and there are not what i mean, i mean, some really advanced options, related to, as i said, like in Mozilla Firefox, is about:config, i suppose you know it, but there are a lot of options, which change the behavior of the software.
4: Ok, i will write him to telling that.
Thanks for your surprisingly speed responses and thanks for your hard work.
Receive a huge hug.
Comment 4 Alberto Díaz López 2018-02-19 17:02:56 UTC
(In reply to David Rosca from comment #2)
> Also this is not a way to request new features. Each bugreport should only
> have one separate bug/feature.

Ok, sorry for that, thanks for the explanation, i will take in consideration at the future.
Comment 5 Alberto Díaz López 2018-02-19 17:04:25 UTC
(In reply to Alberto Díaz López from comment #3)
> (In reply to David Rosca from comment #1)
> > 1. That depends on QtWebEngine. New Qt release usually ships with
> > QtWebEngine based on newer Chromium.
> > 2. Developer tools can be enabled by setting
> > QTWEBENGINE_REMOTE_DEBUGGING=12345 env variable (you can use any port you
> > like, 12345 in this example). QtWebEngine 5.11 will have proper developer
> > tools without this hack.
> > 3. Advanced options are in preferences, I don't see any reason for this.
> > 4. AdBlock implementation can be improved, but if you really want uBlock you
> > should write to the uBlock addon developer.
> > There is a GSoC project to add support for JavaScript/QML extension which
> > should make writing extensions easier.
> 
> Thanks, i read something about that yeah, on Twitter, i'm very excited about
> that.
> 2: So basically at the future, the developer tools will be implemented as
> native? With QtWebEngine, right?
> 3: I saw them, but there are only 4 options on the Appearance, what i can
> see and there are not what i mean, i mean, some really advanced options,
> related to, as i said, like in Mozilla Firefox, is about:config, i suppose
> you know it, but there are a lot of options, which change the behavior of
> the software.
> 4: Ok, i will write him to telling that.
> Thanks for your surprisingly speed responses and thanks for your hard work.
> Receive a huge hug.

I add to the previous comment,
1: Ok, so there is no responsibility of Falkon/QupZilla, because it delegates into QtWebEngine for that.
Thanks and sorry for the inconveniences.