Cancel search filter loses cursor position
Answered
This is a bug that appeared when you did the makeover of the web version last year.
When you use the search filter to find something, then cancel the search, the cursor returns to the top of the whole list, rather than staying at the relevant item that you'd searched for. This significantly decreases the usefulness of Workflowy for people who have very long lists and use search to find things, but crucially what to then see the context and items around it.
A comment in a blog post highlighting this bug last August (August 21, 2018 at 11:09 am by Lee Granas) said this was fixed in beta.workflowy.com. However, it certainly isn't working for me.
This is a pretty major flaw and cripples the use of the search functionality significantly. Please can it be put right as soon as possible?
-
This continues to be a serious frustration. This bug combined with Ctrl+F not working means I cannot move an item around without manually scrolling through the list and finding it visually. Is a fix imminent?
-
I agree that this is a major frustration. I often search to find a place in my data - but then lose that place after I delete the search. I don't want to leave the search term in place because I want to see all items near my new point.
I need a simple way to move to a new spot in the data by searching
This significantly diminishes the usefulness of Workflowy
Desktop Windows 10; Chrome and Firefox and Opera
-
This is still happening on Chrome latest version, Windows 10. To reproduce:
Search for a word (e.g. "assets").
Position your cursor on a filtered item that contains "assets".
Either press the "Esc" key or click the "X" in the Search box to clear the search term.
RESULT: Cursor jumps to the very top of your outline. Filter is cleared - all items are displayed. Item that you just searched for is lost again!
-
Don't hold your breath for a resolution to this one. I asked again a couple of months ago (March 2021) and got this reply from Frank:
"We have discussed this at length in previous meetings and the development team has indicated that this is not something we are able to fix just yet. It's an incredibly complex issue which would require us to roll back features that are absolutely essential (progressive loading). This is something we may be able to tackle later down the line. So sorry.
~Frank"Substantially hampers workflow and limits usefulness of the product, but looks like something they're not going to fix. :(
Please sign in to leave a comment.
Comments
8 comments