Re-reading all of your comments, I’m fairly convinced that the issue is probalby related to the theme you’re using, rather than the Jetpack plugin.
but is there a less cumbersome way to circumvent whatever the problem was in the future?
Taking into consideration that I’m assuming you probably have not edited any of the InkBLot theme files in a manner that may have accidentally caused the symptom, the only real solution is to fix whatever is broken.
If you really like the theme and want to continue using it, you should either find an updated version or a repair for the theme that’s compatible with the current version of WordPress, or choose a different theme that is. You can post a support question directly to the InkBlot dedicated forum here if you like. There’s a better chance of the developer seeing it and responding that way. InkBlot Support
[edit] Okay. Only because I want to make sure we’re really, really on the same page – this is still bothering me a bit, and I can’t help but feel like we may have missed a step:
“I already tried deactivating the only plugin I installed today (Jetpack)” …and…
“So deactivating all the plugins and changing to the default Twenty Sixteen”
Are you indicating that you only have the Jetpack plugin, or are you indicating that you have several plugins, and that it could still be plugin related simply because all plugins were deactivated and the default theme (Twenty Sixteen) activated at the same time? More specifically, was the symptom present under these exact conditions:
a) ALL plugins are deactivated
b) The Inkblot theme is active
What happens in that combination? Is the editor symptom still present?