Annoying ctrl+f behaviour

Narushima

Hello everyone.

I often need to search through a page with ctrl+f. Unfortunately, the recente update has slightly changed how that works.
It used to be that I could just hit ctrl+f and enter/paste what I was looking for.

But now that search bar automatically pastes whatever text is already selected, so if you end up having to ctrl+a that first before you can search for something new.

Is there a way to change that so that it goes back to the old behaviour, where the text in the ctrl+f bar was already selected so it could be easily overwritten?

Narushima

@Gwen-Dragon As I said, I often have to search through a page after alt+tabbing out of Vivaldi, and I definitely have to ctrl+a the text in the search field to select it, otherwise what I type or paste just gets added on to what's already in the ctrl+f search bar.

Pesala

@Narushima Agreed. One has to use Ctrl A to select the text to overtype it, but sometimes this "Annoying behaviour" is very useful. One just needs to get accustomed to it. Take a look at my post in the Feature requests for 1.9 / 1.10 thread, and consider whether that would solve the problem for you.

Find Next (F3) Should not Open the Find Toolbar

If not, post your own feature request.

Narushima

@Pesala said in Annoying ctrl+f behaviour:

@Narushima Agreed. One has to use Ctrl A to select the text to overtype it, but sometimes this "Annoying behaviour" is very useful.

I don't think it can be. I don't see myself, or anyone, looking for [phrase], closing the search bar or alt-tabbing out only to come back and search for [phrase+something else].

And thank you for the suggestion, but I don't think it would change anything for me.

iAN CooG

I'm sure it will be eventually fixed, by the look of it, seems just a missing implementation. Having the search text already selected is normal behaviour, it's not selected only if the find in page function is activated when there's a selected text in the page, and that was introduced in latest snapshots.

Narushima

@Gwen-Dragon I probably explained it poorly.
But if that's fixed in the next version, then great.

Ayespy

@mady: When Gwen-Dragon says "upcoming Snapshot" it's because she has seen it ALREADY fixed in the new backstage versions that we test every day. So a user has cause to rely on that.

As to new features vs bugfixing, Vivaldi has to do both. But the primary focus has to be on features, because in order for Vivaldi to survive it has to attract new eyeballs and increase its user base. Right now it loses money, and that cannot last forever. What attracts eyeballs is things that are new and different. No one is trying or adopting Vivaldi because it's the most bug-free browser. They are coming over for new and different things. Then, thanks to the perfectionist in each one of us, developers also have to constantly shine and polish, to remove the little irritations that may eventually cause a new user to be turned off. So it's a balance. First excitement - then perfection.

Being both a perfectionist and a feature freak myself, I think so far they've struck about the right balance. But that's me. They had me at "mail client."