summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFlorian Bruhin <me@the-compiler.org>2019-12-26 21:52:47 +0100
committerFlorian Bruhin <me@the-compiler.org>2019-12-26 21:52:47 +0100
commit998ccf151505712c873c26aea67e5f7a7c1d3f2f (patch)
tree99e9977af287779ca6a9773488446e425d0e22d2
parentb70683d31c86490c6a33ece93ff596d8f9388a97 (diff)
downloadqutebrowser-998ccf151505712c873c26aea67e5f7a7c1d3f2f.tar.gz
qutebrowser-998ccf151505712c873c26aea67e5f7a7c1d3f2f.zip
Use a Firefox UA for all accounts.google.com pages
Looks like at least for some users, /signin/... needs a Firefox UA to make the workaround work. Given that accounts.google.com only is used for things related to the sign-in form (settings live at myaccount.google.com), let's take a slightly bigger hammer and use a Firefox UA for the entire subdomain. See #5147, #4810
-rw-r--r--qutebrowser/browser/webengine/webenginesettings.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/qutebrowser/browser/webengine/webenginesettings.py b/qutebrowser/browser/webengine/webenginesettings.py
index fcdbd7d7e..77ca3a8e1 100644
--- a/qutebrowser/browser/webengine/webenginesettings.py
+++ b/qutebrowser/browser/webengine/webenginesettings.py
@@ -351,7 +351,7 @@ def _init_site_specific_quirks():
user_agents = {
'https://web.whatsapp.com/': no_qtwe_ua,
- 'https://accounts.google.com/ServiceLogin': firefox_ua,
+ 'https://accounts.google.com/*': firefox_ua,
'https://*.slack.com/*': new_chrome_ua,
'https://docs.google.com/*': firefox_ua,
}