Per domain settings

[The-Compiler]

For all settings where this makes sense, the setting should be configurable per domain (or probably even protocol/domain/port triple).

This will make a lot of things easier:

• NoScript is essentially done then
• RequestPolicy is a lot easier
• etc.

[Ram-Z]

This also deals with custom stylesheets.

IMHO it's best to configure with regexes against the entire URI.

[Ram-Z]

This also deals with custom stylesheets.

IMHO it's best to configure with regexes against the entire URI.

[The-Compiler]

#499 should be done first. Setting the milestone to v0.3 as I really want to see this, but should get v0.2 out first.

[The-Compiler]

#499 should be done first. Setting the milestone to v0.3 as I really want to see this, but should get v0.2 out first.

[iggy]

A nice addition to this would be "force https per domain".

[iggy]

A nice addition to this would be "force https per domain".

[The-Compiler]

@iggy - also see #335 for that :)

[The-Compiler]

@iggy - also see #335 for that :)

[rcorre]

from the mailing list discussion: per-domain user-agents would be useful (right now I need one user-agent for google hangouts and another for github).

[rcorre]

from the mailing list discussion: per-domain user-agents would be useful (right now I need one user-agent for google hangouts and another for github).

[The-Compiler]

Note to myself so this doesn't get lost; a hack to use possibly use a QWebEngineUrlRequestInterceptor per page (e.g. for headers):

16:59 <The-Compiler> carewolf, Emdek: Looking at QTBUG-53372 I wonder... would it be possible/useful to be able to attach an arbitrary identifier (say, a QString, think e.g. UUID) to a request (and sub-requests?) to be able to identify them in different places, like in a QWebEngineUrlRequestInterceptor?
16:59 <qt_gerrit> carewolf, Custom load options - https://bugreports.qt.io/browse/QTBUG-53372 (Reported)
16:59 <The-Compiler> just brainstorming here though :)
17:00 <@carewolf> you could just put anything in there already, and rewrite them in the interceptor if you want
17:01 <The-Compiler> carewolf: put anything in where?
17:02 <@carewolf> you can use invalid URLs and rewrite them to something valid
17:02 <@carewolf> I think (haven't tried)
17:03 <The-Compiler> that's... horrib... eh, I mean really clever.
17:03 <The-Compiler> ;)
17:04 <@carewolf> You can look at NavigatorController:LoadURLParams for what we can pass to Chromium

[The-Compiler]

Note to myself so this doesn't get lost; a hack to use possibly use a QWebEngineUrlRequestInterceptor per page (e.g. for headers):

16:59 <The-Compiler> carewolf, Emdek: Looking at QTBUG-53372 I wonder... would it be possible/useful to be able to attach an arbitrary identifier (say, a QString, think e.g. UUID) to a request (and sub-requests?) to be able to identify them in different places, like in a QWebEngineUrlRequestInterceptor?
16:59 <qt_gerrit> carewolf, Custom load options - https://bugreports.qt.io/browse/QTBUG-53372 (Reported)
16:59 <The-Compiler> just brainstorming here though :)
17:00 <@carewolf> you could just put anything in there already, and rewrite them in the interceptor if you want
17:01 <The-Compiler> carewolf: put anything in where?
17:02 <@carewolf> you can use invalid URLs and rewrite them to something valid
17:02 <@carewolf> I think (haven't tried)
17:03 <The-Compiler> that's... horrib... eh, I mean really clever.
17:03 <The-Compiler> ;)
17:04 <@carewolf> You can look at NavigatorController:LoadURLParams for what we can pass to Chromium

[haasn]

@The-Compiler thanks for the pointers; this works very well:

diff --git a/qutebrowser/browser/webkit/webpage.py b/qutebrowser/browser/webkit/webpage.py
index 7e1d991b9..fec6d0f49 100644
--- a/qutebrowser/browser/webkit/webpage.py
+++ b/qutebrowser/browser/webkit/webpage.py
@@ -366,11 +366,19 @@ class BrowserPage(QWebPage):
 
     def userAgentForUrl(self, url):
         """Override QWebPage::userAgentForUrl to customize the user agent."""
-        ua = config.val.content.headers.user_agent
+
+        special_agents = {
+            # Infinite redirect loop / garbage otherwise
+            'twitter.com': 'Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html',
+        }
+
+        ua = special_agents.get(url.host())
         if ua is None:
