5 ms·
Note that setting that UA globally is a bad idea - it'll break stuff on various other websites. You might want to try setting it with a `https://accounts.google
by The-Compiler 7y ago
Note that setting that UA globally is a bad idea - it'll break stuff on various other websites. You might want to try setting it with a `https://accounts.google.com/*` https://accounts.google.com/*` URL pattern - or ideally, even only `https://accounts.google.com/signin` https://accounts.google.com/signin` or so, if that works. Please let me know what works and what doesn't, as I still can't reproduce this with my own Google account.
- krageon 7y ago> setting that UA globally is a bad idea What exactly will it break?
- The-Compiler 7y agoI often talk to people reporting a broken website in qutebrowser where it turns out to be due to a Firefox user agent. Some examples (there are lots more via IRC/Reddit/...): https://github.com/qutebrowser/qutebrowser/issues/4302 https://github.com/qutebrowser/qutebrowser/issues/4302 https://github.com/qutebrowser/qutebrowser/issues/3822 https://github.com/qutebrowser/qutebrowser/issues/3822 https://github.com/qutebrowser/qutebrowser/issues/1187 https://github.com/qutebrowser/qutebrowser/issues/1187
- Lammy 7y agoIt can be the result of programming in the style of > if(browser == firefox) {new_feature_chrome_does_not_support()} else {old_feature()} instead of > if(new_feature in navigator) {new_feature()} else {old_feature()}