Search Results Opening in Current Tab
Hi,
The latest version of Voodpad changed slightly. In the past, when I performed a search, the results would open in a new tab.
The latest version opens search results in the current open tab which is never what I want as it obscures what I am currently working on.
Could you restore the previous behavior or make it an option in the preferences?
Regards,
Andrew
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Sarah on 07 May, 2018 03:21 PM
Hi Andrew,
Thanks for posting. I've passed your suggestion on to the team, and we will see if we can incorporate this again into future updates.
Let me know if there is anything else I can help with.
Warm regards,
Sarah
Primate Labs Inc.
2 Posted by Naomi Schoenfel... on 23 Jun, 2018 03:16 PM
Yep, this is another one that's interrupted my workflow pretty badly as well -- especially since when I back out of the search, Voodoopad now takes me to the top of the page I was originally on, rather than where I was before it navigated me away.
Some of my pages are quite long, so I'm doing a whole lot of scrolling that was never necessary before.
I'd love to see the original functionality restored.
3 Posted by Sarah on 27 Jun, 2018 04:00 PM
Hi Naomi,
Thanks for bringing that up. I've let the team know about that as well (VoodooPad starting at the top of page when navigating backwards). I can see how that might be frustrating.
All the best,
Sarah
Primate Labs Inc.
4 Posted by andrewb on 30 Jul, 2018 04:57 PM
A work around I found for this issue is the tab preference: "clicking a link" opens in a new tab. Seach seems to open in a new tab with this setting. I will have to change my usage pattern, but this seems to be an improvement at the moment.
5 Posted by andrewb on 30 Jul, 2018 08:12 PM
Oops, I was wrong. This preference does not fix search. So, I am still waiting on a fix for this issue.