Yup, and Safari may be signaling that <video> doesn't provide the right semantics for the expected behavior. <img> probably isn't the right place either and a new tag might be necessary, but I'll bet the desired code path for the browsers is closer to the img implementation then the video one.