Comment # 5 on bug 1204074 from Wolfgang Rosenauer

Ok, in that case this is somewhat expected behavior within the limits given by
the codec situation.
I have no idea how Firefox would be able to handle that differently. Therefore
closing. If anyone has an idea please reopen.