[BUG] cant run element.requestFullscreen() without user interaction #224

New issue

Open

opened 2020-04-24 14:50:11 -05:00 by saty9 · 2 comments

saty9 commented

2020-04-24 14:50:11 -05:00

(Migrated from github.com)

Platform

Operating system and version:
Ubuntu 18.04.4 LTS
(also reproduced on windows 10)
OBS Studio version:
installed using ubuntu store snap version 25.0.7 rev 1063

Expected Behavior

A page that runs videoelement.requestFullscreen() should have that element go fullscreen

Current Behavior

The action is blocked with the message:

'requestFullscreen' on 'Element': API can only be initiated by a user gesture.

Steps to Reproduce

https://jsfiddle.net/saty9/xpntf1qc/3/
Should have enough to reproduce a page with the same issue. I believe it cant be hosted from a local file for testing as that may bypass the restriction (I haven't checked this)

Additional information

The video is displaying data from a webrtc stream in my usecase

## Platform   Operating system and version: Ubuntu 18.04.4 LTS (also reproduced on windows 10) OBS Studio version: installed using ubuntu store snap version 25.0.7 rev 1063 ## Expected Behavior  A page that runs videoelement.requestFullscreen() should have that element go fullscreen ## Current Behavior   The action is blocked with the message: ``'requestFullscreen' on 'Element': API can only be initiated by a user gesture.`` ## Steps to Reproduce    https://jsfiddle.net/saty9/xpntf1qc/3/ Should have enough to reproduce a page with the same issue. I believe it cant be hosted from a local file for testing as that may bypass the restriction (I haven't checked this) ## Additional information   The video is displaying data from a webrtc stream in my usecase

dodgepong commented

2020-04-24 15:09:56 -05:00

(Migrated from github.com)

I suspect they are trying to fullscreen a video player, perhaps.

WizardCM commented

2021-06-16 00:57:07 -05:00

(Migrated from github.com)

I can however see a use case for potentially sending a dummy interaction on load to make the page think a user has interacted with it, to allow for APIs such as this to succeed without actual user interaction (via the Interact dialog). The downside of doing this is there are certain APIs that shouldn't be run without actual user interaction.

After testing this myself, the behaviour is correct in terms of behaving like a web browser - that is, the fullscreen API fails if you have not yet interacted with the site, but succeeds if you have. I've confirmed Microsoft Edge 91 does the same thing as obs-browser. I can however see a use case for potentially sending a dummy interaction on load to make the page think a user has interacted with it, to allow for APIs such as this to succeed without actual user interaction (via the Interact dialog). The downside of doing this is there are certain APIs that *shouldn't* be run without actual user interaction.

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gh-obsproject/obs-browser#224

No description provided.

Rows
Columns