PJ Eby

Addendum: it keeps working so long as it does not completely cover a monitor - resizing manually has the same effect as maximizing. The effect also persists across Obsidian restart...

Also seeing this warning appearing: ``` plugin:obsidian-kanban:formatted:21433 Event emitted with no handler dragStart undefined emit @ plugin:obsidian-kanban:formatted:21433 dragStart @ plugin:obsidian-kanban:formatted:14843 eval @ plugin:obsidian-kanban:formatted:15039 eval @ plugin:obsidian-kanban:formatted:10942 requestAnimationFrame (async) i @...

Further detail: it's only maximizing on my *main* monitor that's the problem. Maximizing on either my left or right secondary monitor doesn't produce the effect.

And even more detail: it's not maximizing or sizing to the monitor, it's *hiding the main window* that causes the problem. If I minimze the Obsidian main window, the same...

So, per Licat on Discord this is an issue where using the global requestAnimationFrame defers all the calls while the window isn't visible at least in part. The correct window's...

So it turned out to be setTimeout -- all uses of window.setTimeout and clearTimeout need to use the active window's version. My "const at the top" trick wasn't addressing the...

Some possibly-related info. I just had Kanban crash in a secondary window with this error: ``` Uncaught (in promise) TypeError: Failed to execute 'unobserve' on 'ResizeObserver': parameter 1 is not...

More info: it appears the issue has to do with moving a kanban pane to a new window. I can't 100% reliably reproduce it, but I can now do so...

Note that if the kanban view was implemented as a markdown postprocessor instead of as a custom view type, then normal embedding would work just fine. (There'd also be no...

Please stop leaving +1 comments: they send an email to everyone else who has touched this issue every time you do. If you look at the top of the issue,...