Florian Bruhin

That's intended, as for many cases, qutebrowser doesn't know where an error message is coming from (and there isn't always a focused window).

@edrex Sorry for the late answer, this got lost in my inbox for a bit! For prompts the situation is indeed very tricky (some are synchronous, some are asynchronous, some...

Also see #5535 for prompts.

Chromium can closely tie their low-level API to whatever their UI needs, while with qutebrowser there are more layers in between that constrain how a solution can look like.

Yup, indeed! Qt 5 support will be dropped soon-ish anyways though, see #8417. Hopefully that will make those kind of things a fair bit easier.

Thanks for the detailed description! To be completely honest, given this has been around for 4.5 years and this is the first complaint I hear, I won't be spending any...

I'm not really interested in all the additional complexity if it doesn't solve a real-world issue. Why do you need to build your own custom builds in the first place?

In #8614 @jasondh mentions this happens after upgrading to v3.5.1, i.e. Qt 6.9.1 (assuming from v3.5.0, i.e. Qt 6.9.0?). Can't immediately spot something relevant in the [release notes](https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.9.1/release-note.md), the only...

> not sure how appropriate passing all this around is Instead of changing all `url_handlers`, you could: - Move `run_cmd`, `preset_cmd_text` and `spawn` to `elem_handlers` (which already get the element...

Note that for freezegun specificially, there is [pytest-dev/pytest-freezer](https://github.com/pytest-dev/pytest-freezer) you might want to use instead of hand-rolling a fixture.