Is this a bug/regression of the UI components?
Thanks for reporting this. We’re looking into what’s happened now.
This has now been fixed.