Confirmed here too! I've added it to our bug tracker with the tracking number 4662.


I work here