Florian Bruhin

I can reproduce via `qutebrowser --temp-basedir -s content.local_storage false ":cmd-later 1000 devtools"`. Also see #8271.

Not really anything we can do without more information (as in, ideally a reproducer). Perhaps you could help by finding the offending commit that broke things, though no guarantee that...

Regarding > is it possible that what we were doing was unsupported and worked under 7.x purely by accident? I ask because the documentation says that `-p` is for plugins,...

I agree it'd be nice if things worked that way, but I have no idea how to make them work that way :wink:

@maxime-michel You might want to take a look at the [keybinding cheatsheet](https://qutebrowser.org/img/cheatsheet-big.png) or the [list of default keybindings](https://github.com/qutebrowser/qutebrowser/blob/master/doc/help/settings.asciidoc#bindings.default). As for this issue: As long as nobody finds out a good...

I think we're all on the same page on how things *should* work. The problem is that there's no easy way for qutebrowser to know when a field gets input...

Works fine for me, even with qutebrowser v3.2.1 and QtWebEngine 6.7.3 (though on Linux). Are you actually testing with `--temp-basedir`? At least the version information doesn't show as much.

@A-Z-X-R While you look at more recent releases for #8503, it would be good if you could give this another try as well.

Please try the nightly as well with this, ~~I'll answer over in the other issue~~ or not, given that your comment is gone now. Still no idea what's going on...

I suppose having `:hint` pass the count through to userscripts would work. I'm not sure if I like the idea, given that it's just a very specific usage of `:hint`...