You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When searching for a word in the main search bar (on the left panel), and then clicking on a result:
the page opens
the page is not scrolled to the first occurrence of the word.
I have a hypothesis that I haven't tested yet:
I think this occurs primarily when the page that is being opened has reached the editable-word-limit thingy: ie, it opens in read-only mode, not in edit mode.
Whether the hypothesis is true or false doesn't matter, the behavior is not the expected one, in my humble opinion.
I see myself having to search first on the left panel, then close the search bar that opened at the bottom, trigger it again using Cmd+F, then search again the word within the page to force the scrollbar to focus on the highlighted terms.
This is something I frequently use and I assume i'm not the only one, so I'd say it's a critical issue.
Error logs
not relevant.
The text was updated successfully, but these errors were encountered:
I think this occurs primarily when the page that is being opened has reached the editable-word-limit thingy: ie, it opens in read-only mode, not in edit mode.
No, this just isn't supported / implemented at all.
Trilium Version
0.63.3
What operating system are you using?
macOS
What is your setup?
Local + server sync
Operating System Version
latest
Description
When searching for a word in the main search bar (on the left panel), and then clicking on a result:
I have a hypothesis that I haven't tested yet:
Whether the hypothesis is true or false doesn't matter, the behavior is not the expected one, in my humble opinion.
I see myself having to search first on the left panel, then close the search bar that opened at the bottom, trigger it again using Cmd+F, then search again the word within the page to force the scrollbar to focus on the highlighted terms.
This is something I frequently use and I assume i'm not the only one, so I'd say it's a critical issue.
Error logs
not relevant.
The text was updated successfully, but these errors were encountered: