It’s due to Chrome classifying small flash content as secondary and refusing to autoplay it under normal configuration. It should sort itself out when the full html5 player becomes default, which shouldn’t be too far in the future.
It’s due to Chrome classifying small flash content as secondary and refusing to autoplay it under normal configuration. It should sort itself out when the full html5 player becomes default, which shouldn’t be too far in the future.