Ability To Prevent DOM Element Removal In Active Note, Nav Tree, etc

[untitled]

I support this request.

I had a need to make table column headers dynamically attached at the top when scrolling, but it didn’t work. If it wasn’t for holroy’s reply (below), I wouldn’t have realized what was wrong.

1rst row of tables always visible when scrolling?

I’m not sure this is the case for you, but I do know that Obsidian is actively only loading parts of longer documents related to what is visible or not. This mean that if you table header is a portion of your document Obsidian believes is not visible, it’s removed from memory. This also means that it can as sticky as it likes, but if it’s not loaded it’ll not show. One possible workaround could possibly be to insert your table headers into the table every now and then. How is you table defined?…

In my case, compatibility of unloading of non-visible file elements from memory with CSS’s position: sticky will be enough.

related plugin request: Plugin which permanently renders div elements even if outside the viewport

---

Addition:

I’m not sure if this is the reason, but it seems that the ability to use the:

… {
  visibility: hidden;
}

…:hover {
  visibility: visible;
}

… is also impossible because of this feature of Obsidian’s work.

As a workaround, I have to use opacity instead of visibility.

---

One more addition:

It seems that this feature of Obsidian’s behavior also prevents CSS created for a specific combination of selectors from working correctly:

.selector00 + .selector01 + .selector02 {
	...;
}

… because as soon as one of the selectors leaves the viewport while scrolling the file, it is unloaded from memory, and what was .selector00 + .selector01 + .selector02 now becomes simply, for example, .selector01 + .selector02, and thus the CSS created no longer has any effect on the remaining .selector01 + .selector02 in the viewport.