I can't reproduce the problem have you tried to restart Boostnote?

This issue appears on my Windows (Windows 10 Home 1803) installation starting from 0.11.11. It doesn't appear on my Linux (openSUSE Tumbleweed) installation.
Thanks.

@ZeroX-DG Next day I opened Boostnote the bug was not there anymore. Looks like restarting solves the issue.

Also having this issue on Windows 10 Enterprise

I noticed that if I do a hard reload on the view (ctrl + r) rather than restarting Boostnote, it resolves the issue. When I restart, the issue is present again (and is again resolved by refreshing the view).

@jrpope2014 this is probably an issue on windows only. If it happens again, can you take a picture of the dev tool console? You can open the dev tool console by hitting ctrl + shift + i and switch to the console tab.

@ZeroX-DG here is what happened. Not sure if that error is what's causing the issue with the editor pane or not though. I ran through the following test scenarios to reproduce the error/get it to stop:

1. Open Boostnote application to a note that fits all on a single page. The result was that attachment folder did not exist message. No editor pane cutoff occurs, but the note it loaded into didn't require any scrolling.
2. From an open Boostnote application, I navigated to a different note. The message was logged a second time (I couldn't get it to log a third). Editor pane is cut off at the bottom.
3. After refreshing the view (ctrl + r), the message is no longer logged, and I cannot get it to appear again. Also, my editor pane is normal at that point.

@jrpope2014 the console output is only an information... As far as i know it does not indicate any problem.. Maybe i should have removed that debug line..

it appears because of the following reason: when you leave the note (e.g. onBlur) the attachmentManagement tries to figure out which attachments are not referenced in the note anymore and should be deleted from the file system therefore as well.. If there is no attachment folder for that particular note the information appears..

As far as i know: nothing to worry about.. :)

That's interesting! So yeah, if that's the case, there are no errors logged/thrown for the weird editor pane situation. I will try it on my computer later (which is Windows Home and not Enterprise) and see if there's a difference on that end. Sometimes I wish debugging Javascript was a skill that I possessed!

@issuehuntfest has funded $20.00 to this issue. See it on IssueHunt

Seems like this issue is fixed with the never versions. I'm using it on Arch Linux.

I'm still experiencing this issue with version 0.12.1 on Windows 10.