-            return super().userAgentForUrl(url)
-        else:
-            return ua
+            ua = config.val.content.headers.user_agent
+        if ua is None:
+            ua = super().userAgentForUrl(url)
+
+        return ua
 
     def supportsExtension(self, ext):
         """Override QWebPage::supportsExtension to provide error pages.

Now twitter links work again, for starters. :p Honestly this seems useful enough that I wonder if perhaps the user_agents thing couldn't just (easily?) be turned into a host/agent dictionary in the qutebrowser settings using essentially the same code. This would solve the problem for me and perhaps some others.

[haasn]

@The-Compiler thanks for the pointers; this works very well:

diff --git a/qutebrowser/browser/webkit/webpage.py b/qutebrowser/browser/webkit/webpage.py
index 7e1d991b9..fec6d0f49 100644
--- a/qutebrowser/browser/webkit/webpage.py
+++ b/qutebrowser/browser/webkit/webpage.py
@@ -366,11 +366,19 @@ class BrowserPage(QWebPage):
 
     def userAgentForUrl(self, url):
         """Override QWebPage::userAgentForUrl to customize the user agent."""
-        ua = config.val.content.headers.user_agent
+
+        special_agents = {
+            # Infinite redirect loop / garbage otherwise
+            'twitter.com': 'Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html',
+        }
+
+        ua = special_agents.get(url.host())
         if ua is None:
-            return super().userAgentForUrl(url)
-        else:
-            return ua
+            ua = config.val.content.headers.user_agent
+        if ua is None:
+            ua = super().userAgentForUrl(url)
+
+        return ua
 
     def supportsExtension(self, ext):
         """Override QWebPage::supportsExtension to provide error pages.

Now twitter links work again, for starters. :p Honestly this seems useful enough that I wonder if perhaps the user_agents thing couldn't just (easily?) be turned into a host/agent dictionary in the qutebrowser settings using essentially the same code. This would solve the problem for me and perhaps some others.

[The-Compiler]

I really haven't heard of people needing per-domain user agents much with QtWebEngine (and neither with QtWebKit 5.212). I'm not really keen on having a temporary half-baked solution for this which gets removed again as soon as per-domain settings are in.

[The-Compiler]

I really haven't heard of people needing per-domain user agents much with QtWebEngine (and neither with QtWebKit 5.212). I'm not really keen on having a temporary half-baked solution for this which gets removed again as soon as per-domain settings are in.

[SirCmpwn]

fwiw I'm not in it for per-domain user agents, but per-domain JavaScript toggles, macros/keybindings, etc

[SirCmpwn]

fwiw I'm not in it for per-domain user agents, but per-domain JavaScript toggles, macros/keybindings, etc

[MichaelMackus]

I agree. The main use-case for this for me would be a NoScript-like setup. Is there any way to hack the enable javascript setting like @haasn did here?

[MichaelMackus]

I agree. The main use-case for this for me would be a NoScript-like setup. Is there any way to hack the enable javascript setting like @haasn did here?

[The-Compiler]

Probably not as easily as there isn't a simple mechanism for per-domain settings in QtWebKit/QtWebEngine, qutebrowser needs to adjust them at the right point in time by itself.

[The-Compiler]

Probably not as easily as there isn't a simple mechanism for per-domain settings in QtWebKit/QtWebEngine, qutebrowser needs to adjust them at the right point in time by itself.

[tidux]

Something else needed for full uBO-equivalent functionality: gorhill/uBlock#3374

[tidux]

Something else needed for full uBO-equivalent functionality: gorhill/uBlock#3374

[The-Compiler]

@tidux That seems unrelated to per-domain settings and would probably better fit in #29. The domains should probably be submitted to the blocklists qutebrowser uses. Also, note that this probably applies to qutebrowser too:

For Chromium-based browsers, there is no solution until their extensions API allows for modifying the response body data on the fly.

[The-Compiler]

@tidux That seems unrelated to per-domain settings and would probably better fit in #29. The domains should probably be submitted to the blocklists qutebrowser uses. Also, note that this probably applies to qutebrowser too:

For Chromium-based browsers, there is no solution until their extensions API allows for modifying the response body data on the fly.

[ghost]

Would it be possible to disable remote fonts per domain? If so, would it also be possible to disable them by default and then enable them per domain? Or is it impossible because the backend handles that?

[ghost]

Would it be possible to disable remote fonts per domain? If so, would it also be possible to disable them by default and then enable them per domain? Or is it impossible because the backend handles that?

[The-Compiler]

@Zekario Should be possible with QtWebEngine, see #2626.

[The-Compiler]

@Zekario Should be possible with QtWebEngine, see #2626.

[The-Compiler]

Sooo... good news! After some hard work over the past few days, this is now nearly ready! 🎉

It still has some issues (like needing a refresh for some settings with QtWebEngine), and only supports a few settings (search for "pattern"). However, I think it's ready to merge in this stage with further improvements coming later after it's in the master branch.

If you want to try it out (and I'd love some feedback!), check the per-url branch. Note that you should back up your ~/.config/qutebrowser/autoconfig.yml as it'll be migrated to a format the master branch can't read.

[The-Compiler]

Sooo... good news! After some hard work over the past few days, this is now nearly ready! 🎉

It still has some issues (like needing a refresh for some settings with QtWebEngine), and only supports a few settings (search for "pattern"). However, I think it's ready to merge in this stage with further improvements coming later after it's in the master branch.

If you want to try it out (and I'd love some feedback!), check the per-url branch. Note that you should back up your ~/.config/qutebrowser/autoconfig.yml as it'll be migrated to a format the master branch can't read.

[The-Compiler]

I now opened a PR for this: #3618 - if you have the time to take a look at it (code/functionality), please do!

[The-Compiler]

I now opened a PR for this: #3618 - if you have the time to take a look at it (code/functionality), please do!

[MichaelMackus]

Sweet! Now that my favorite FF extensions are being abandoned/watered down I'm waiting for this to make qutebrowser my full time browser.

[MichaelMackus]

Sweet! Now that my favorite FF extensions are being abandoned/watered down I'm waiting for this to make qutebrowser my full time browser.

[The-Compiler]

It's been a while™, but this is finally ready and merged into master! 🎉 I think I found workarounds for most annoying issues I've found (such as needing to reload manually to turn on/off JS). If you notice some issues, please let me know!

The remaining bits are split across various issues:

• #3622 (various small remaining issues)
• #2626, #3636 (support for more settings) (nice issue IDs 😆)
• #28 (support for a second URL in settings, uMatrix-/request-policy like)

[The-Compiler]

It's been a while™, but this is finally ready and merged into master! 🎉 I think I found workarounds for most annoying issues I've found (such as needing to reload manually to turn on/off JS). If you notice some issues, please let me know!

The remaining bits are split across various issues:

• #3622 (various small remaining issues)
• #2626, #3636 (support for more settings) (nice issue IDs 😆)
• #28 (support for a second URL in settings, uMatrix-/request-policy like)

[dessalines]

how do you actually use this then? I'd like to set custom css for a specific site.

[dessalines]

how do you actually use this then? I'd like to set custom css for a specific site.

[jgkamat]

Right now stylesheets dosen't have patterns implemented, see #3854.

There's examples on setting pattern settings in the configuration documentation, for both :set and config.py. Whether a setting supports patterns is visible on it's :help page.

[jgkamat]

Right now stylesheets dosen't have patterns implemented, see #3854.

There's examples on setting pattern settings in the configuration documentation, for both :set and config.py. Whether a setting supports patterns is visible on it's :help page.

[jcjordyn130]

I have a pr and it mostly works, if you're alright with running from a git repo

On Fri, Apr 27, 2018 at 20:31 Jay Kamat ***@***.***> wrote: Right now stylesheets dosen't have patterns implemented, see #3854 <#3854>. There's examples on setting pattern settings in the configuration documentation <http://qutebrowser.org/doc/help/configuring.html>, for both :set and config.py. Whether a setting supports patterns is visible on it's :help page. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#27 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AK2v6jXQZjRxtaIkSSQ2s8IyzsIv3jzpks5ts8aAgaJpZM4CpdC5> .

-- Jordyn Carattini (The Linux Geek)

[jcjordyn130]

I have a pr and it mostly works, if you're alright with running from a git repo

On Fri, Apr 27, 2018 at 20:31 Jay Kamat ***@***.***> wrote: Right now stylesheets dosen't have patterns implemented, see #3854 <#3854>. There's examples on setting pattern settings in the configuration documentation <http://qutebrowser.org/doc/help/configuring.html>, for both :set and config.py. Whether a setting supports patterns is visible on it's :help page. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#27 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AK2v6jXQZjRxtaIkSSQ2s8IyzsIv3jzpks5ts8aAgaJpZM4CpdC5> .

-- Jordyn Carattini (The Linux Geek)