I've noticed that screenfull.enabled returns true on the Samsung Galaxy S4 / Android 4.3 Stock Browser, where the fullscreenAPI isn't supported. But this is not a bug in screenfull, as document.webkitFullscreenEnabled returns true and the stock browser is pretending to support the fullscreenAPI (see https://code.google.com/p/chromium/issues/detail?id=180734).
The HTC One / Android 4.4.2 Stock Browser returns undefined as expected and therefore screenfull.enabled is false.
Do you see any possibility to deal with this false behaviour?
First of all, thank you for your work!
I've noticed that screenfull.enabled returns true on the Samsung Galaxy S4 / Android 4.3 Stock Browser, where the fullscreenAPI isn't supported. But this is not a bug in screenfull, as document.webkitFullscreenEnabled returns true and the stock browser is pretending to support the fullscreenAPI (see https://code.google.com/p/chromium/issues/detail?id=180734). The HTC One / Android 4.4.2 Stock Browser returns undefined as expected and therefore screenfull.enabled is false.
Do you see any possibility to deal with this false behaviour?