Per domain settings #27
Comments
This also deals with custom stylesheets. IMHO it's best to configure with regexes against the entire URI. |
#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. |
A nice addition to this would be "force https per domain". |
stylesheet Of course, this means that attempting to use any of these fonts on *any* site will result in it being replaced with the selections here. Ideally this should only be done on particular sites as seen fit. This can be fixed when qutebrowser gains the ability to have per-domain settings [1]. [1]: qutebrowser/qutebrowser#27
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). |
Note to myself so this doesn't get lost; a hack to use possibly use a
|
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. |
Something else needed for full uBO-equivalent functionality: gorhill/uBlock#3374 |
@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:
|
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? |
@Zekario Should be possible with QtWebEngine, see #2626. |
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 If you want to try it out (and I'd love some feedback!), check the |
I now opened a PR for this: #3618 - if you have the time to take a look at it (code/functionality), please do! |
Sweet! Now that my favorite FF extensions are being abandoned/watered down I'm waiting for this to make qutebrowser my full time browser. |
It's been a while™, but this is finally ready and merged into The remaining bits are split across various issues: |
how do you actually use this then? I'd like to set custom css for a specific site. |
Right now stylesheets dosen't have patterns implemented, see #3854. There's examples on setting pattern settings in the configuration documentation, for both |
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)
|
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:
The text was updated successfully, but these errors were encountered: