Can we navigate to a tiddler without changing the $:/HistoryList? #5796
Replies: 3 comments 1 reply
-
I'm not sure if the |
Beta Was this translation helpful? Give feedback.
-
As written here. #4782 (comment) ... probably not, with the existing navigation handling. ... Which we didn't fix yet, since several different core elements are involved. ... So IMO we need to improve the underlying mechanism first. If we introduce a hack for your "selection handling", imo it will make fixing the underlying problem harder. Just a thought. |
Beta Was this translation helpful? Give feedback.
-
The refresh mechanism of the edit text widgets avoids changing the value of the text area if it contains the focus. We do it because when a tiddler is being edited we can guarantee that the text in the control will always be up to date. We could explore tweaking the logic. For example, we might check whether the text we've got from the store is different to the text in the control before we assign it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm working on a mechanism that preserves the focused domNode over refresh cycles
There are also keyboard shortcuts to navigate from one tiddler in the StoryRiver to another
If there's a tiddler in edit-mode with the title focused and I navigate to another tiddler, the
$:/HistoryList
is changed which causes the page to refresh and theedit-text
widgets of the tiddler in edit-mode also somehow do a full refresh.Now I'm asking if it's possible to avoid that behavior either by not making the
edit-text
widgets do a full refresh when$:/HistoryList
changes (???) or by somehow avoiding the change of$:/HistoryList
Beta Was this translation helpful? Give feedback.
All reactions