We’re no longer able to replicate this bug since the editor overhaul in Supernotes 3.1. Marking this as fixed
