I’ve opened an internal ticket, but it’s a problem with the Look-and-Feel used for the component, which means it’s not something we’ll fix in-house, which in turn means it’s going to probably be a couple of releases before it gets fixed unless this already happens to be on their radar.