Hi Vincent. Thanks for the note here, and my apologies that this one slipped through the cracks…not sure how that happened but I apologize on behalf of the whole team.
As for your specific issue, it doesn’t appear we’ve had earlier reports of this…so you may have uncovered a bug. But, I’m unable to recreate it using the latest code. 2.0.9 has been released since you first published this…were you able to update? If so, can you confirm whether or not the issue persists when running the 2.0.9 code base?
Let me know and if it persists and I can get a dev to take a look. Thanks again for your support and patience so far.