Not sure if this is fixed yet, as I haven't seen it in a while (but also didn't go out of my way to investigate it at the time). It did look somewhat odd, although it's hardly critical to the functionality of the addon.