Indeed, that's a bug that I didn't have the time to fix. :( Oddly enough, it seems to occur *much* more frequently in the HTML5 export, so if you want to avoid it, maybe try downloading it for your OS.