Control not shown in Chrome

[zeyo-stud]

As shown in the following picture,
http://oi61.tinypic.com/2m7btd2.jpg

Chrome is using the default player but not videoJS control.
However, the plugin such as overlay is working correctly.
This issue happens on 4.2 version and later, not in 4.1.
Also, firefox do not have this issue.

[heff]

Is that on a mobile device?

[zeyo-stud]

This issue happens in my chrome on windows.

[heff]

Which Chrome version and which Windows version?

[zeyo-stud]

I am using CoolNovo 2.0.9.20 which is base on Chromium 27.0.1453.110 on windows 8 (desktop mode).
Using the same browser on windows 7 do not have this issue.
The page I tested is the home page of www.videojs.com.
So that it is the problem with my touchscreen?

Also, something want to ask about, does nativeControlsForTouch work for 4.4.2 on Android and iOS?
Is there some ways that I can works on myself to enable the controls on mobile?
Since I use my Android phone (Chrome 33.0.1750.136) can not see the VideoJS controls with nativeControlsForTouch:true.
While customControlsOnMobile:true on version 4.1 work for my phone although it appears a little bit strange that it overlap with the default player controls.

[vdumontier]

I have the same problem with chrome 33 on windows 8 & 8.1 but only with tactile devices.

It work good with nativeControlsForTouch:false in parameter.

thanks @zeyo-stud for your suggestion

[mmcc]

So the thing to keep in mind with nativeControlsForTouch is that there's a reason it's off by default. :) It works pretty well on some devices, but other devices really make life tough there, so we generally suggest letting native controls take over.

As for the original issue, we tried hard to reproduce and just can't. Chromium on Windows 7 / 8 both worked fine, and the CoolNovo copyright on their website is from 2010, so it seems a bit like abandonware at this point. Closing the issue, but if you're able to reproduce in a current browser, let us know and we'll reopen.

[michelt]

Hey it seems that some users have the issue with Windows 8.1 and Chrome 33 (last release)