@danielsamuels not fixed according to the test we just posted -- lots of people confirming the bug in Chrome 41. We do see it fixed in 43