Our QA team has confirmed this issue. We’ll look into it (not specific timeframe of fix at this stage) and I’ll nclude it on the next Known Issues list for 3.4. Thanks for the update.
@Nullings for future bug reports please follow the format 
(this format will pop-up if you go to create a new post)