Hey All, thanks for flagging this!
We’ve passed this topic onto our UI3 team to investigate and work on a fix.