search

w3c / webmediaporting

Web Media porting spec
2 stars 10 forks source link

fullscreen api: is a request to fullscreen a video element guaranteed to succeed? #4

Open jpiesing opened 7 years ago

jpiesing commented 7 years ago

Copied over from https://github.com/w3c/webmediaapi/issues/22

Support for the fullscreen API doesn't mean a request to full screen (say) a video element is guaranteed to succeed. If you look at step 6 of the requestFullScreen algorithm, the last of the 4 sub-steps refers to https://fullscreen.spec.whatwg.org/#fullscreen-is-supported which says "Fullscreen is supported if there is no previously-established user preference, security risk, or platform limitation. " Is it reasonable for this test to fail on a WAVE device?

michelnev commented 7 years ago

I think it is reasonable for it to fail on PCs, tablets, & phones to conform to the user's security preferences and therefore fail on those types of devices. For a trusted ecosystem, it should not be allowed to fail.

jpiesing commented 7 years ago

It's reasonable for fullscreen of a video element to fail due to a user preference as the user then has the opportunity to change that if they want to watch their video full screen.

The WHATWG fullscreen spec includes 2 other reasons why full screen might not be supported - "security risk" and "platform limitation". "security risk" isn't defined and it's not obvious that a user could do anything about this. A user certainly would not be able to do anything about "platform limitation". Is it reasonable for a WAVE system to allow these two reasons why full screen might not be supported?