Jump to content

Text boxes don't load in qutebrowser

LloydLynx

Browser, version and OS: 

qutebrowser v2.0.2
Backend: QtWebEngine (Chromium 83.0.4103.122)
Qt: 5.15.2

CPython: 3.9.2
PyQt: 5.15.2

Debian 11

 

Steps to reproduce/what were you doing before it happened?

Google doesn't allow accounts to be logged into from from many lesser known browsers. There is a workaround for qutebrowser here that changes the user agent, which then the user can log into their Google account. It's suppose to only change the user agent for accounts.google.com. Since applying this fix, text boxes on linustechtips.com don't load.

 

What happened?

Text boxes won't load except for the "Drag files here to attach..." part of the box. Title boxes seem to work fine.

 

What did you expect to happen?

For the text box to load and work properly.

 

Link to a page where it happened, if applicable: 

Creating topics, status updates, replying in threads, etc...

 

Screenshots of the issue, if applicable: 

677188216_Screenshotat2021-10-3020-32-39.thumb.png.4e34cfc8ac8cb29e67c2f30700ccbe0b.png

1877790582_Screenshotat2021-10-3020-33-02.thumb.png.ad592287f189d2c00fb3e98e735220e9.png

1358747511_Screenshotat2021-10-3020-34-11.thumb.png.158547d404e2d2e81d8a81e8c8081b53.png

 

Any other relevant details:

The LTT forum has worked perfectly in qutebrowser for a long time, until today when I applied the fix for Google account logins.

 

whatsmybrowser.org reports my browser as "Default Browser".

622372125_Screenshotat2021-10-3020-45-42.thumb.png.58ee4a26a9a497ff0391d6a819f0f239.png

lumpy chunks

 

Expand to help Bunny reach world domination

(\__/)
(='.'=) This is Bunny. Copy Bunny into your signature to
(")_(") help him on his way to world domination.

 -Rakshit Jain

Link to comment
Share on other sites

Link to post
Share on other sites

Sorry, we don't formally support qutebrowser, especially if they're caused by weird hacks like that. Issues with the editor like this tend to be pretty difficult to debug and fix, which simply isn't worth the time for an issue that only affects one person. There are a number of browser-specific workarounds in the editor, so pretending to be a different browser could potentially cause problems. If you're able confirm that it is caused by the config change (eg by disabling it and verifying that it works again), I suggest raising it with the browser devs, since their site-specific config clearly isn't working quite right.

HTTP/2 203

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×