Florian Bruhin

One more thing coming to mind: `options` would probably be best renamed to `choices` or so, to avoid sounding similar to the completely different `option` argument.

Regarding the first question, looking at [a failing `downloads.feature` test](https://github.com/qutebrowser/qutebrowser/actions/runs/16539424807/job/46778534815?pr=8642#step:10:39): ``` Error: E end2end.fixtures.testprocess.WaitForTimeout: Timed out after 15000ms waiting for {'message': "Asking question , *"}. ``` and ``` 11:39:46.417 DEBUG...

I don't see anything related to the import there - it (correctly) points out that `self._request` can be `None` and the functions don't guard against that (because technically, nothing guarantees...

Looks like the bulk of failures is gone, and only two things are left: - Python 3.14 failing: This is a change in Python 3.14 rc1 (not present in Beta...

> This seems to work for the import and the signal but it still fails for all methods that use the `QWebEngineWebAuthUxRequest` object. Hmm, right. It's a bit hacky, but...

I managed to get mypy to cooperate while adding some more type annotations, took the freedom to push that to your branch (so you should `git pull` before continuing things)....

Huh? None of the comments displayed currently at https://github.com/qutebrowser/qutebrowser/pull/8642/files seem to be resolved, e.g.:

Sorry for the radio silence, was focused on Qt 6.10 things and getting v3.6.0 out as soon as possible. Now that that's taken care of, planning to get back to...

With "two instances", do you mean "two windows but in the same instance" (which is at least what your reproduction steps seem to hint at)? Also, weird that you can't...

Bisected to 331bc1be4634cf95fdb33021d4355c35723b73fe: - #11041 As a workaround, `--assert=plain` works. cc @aless10