Please check this issue here. The timeupdate event seems to behave differently with regard to the default tech (see here)